53-1003090-02 19 February 2014 FastIron Ethernet Switch Stacking Configuration Guide Supporting FastIron Software Release 08.0.
© 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.
Contents Preface..................................................................................................................................... 5 Document conventions......................................................................................5 Text formatting conventions.................................................................. 5 Command syntax conventions.............................................................. 5 Notes, cautions, and warnings....................................
PHY calibration errors in stack ports of the ICX 6610.......................42 Configuring an ICX 6430 and ICX 6450 traditional stack..............................43 Configuring ICX 6430 or ICX 6450 trunked stacking ports............... 43 Configuring ICX 6430 or ICX 6450 multi-trunked stacking ports...... 43 Periodic background stack diagnosis for ICX 6430 and ICX 6450 devices...............................................................................
Displaying information about stack failover.......................................117 Displaying information about link synchronization status..................117 Syslog messages for hitless stacking failover and switchover..........117 Syslog messages.......................................................................................... 118 Mixed Stacking.....................................................................................................................
4 FastIron Ethernet Switch Stacking Configuration Guide 53-1003090-02
Preface ● Document conventions......................................................................................................5 ● Brocade resources............................................................................................................ 7 ● Getting technical help........................................................................................................7 ● Document feedback...................................................................................................
Notes, cautions, and warnings Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [] 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.
Brocade resources Brocade resources 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.
Document feedback Document feedback 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.
About This Guide ● Introduction....................................................................................................................... 9 ● What’s new in this document............................................................................................ 9 ● Related publications........................................................................................................10 ● How command information is presented in this guide.....................................................
Related publications Related publications The following Brocade documents supplement the information in this guide and can be located at http://www.brocade.com/ethernetproducts. • • • • • • • • • • • • • • • • • • • • FastIron Ethernet Switch Administration Guide, 08.0.10a FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide, 08.0.10a FastIron Ethernet Switch Layer 3 Routing Configuration Guide, 08.0.10a FastIron Ethernet Switch IP Multicast Configuration Guide, 08.0.
Traditional Stacking ● Supported traditional stacking features...........................................................................11 ● Traditional stacking overview.......................................................................................... 12 ● Supported traditional stacking topologies....................................................................... 14 ● Connecting ICX 6450 and ICX 6430 devices in a traditional stack.................................
Traditional stacking overview Feature ICX 6430 ICX 6450 FCX ICX 6610 ICX 6650 FSX 800 FSX 1600 ICX 7750 Hitless stacking: Hitless failover, Hitless switchover 08.0.01 08.0.01 08.0.01 08.0.01 No No No Trunking of stacked ports 08.0.01 08.0.01 No 08.0.01 No No No Auto Image Copy for stack units 08.0.01 08.0.01 08.0.01 08.0.01 No No No Stack port resiliency No No No 08.0.10a No No No NOTE Traditional stacking is not supported on the ICX 6430-C devices.
ICX devices ICX devices 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 Switch Hardware 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.
Supported traditional stacking topologies • • • • • • • • • • • • • • • • 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.
Brocade traditional stacking topologies Brocade traditional stacking topologies 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.
Traditional Stacking 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.
Traditional Stacking FCX stack topologies shows FCX-E devices in a linear topology stack. 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.
ICX 6610 stacking for different topologies 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.
Traditional Stacking The following figure shows a fully connected linear stacked trunk topology. FIGURE 6 ICX 6610 linear stack topology The following figure shows a fully connected stacked trunk ring topology.
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.
Connecting ICX 6450 devices in a stack 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.
ICX 6430 and ICX 6450 stack topologies • • • • • 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.
Traditional Stacking 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.
Software requirements 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 stacking configuration notes procedure, refer to Scenario 1 - Three-member traditional stack in a ring topology using securesetup 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.
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.
Traditional Stacking 3. Connect your console to the intended active controller. The unit through which you run securesetup becomes the active controller by default. 4. Issue the stack enable command on the intended active controller. device# config terminal device(config)# stack enable device(config)# exit 5. Enter the stack secure-setup command.
Traditional Stacking For ICX devices, it displays an equals sign (=) to show connections between trunk ports, for example: ICX6610-24P POE Router#show stack active standby +---+ +---+ +---+ =2/1| 1 |2/6==2/6| 5 |2/1==2/1| 4 |2/6= | +---+ +---+ +---+ | | | |-------------------------------------| NOTE In this output, D indicates a dynamic configuration. After you perform a write memory , this display will change to S, for static configuration. 6.
Scenario 2 - Three-member traditional stack in a ring topology using the automatic setup process For ICX devices, it displays the port up state of all ports of the trunk, for example: ICX6610-24P POE Router#show stack stack-port active standby +---+ +---+ +---+ =2/1| 1 |2/6==2/6| 5 |2/1==2/1| 4 |2/6= | +---+ +---+ +---+ | | | |-------------------------------------| U# Stack-port1 1 up (1/2/1-1/2/5) up ports: 1/2/1, 1/2/2, 1/2/3, 1/2/4, 1/2/5 up ports: 1/2/6, 1/2/7, 1/2/8, 1/2/9, 1/2/10 4 up (4/2/1-4/2/5) u
Traditional Stacking 1. Power on the devices. 2. This process requires clean devices (except for the active controller) that do not contain any configuration information. To change a device to a clean device, enter the erase startup-config command and reset the device. When all of the devices are clean, continue with the next step. NOTE The physical connections must be sequential, and must match the stack configuration. 3. Log in to the device that you want to be the active controller. 4.
Configuration tips for building a stack using the automatic setup process priority 255 stack unit 2 module 1 fcx-24-port-copper-base-module module 2 fcx-xfp-1-port-10g-module module 3 fcx-xfp-1-port-10g-module priority 240 stack unit 3 module 1 fcx-24-port-copper-base-module module 2 fcx-xfp-1-port-10g-module module 3 fcx-xfp-1-port-10g-module stack enable ! 11. To see information about your stack, enter the show stack command.
Extended distance stacking device(config-unit-1)# priority 255 device(config-unit-1)# stack enable Enable stacking. This unit actively participates in stacking device(config-unit-1)# write memory Write startup-config done. Flash Memory Write (8192 bytes per dot) .Flash to Flash Done. device(config-unit-1)# end Unit 2 device# config t device(config)# stack suggested-id 2 device(config)# stack enable Enable stacking. This unit actively participates in stacking Write startup-config done.
Connectivity options for stacking with FCX and ICX Series devices TABLE 1 Fiber-optic options and stacking distances Device Stacking port Copper options Fiber-optic options Fiber-optic maximum distance ICX 6610 4 X 40 Gbps 1- or 5-meter OSFP 40G Base-SR4 • Dedicated ICX 6450 4 X 10 Gbps Stacking and uplink ICX 6430 4 X 1 Gbps Stacking and uplink FCX 624S 2 X 18 Gbps FCX 648S Dedicated FCX 624S-F FCX 648S-F Optional 2-port 10 GbE XFP module • 100 meters (OM3 cable) 150 meters (OM4 cabl
FCX traditional stack configuration FCX traditional stack configuration FCX devices cannot be intermixed with non-FCX devices, and FCX devices have more possible stacking ports. Every FCX-S and FCXS-F device contains two default 16 Gbps stacking ports on the rear panel and two 10 Gbps ports on the front panel that can also be used as stacking ports. NOTE FCX-I and FCX-E devices can only be used for stacking if they have an optional 10 Gbps SFP+ module installed in the front panel.
Changing FCX-S and FCXS-F CX4 ports from 10 Gbps to 16 Gbps • • • • • • • • 10-full - 10M, full duplex 10-half - 10M, half duplex 100-full - 100M, full duplex 100-half - 100M, half duplex 1000-full-master - 1G, full duplex, master 1000-full-slave - 1G, full duplex, slave 10g-full - 10G, full duplex auto - Autonegotiation NOTE Both ends of a link must be configured for 10 Gbps for the link to operate as 10 Gbps.
Configuring default ports on FCX devices BPDU guard is Disabled, ROOT protect is Disabled Link Error Dampening is Disabled STP configured to ON, priority is level0, mac-learning is enabled Flow Control is enabled mirror disabled, monitor disabled Not member of any active trunks Not member of any configured trunks No port name IP MTU 1500 bytes, encapsulation ethernet 300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization 300 second output rate: 0 bits/sec, 0 packets/sec, 0.
Traditional Stacking NOTE FCX-I and FCX-E models cannot be used in a traditional stack without the addition of an optional 10 Gbps SFP+ module.
Using secure-setup to build an FCX traditional stack Error! port 3/4/1 is invalid device(config-unit-3)# stack-port 3/2/1 To return both ports to stacking status, enter the no stack-port command on the single stacking port. This converts both ports to stacking ports. By default, if both ports are stacking ports, they are displayed by the system only when stacking is enabled. If only one port is configured as a stacking port, the system always displays this port.
Configuring a default stacking port to function as a data port device#show stack alone: standalone, D: dynamic config, S: static config ID Type Role MAC Address Pri State Comment 1 S FCX624POE active 0000.00e5.0100 128 local Ready 2 S FCX648POE standby 0000.00d6.0511 0 remote Ready 3 S FCX624 member 0000.0099.0000 0 remote Ready standby active +---+ +---+ +---+ | 3 |3/1--3/1| 2 |2/1--2/1| 1 | +---+ +---+ +---+ Current stack management MAC is 0000.00e5.
Configuration notes for ICX 6610 stack topologies At least one port of a trunk must be connected. If multiple ports of a trunk are connected, they must be connected to the same trunk of other unit. For example, it is invalid that the two ports of a trunk connect to two different units, or to different trunks of the same unit. Wrong connection might result in stacking formation failure or other problems. Some invalid connections still form a stack but with forwarding problems.
Stack port resiliency in ICX 6610 devices the diagnosis prints nothing because it cannot distinguish hardware failure or the cable is not connected. *** Warning! miss 4*10G link 5/2/8(down)to 1/2/8(down). Stack can still work. *** Warning! U1, dir=1, 4*10G ports: 1/2/8 are down. *** Warning! U5, dir=1, 4*10G ports: 5/2/8 are down.
PHY calibration errors in stack ports of the ICX 6610 When a stack unit reloads, the stack unit generates a syslog message similar to the following: SYSLOG: <9>3d21h52m57s : ICX6610-24P Router Stack: unit 3 Reload u3 in 10 sec due to 3/2/6 port problems. reason: lose one nbr SYSLOG: <9>0d00h08m59s : ICX6610-48 Router Stack: unit 2 U3 detects stack port problem.
Configuring an ICX 6430 and ICX 6450 traditional stack Configuring an ICX 6430 and ICX 6450 traditional stack ICX 6430 and ICX 6450 devices can be stacked using the methods and topologies described in “Connecting ICX 6450 and ICX 6430 devices in a traditional stack.
Displaying multi-trunked stacking configuration trunk, and other side of the ports does not. A trunk-to-port connection can result in packet drops and can potentially break a stacking link. The primary ports of the stack trunk must be connected and in an up status to enable the multi-stacktrunk command. If the primary stack trunk ports are not connected and not in an up status, the command is rejected and the following error message is displayed on the CLI.
Error messages encountered during the configuration of an ICX 6430 or ICX 6450 traditional stack 1. Ports of the same trunk connect to different units. 2. Ports of the same trunk connect to different trunks of the same unit. 3. One end of a 10G port is up and the other end is down. 4. Communication problems between units of the stack Another connection error is that the two cables of a trunk go to different units, or to different trunks of the same unit as in case 1 and 2.
Verifying a traditional stack configuration Verifying a traditional stack configuration Log in to the active controller and verify the stack information by entering the show running-config and show stack or show stack detail commands. If your stack is configured properly, you should see the following: • • One active controller, one standby controller, and stack members. All stack members show a status of Ready The following output shows an example configuration of an FCX traditional stack.
Brocade traditional stack management UNIT 4: SL 2: FCX-2XGC 2-port 16G Module (2-CX4) ========================================================================== UNIT 4: SL 3: FCX-2XG 2-port 10G Module (2-XFP) ========================================================================== UNIT 8: SL 1: FCX-48G POE 48-port Management Module P-ENGINE 0: type DB90, rev 01 P-ENGINE 1: type DB90, rev 01 ========================================================================== UNIT 8: SL 2: FCX-2XGC 2-port 16G Module
Logging in through the CLI Logging in through the CLI You can access the traditional stack and the CLI in two ways: • • Through a direct serial connection to the console port Through a local or remote Telnet session using the stack IP address You can initiate a local Telnet or SNMP connection by attaching a cable to a port and specifying the assigned management station IP address.
Traditional Stacking NOTE Error messages that are generated during a reload of the active controller will not appear on rconsole connections from the stack units to the active controller. To see these error messages, you must connect a console cable to the active controller itself. To establish an rconsole session, enter the rconsole command as shown: device# rconsole 1 Syntax: rconsole stack-unit The following example shows how to establish rconsole sessions to stack members.
Traditional stack management MAC address Traditional stack management MAC address The traditional stack is identified in the network by a single MAC address, usually the MAC address of the active controller (the default). If a new active controller is elected, the MAC address of the new active controller (by default) becomes the MAC address for the entire stack. However, you can manually configure your stack to use a specified MAC address.
Removing MAC address entries stack 2 module 1 fcx-24-port-copper-base-module module 2 fcx-cx4-1-port-10g-module module 3 fcx-cx4-1-port-10g-module stack enable stack mac 0000.0000.0011 To display the stack MAC address, enter the show chassis command. device# show chassis The stack unit 1 chassis info: Power supply 1 (NA - AC - Regular) present, status ok Power supply 2 not present Fan 1 ok Fan 2 ok Exhaust Side Temperature Readings: Current temperature : 35.5 deg-C Warning level.......: 80.
Traditional stack unit identification Traditional stack unit identification Stack units are identified by numbers 1 though 8. You can display stack unit IDs by entering the show stack command. A new device (one that has not been connected in traditional stack or has not been manually assigned a stack unit number) ships with a default number of 1. Once you enable stacking and the unit becomes part of a traditional stack, its default stack unit number changes to the lowest available number in the stack.
CLI command syntax for stack units 1 S FCX624 active 0000.00eb.a900 128 local Ready 2 S FCX624 standby 0000.004f.4243 0 remote Ready, member after reload 3 S FCX624 member 0000.005d.a100 200 remote Ready, active after reload device(config-unit-3)# Changing the priority of a stack unit To change the priority value for a stack unit, enter the priority command.
Traditional Stacking TABLE 3 Stacking CLI commands (Continued) Command Description location show chassis Displaying traditional stack chassis information on page 64 show flash Displaying traditional stack flash information on page 62 show memory Displaying traditional stack memory information on page 63 show module Displaying stack module information on page 65 show running-config Displaying running configuration information on page 75 show stack Displaying stack information on page 66 show s
Enabling the stacking mode TABLE 3 Stacking CLI commands (Continued) Command Description location hitless-failover enable Enabling hitless stacking on page 108 stack switch-over Executing a hitless stacking switchover on page 111 show stack Displaying information about hitless stacking on page 116 show stack failover Displaying information about stack failover on page 117 show stack link-sync Displaying information about link synchronization status on page 117 Enabling the stacking mode When a
Converting from a pre-stacking image to a stacking image Converting from a pre-stacking image to a stacking image When you boot a stacking image (release 05.X or later) on a device with a pre-stacking (pre-release 05.X) startup-config.txt file, the system automatically converts the interface format from 0/X/X to 1/X/X. In addition, when a write memory command is issued, the pre-stacking startup-config.txt file is renamed to start-config.v4 and saved as a backup file.
Confirming traditional stack software versions Confirming traditional stack software versions All units in a traditional stack must be running the same software image. To confirm this, check the software version on all devices that you want to add to your traditional stack. Upgrade any units that are running older versions of the software before you build your stack. 1. Telnet, SSH, or connect to any of the console ports in the stack. 2. Enter the show version command.
Controlling stack topology • • • • after - Schedule reloading after certain time period at - Schedule reloading at an exact later time cancel - Cancel scheduled reload unit-id - Stack members to reload. The unit-list variable can be a combination, such as 2,4-6,8. Tokens must be separated by a comma and there is no space. Stack units can be reloaded only if they are not the active master. To reload the active master, use the stack switch-over command.
Merging traditional stacks When a stack breaks into partitions, the partition with the active controller remains operational. If a partition contains the standby controller, this partition will become operational because the standby controller will assume the active role and will reload the partition units. If the hitless-failover enable command is configured, the partition units are not reloaded. A partition without an active or standby controller will not function.
Traditional Stacking stack. When you enable the Persistent MAC Address feature, you configure a time delay before the stack MAC address changes. During this configured interval, if the previous active controller is reinstalled in the stack, the stack continues to use the MAC address of this unit, even though it may no longer be the active controller.
Unconfiguring a traditional stack To display the stack MAC addresses, enter the show stack command. device(config)# show stack alone: standalone, D: dynamic config, S: static config ID Type Role MAC Address Prio State Comment 1 S FCX648p active 0000.00d5.9380 80 local Ready 2 S FCX648 member 0000.0066.8880 0 remote Ready 3 S FCX624 standby 0000.00dc.0ec0 40 remote Ready Current persistent MAC is 0000.00d5.9380 device(config)# stack mac 000.011.
Displaying traditional stack information • • • me - Unconfigure this unit only clean - Removes all startup configuration files including v4 and v5 and makes this a clean unit mixed-stack - Removes all peripheral ports and peripheral trunks from the ICX 6610 devices in a mixed stack. NOTE The stack unconfigure me command is available to all units, while stack unconfigure all and stack unconfigure stack-unit are available on the active controller only.
Displaying traditional stack memory information Compressed Compressed Code Flash Stack unit Compressed Compressed Compressed Code Flash device# Sec Code size = 2873523, Version 04.2.00aT7e1 (fcx04200a.bin) BootROM Code size = 403073, Version 03.0.00T7e5 Free Space = 24117248 3: Pri Code size = 3034232, Version 05.0.00T7e1 (fcx05000.bin) Sec Code size = 2873568, Version 04.2.00T7e1 (fcx04200.bin) BootROM Code size = 405217, Version 04.0.
Displaying traditional stack chassis information TABLE 5 Field definitions for the show memory command Field Description Total DRAM The size (in bytes) of DRAM Dynamic memory The total number of bytes in dynamic memory, including the number of bytes that are available (free, or unused), and the percentage of memory used. Displaying traditional stack chassis information The show chassis command displays chassis information for each stack unit.
Displaying stack module information TABLE 6 Field definitions for the show chassis command (Continued) Field Description Exhaust Side Temperature Readings From the air exhaust side of the chassis, the current temperature reading, the warning level temperature setting, and the shutdown level temperature setting. Intake Side Temperature Reading The current temperature reading from the air intake side of the chassis.
Displaying stack resource information Displaying stack resource information Use the show stack resource command to display stack resource information, as shown in the example output from an ICX 6610 switch.
Traditional Stacking +--+ +--+ +--+ +--+ +--+ +--+ =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= +--+ Standby u5 - protocols ready, can failover or manually switch over Current stack management MAC is 0000.0034.1234 If you add a stack member ID, output is displayed for that member only.
Traditional Stacking TABLE 9 Field descriptions for the show stack command Field Description alone: Standalone This device is operating as a standalone device S: static configuration The configuration for this unit is static (has been saved with a write memory command). D: dynamic configuration The configuration for this unit is dynamic and may be overwritten by a new stack unit. To change to a static configuration, enter the write memory command. ID The stack identification number for this unit.
Displaying stack flash information Displaying stack flash information Use the show stack flash command to display information about flash memory for stack members, as shown in this example output from an ICX 6610 switch. device# show stack flash There is no startup-config.
Traditional Stacking DAT: 15556, DAT+ACK: 1, DAT+WND: 0, DAT+ACK+WND: 0 Data retransmits done: 1069, Zero-window probes sent: 0 Dup ACK pkts rcvd: 1224, Pkts rcvd w/dup data: 0 Pkts rcvd w/data past window: 0 Session statistics: image-transfer, unit 2, channel 1: Session state: established (last established 15 hours 11 minutes 2 seconds ago) Connections established: 1 Remote resets: 0, Reset packets sent: 0 Connection statistics (for current connection, if established): Msgs sent: 9850, Msgs received: 1 At
Traditional Stacking Session statistics: base-channel, unit 3, channel 0: Session state: established (last established 15 hours 33 minutes 49 seconds ago) Connections established: 1 Remote resets: 0, Reset packets sent: 0 Connection statistics (for current connection, if established): Msgs sent: 14647, Msgs received: 14003 Atomic batches sent: 0, Atomic batches received: 0 Pkts sent: 31055, Pkts received: 31403 Msg bytes sent: 1801742, Msg bytes received: 1232204 Pkt bytes sent: 2402644, Pkt bytes received
Displaying IPC statistics for a specific stack unit Remote resets: 0, Reset packets sent: 0 Connection statistics (for current connection, if established): Msgs sent: 14630, Msgs received: 14031 Atomic batches sent: 0, Atomic batches received: 0 Pkts sent: 30186, Pkts received: 31052 Msg bytes sent: 1801548, Msg bytes received: 1234680 Pkt bytes sent: 2325044, Pkt bytes received: 1857824 Flushes requested: 30, Suspends: 0, Resumes: 0 Packets sent with data (DAT), ACKs, and window updates (WND): Other: 1199
Traditional Stacking Message types sent: [9]=1182, [10]=2, [11]=2, [13]=2, [19]=29, Message types received: [9]=506, [10]=1, [13]=2, Session statistics, unit 3, channel 0: Session state: established (last established 32 minutes 19 seconds Connections established: 1 Remote resets: 0, Reset packets sent: 0 Connection statistics (for current connection, if established): Msgs sent: 971, Msgs received: 506 Atomic batches sent: 0, Atomic batches received: 0 Pkts sent: 1205, Pkts received: 1088 Msg bytes sent: 44
Displaying stack neighbors information Displaying stack neighbors information The show stack neighbors command displays information about stack member neighbors. The following output is from an ICX 6610 switch.
Displaying running configuration information 2 3 4 5 6 7 up up up up up up up up up up up up up up up up up up up up ports: 1/2/1, ports: 1/2/6, (2/2/1-2/2/5) ports: 2/2/1, ports: 2/2/6, (3/2/1-3/2/5) ports: 3/2/1, ports: 3/2/6, (4/2/1-4/2/5) ports: 4/2/1, ports: 4/2/6, (5/2/1-5/2/5) ports: 5/2/1, ports: 5/2/6, (6/2/1-6/2/5) ports: 6/2/1, ports: 6/2/6, (7/2/1-7/2/5) ports: 7/2/1, ports: 7/2/6, 1/2/2, 1/2/3, 1/2/4, 1/2/5 1/2/7, 1/2/8, 1/2/9, 1/2/10 2/2/2, 2/2/3, 2/2/4, 2/2/5 2/2/7, 2/2/8, 2/2/9, 2/2/10 3
Displaying configured stacking ports priority 128 stack-trunk 1/2/1 to 1/2/2 stack-trunk 1/2/6 to 1/2/7 stack-port 1/2/1 1/2/6 stack unit 4 module 1 icx6610-48p-poe-port-management-module module 2 icx6610-qsfp-10-port-160g-module module 3 icx6610-8-port-10g-dual-mode-module priority 100 stack-trunk 4/2/1 to 4/2/2 stack-trunk 4/2/6 to 4/2/7 stack-port 4/2/1 4/2/6 stack unit 5 module 1 icx6610-48-port-management-module module 2 icx6610-qsfp-10-port-160g-module module 3 icx6610-8-port-10g-dual-mode-module pri
Displaying software version information Displaying software version information The show version command shows the software version that the stack is running. Note that the last line of this output shows the bootup ID and role for this unit. Output resembles the following. device(config)# show version Copyright (c) 1996-2013 Brocade Communications Systems, Inc. All rights reserved. UNIT 1: compiled on Apr 26 2013 at 20:08:17 labeled as FCXR08000a (8837030 bytes) from Primary FCXR08000a.bin SW: Version 08.
Displaying stacking port interface information ========================================================================== UNIT 5: SL 2: ICX6610-QSFP 10-port 160G Module ========================================================================== UNIT 5: SL 3: ICX6610-8-port Dual Mode(SFP/SFP+) Module ========================================================================== UNIT 6: SL 1: ICX6610-24 24-port Management Module Serial #: BMA2524H02S License: ICX6610_PREM_ROUTER_SOFT_PACKAGE (LID: docHKHJjFHu) P-
Displaying stacking port statistics TABLE 15 Field descriptions for the show interfaces stack-ports command Field Description Port The stack identification number for this unit. Link Identifies the configuration for modules on this unit.
Displaying stacking topology TABLE 16 Field definitions for the show statistics stack-ports command Field Description Port The stack identification number for this unit.
Adding, removing, or replacing units in a traditional stack 4: 5/2/9 (T1) <---> 6/2/4 (T0) 5: 5/2/10(T1) <---> 6/2/5 (T0) Link 7: u7 -- u6, num=5 1: 6/2/6 (T1) <---> 7/2/6 (T1) 2: 6/2/7 (T1) <---> 7/2/7 (T1) 3: 6/2/8 (T1) <---> 7/2/8 (T1) 4: 6/2/9 (T1) <---> 7/2/9 (T1) 5: 6/2/10(T1) <---> 7/2/10(T1) CPU to CPU packets are fine between 7 units.
Removing a unit from a traditional stack • • order for the configuration to stay on the active controller (to make it a static configuration), you must do a write memory on the active controller. If the active controller has configuration information for a new unit, and it matches the base module (module 1) of the new unit, no action is necessary.
Moving a unit to another stack 1. 2. 3. Remove the old stack unit from the stack Connect the new unit to the existing stack using the same stacking ports used by the old unit. Run secure‐setup to select the ID of the old unit for the new unit. The active controller resets the unit, and it joins the stack.
Configuration notes for renumbering stack units Enter an unused id for the UPSTREAM FCX623 unit a 1 hop(s) (1-8)[5]: 2 Enter an unused id for the UPSTREAM FCX624 unit at 2 hop(s) (1-8) [6]: 3 device# Election, was active, no role change, assigned-ID=1 reset unit 2: diff bootup id=5 reset unit 3: diff bootup id=6 Election, was active, no role change, assigned-ID=1 device# show stack ID Type Role MAC Address Pri State Comment 1 S FCX624 active 0000.0039.2d40 128 local Ready 2 S FCX624 standby 0000.00d5.
Configuring SNMP for a traditional stack For more information about Syslog messages, refer to the FastIron Ethernet Switch Administration Guide. Configuring SNMP for a traditional stack SNMP server and feature configuration is the same for a traditional stack as it is for standalone units. In a traditional stack, SNMP gets and sets are processed by the active controller for the standby controller and all stack members.
Traditional Stacking NOTE If you are building a stack using secure-setup, you do not have to enter stack enable on each unit. 2. Check that all of your stacking port connections are secure and working properly. Enter show interface stack on each device to confirm that the stacking port links are up and the ports are in the forward state. device# show interfaces stack Port Link State Dupl Speed 1/2/1 Up Forward Full 10G 1/2/2 Up Forward Full 10G Trunk None None Tag No No P MAC Name 1 0000.00eb.
Troubleshooting a stacking upgrade NOTE If your intended stacking ports are connected in a ring topology, they will not all appear to be in the forwarding state because of spanning tree, but secure-setup can still build the stack. 7. If you run out of flash memory while doing a write memory, your stack devices may contain very large startup-config.v4 or startup-config.old files, which are preserved for recovery purposes. If you do not need these files, you can delete them using the flash delete command.
Troubleshooting image copy issues Troubleshooting image copy issues The copy tftp flash command copies the image to all stack units including the active controller. The copy flash flash command copies the image from the primary or secondary flash on the active controller to the primary or secondary flash image of a stack member, respectively. If you are unable to copy an image to one or more stack units, check the following: • • Make sure the unit is actually part of the stack. Use the show stack command.
Advanced feature privileges Advanced feature privileges Advanced feature privileges must be enabled to run advanced features such as BGP. Both active and standby units must be enabled for advanced features for these features to operate across the stack. A unit that is not enabled for these features is put into a non-operational state. If the active controller is not enabled for advanced features, these features will not operate on the stack.
Auto Image Copy for stack units Configuration mismatches can happen during manual setups, or when moving a unit from one stack to another stack or the ID of a unit is changed by secure-setup. When you renumber identical units using secure-setup, the configurations are not mapped to the new units (because they match exactly). However, if you switch the IDs of units that are not identical, a configuration mismatch occurs.
Verifying Auto Image Copy Verifying Auto Image Copy Use the show stack detail command to verify if there are any units in the mismatch state after the stack is formed. Memory allocation failure A memory allocation (malloc) failure occurs when the active controller does not have enough memory to run a stack unit. This failure may occur if you configure large numbers (for example, 4 K of VLANs, or STP instances (for example, 255) in the router image.
Troubleshooting secure-setup If you are unable to remove the configuration because of a multi-slot trunk configuration, you must first manually remove the multi-slot trunk configuration. 3. When you have successfully deleted the mismatched stack unit, a re-election is triggered, and the active controller learns the correct module configuration from the standby controller or from other stack members. No reload is required.
More about traditional stack technology More about traditional stack technology This section discusses stacking technology in greater detail than the information presented in the previous sections. Configuration, startup configuration files, and stacking flash Stacking system behavior is defined by the runtime configuration, which can be displayed using the show run command. The write memory command stores the runtime configuration in a flash file called startup-config.txt.
Traditional stack topologies Traditional stack topologies Brocade traditional stack technology supports both linear and ring stack topologies. Because the unicast switching follows the shortest path in a ring topology, this topology offers the strongest redundancy. When the ring is broken, the stack recalculates the forwarding path the resumes the flow of traffic within a few seconds.
Standby controller Standby controller In addition to the active controller, another stack member is elected as the standby controller. After a default interval of 30 seconds, the standby controller takes over if the active controller fails. If hitless stacking failover is enabled, the standby unit can take over immediately without reloading any unit. NOTE Because it can take as long as 20 seconds to age out a neighbor, the standby takeover period may last up to 50 seconds.
Active controller and standby controller resets Active controller and standby controller resets If the active controller is reset or removed from the stack, the entire stack reloads and active controller and standby controller elections are initiated. If the unit functioning as the previous active controller is no longer part of the stack, the standby controller unit becomes the new active controller.
Supported hitless stacking events • • Addition or removal of units in a stack Removal or disconnection of the stacking cable between the active and standby controllers During such events, the standby controller takes over the active role and the system continues to forward traffic seamlessly, as if no failure or topology change has occurred.
Traditional Stacking TABLE 18 Hitless-supported services and protocols Traffic type Supported protocols and services Impact Layer 2 switched traffic, including unicast and multicast • Layer 2 switched traffic is not impacted during a hitless stacking event. All existing switched traffic flows continue uninterrupted. • • • • + System-level • • + Layer 4 • • • • • • • • • • • • • • • • • 98 802.1p and 802.1Q 802.3ad - LACP 802.3af - PoE 802.
Traditional Stacking TABLE 18 Hitless-supported services and protocols (Continued) Traffic type Supported protocols and services Impact Management traffic N/A All existing management sessions (SNMP, TELNET, HTTP, HTTPS, FTP, TFTP, SSH etc.), are interrupted during the switchover process. All such sessions are terminated and can be reestablished after the new active controller takes over.
Traditional Stacking TABLE 18 Hitless-supported services and protocols (Continued) Traffic type Supported protocols and services Impact Security • Supported security protocols and services are not impacted during a switchover or failover, with the following exceptions: • • • • • • • 802.
Hitless stacking configuration notes and feature limitations TABLE 18 Hitless-supported services and protocols (Continued) Traffic type Supported protocols and services Impact controller will reauthenticate 802.1X or MDPA sessions that were being forwarded in hardware. The hardware continues to forward them (even with dynamic VLAN) while re-authentication occurs.
What happens during a hitless stacking switchover or failover • • • After a switchover or failover, the Syslog may contain invalid (non-existent) port numbers in messages such as “Interface portnum state up.” This is because some messages from the old active controller will remain in the Syslog after a switchover or failover. Failover for devices connected to the management port is not supported.
Standby controller role in hitless stacking over as the active controller. In the event of a switchover, the standby controller will pick up where the active module left off, without interrupting data traffic. After baseline synchronization, any new events that occur on the active controller will be dynamically synchronized on the standby controller.
Runtime configuration mismatch If more than one unit in the stack meets this criteria, the standby controller is chosen according to the following criteria, in the order shown: • • • • Priority - The unit with the highest priority value. Current standby - The unit that is currently the standby controller. Bootup master - The unit that was the active controller before the stack was reloaded. Bootup standby - The unit that was the standby controller before the stack was reloaded.
Traditional Stacking The following figure illustrates hitless stacking support during stack formation. Operational stages 1 and 2 are also shown in this illustration.
Traditional Stacking The following figure illustrates hitless stacking support during a stack merge.
Hitless stacking default behavior The following figure illustrates hitless stacking support in a stack split. FIGURE 15 Hitless stacking support in a stack split Hitless stacking default behavior Hitless stacking is disabled by default. When disabled, the following limitations are in effect: • • If a failover occurs, every unit in the stack will reload Manual switchover is not allowed.
Enabling hitless stacking • • • Internal switchover resulting from a priority change is blocked until the entire stack is reloaded or hitless stacking is enabled. A priority change will trigger an election, but the newly elected winner will not immediately assume its role. If there is no active controller after a reload, the bootup standby will assume the active role after reloading every unit in the stack, including itself.
Displaying pending device roles 8 S FCX648 active 0000.0077.7980 128 local Ready active standby +---+ +---+ +---+ -2/1| 8 |2/2--2/2| 3 |2/1--2/1| 5 |2/2| +---+ +---+ +---+ | | | |-------------------------------------| Standby u5 - No hitless failover.
Hitless stacking failover example Hitless stacking failover example FIGURE 16 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 and standby controllers without reloading the stack and without any packet loss to the services and protocols that are supported by hitless stacking. A switchover is activated by the stack switch-over CLI command .
Executing a hitless stacking switchover Hitless switchover can be used by a system administrator, for example, to perform maintenance on a controller that has been functioning as the active controller. For a description of the events that occur during a hitless stacking switchover, refer to What happens during a hitless stacking switchover or failover on page 102. For a description of this feature’s impact on major system functions, refer to Supported hitless stacking protocols and services on page 97.
Traditional Stacking The following figure illustrates a hitless stacking switchover triggered by the stack switch-over command.
Traditional Stacking The following figure illustrates a hitless stacking switchover when the active controller goes down then comes back up. The stack in this example has user-configured priorities.
Traditional Stacking The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value of the standby controller.
Traditional Stacking The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value of one of the stack members.
Displaying information about hitless stacking The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value for two of the stack members. FIGURE 21 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.
Displaying information about stack failover 4 S FCX624S member 0000.0000.0000 128 reserve active standby +---+ +---+ +---+ -1/3| 1 |1/5--1/5| 2 |1/3--1/5| 3 |1/3| +---+ +---+ +---+ | | | |-------------------------------------| Standby unit 2: protocols ready, can failover or manually switch over Current stack management MAC is 0000.0000.1100 NOTE The text “can failover or manually switch over” was added for hitless stacking failover and switchover.
Syslog messages To view the System log or the traps logged on an SNMP trap receiver, enter the show log command at any level of the CLI. The following example output shows what the log might look like after a switchover or assignment of the standby controller.
Traditional Stacking Message Stack: Stack is operational due to FAIL-OVER Explanation Indicates that a failover has occurred. Message Level Informational To view the System log or the traps logged on an SNMP trap receiver, enter the show log command at any level of the CLI. The following example output shows what the log might look like after a switchover or assignment of the standby controller.
Syslog messages 120 FastIron Ethernet Switch Stacking Configuration Guide 53-1003090-02
Mixed Stacking ● Supported mixed stacking features...............................................................................121 ● Mixed stacking overview............................................................................................... 121 ● Configuring basic mixed stacking..................................................................................125 ● Basic mixed stacking configuration examples...............................................................
Mixed stacking devices Mixed stacking devices A mixed stack contains ICX 6610 devices and ICX 6450 devices. ICX 6610 devices form the backbone of the mixed stack. ICX 6450 devices are peripheral units that connect to the backbone and to other peripheral units. A mixed stack can contain one or two ICX 6610 devices and one to six ICX 6450 devices. ICX 6610 devices have full Layer 2 and Layer 3 unicast and multicast capabilities.
Mixed stacking terms topology with six ICX 6450 devices connected as peripherals. Each ICX 6610 device is directly connected to each ICX 6450 device. Each ICX 6450 device is connected to two ICX 6610 devices. FIGURE 22 Star Topology for ICX 6610 and ICX 6450 Other stacking topologies The following mixed stacking topology comprises of two ICX 6610 devices in a ring topology with six peripheral devices. Each ICX 6610 device has three peripheral links.
Mixed stacking software image requirements TABLE 20 Mixed stacking terms Term Definition Active controller ICX 6610 device. Backbone or core Topology formed by ICX 6610 devices. Backbone or core unit ICX 6610 device. Peripheral port or trunk (peri-port or peri-trunk) On ICX 6610 devices only, used to link to a stacking port or trunk of an ICX 6450 device. Peripheral unit ICX 6450 device.
Configuring basic mixed stacking Configuring basic mixed stacking There are three ways to configure a mixed stack: the secure-setup utility, automatic configuration, and manual configuration. Method Description Secure-setup utility An interactive utility requiring some selection on the part of the user but minimal use of CLI for configuration. Automatically forms trunks. Requires configuring the SFP+ ports on the ICX 6610 devices to 10 Gbps using the speed command.
Mixed Stacking 4. When prompted, specify the topology by accepting the discovered topology. Do you accept the topology (RING) (y/n)?: y The devices in the substacks are discovered. 5. When prompted, enter the number of devices (units) you want to include in the substacks. Enter the number of the desired units in the above sub stack(0-3)[0]: 3 Stack unit IDs are assigned. 6. When prompted, specify the stack unit IDs by accepting the assigned IDs.
Mixed Stacking The following example shows the configuration of a mixed stack using the secure-setup utility. The mixed stack contains two ICX 6610 devices in the backbone, and there are two substacks containing three ICX 6450 devices each.
Mixed Stacking Use the show stack command or the show stack connection command to verify the mixed stack configuration. Brocade# show stack alone: standalone, D: dynamic config, S: static config ID Type Role Mac Address Pri State Comment 1 S ICX6610-24F active 748e.f891.c5b8 128 local Ready 2 D ICX6610-48P standby 748e.f834.4800 0 remote Ready 3 D ICX6450-24 member 748e.f86d.7aa7 0 remote Ready 4 D ICX6450-24P member 748e.f8b0.7aa0 0 remote Ready 5 D ICX6450-24P member 748e.f8b0.
Configuring a mixed stack using automatic configuration 2: 2/3/8 (T3) <---> 8/2/4 Link 7: u3 -- u4, num=2 1: 3/2/1 (T0) <---> 4/2/3 2: 3/2/2 (T0) <---> 4/2/4 Link 8: u4 -- u5, num=2 1: 4/2/1 (T0) <---> 5/2/3 2: 4/2/2 (T0) <---> 5/2/4 Link 9: u6 -- u7, num=2 1: 6/2/3 (T1) <---> 7/2/1 2: 6/2/4 (T1) <---> 7/2/2 Link 10: u7 -- u8, num=2 1: 7/2/3 (T1) <---> 8/2/1 2: 7/2/4 (T1) <---> 8/2/2 CPU to CPU packets are fine (T1) (T1) (T1) (T1) (T1) (T0) (T0) (T0) (T0) between 8 units.
Automatically configuring a standby controller device in a mixed stack The following example shows the configuration of a mixed stack using the automatic configuration method in which all stack members are configured from the active controller. The mixed stack contains two ICX 6610 devices in the backbone and two substacks of three ICX 6450 peripheral devices each.
Automatically configuring peripheral devices in a mixed stack Specifying the port modules identifies the device to the active controller. Use the show runningconfig command to get port module information. You only need to specify one port module, because the active controller generates information for other modules. 3. Specify the priority. Brocade(config-unit-1)# priority 128 Priority is used in the case of a switchover between the active and standby controllers.
Manually configuring a standby controller device in a mixed stack 1. Specify the stack unit ID. Brocade# stack unit 1 2. Specify the trunks or ports on this backbone device that connect to a peripheral device in a substack. Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# peri-port peri-port peri-port peri-port exit 1/3/1 1/3/2 1/3/7 1/3/8 3. Enable stacking. 4.
Manually configuring peripheral devices in a mixed stack 1. Specify the stack unit ID. Brocade# stack unit 1 Because you are configuring each device from the device itself, and the stack is not yet formed, the stack unit ID is 1 for each device. 2. Specify the trunks or ports on this backbone device that connect to a peripheral device in a substack. Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# Brocade(config-unit-1)# 3.
Mixed Stacking Use the show running-config command to view the mixed stack configuration.
Configuration example for mixed stacking using manual configuration Standby u2 - No hitless failover. Reason: hitless-failover not configured Current stack management MAC is 748e.f8ce.bc40 Configuration example for mixed stacking using manual configuration Configuration and verification examples for a manual configuration of mixed stacking. 1. Use the show running-config command to view the mixed stack configuration. Brocade# show running-config 2.
Mixed Stacking Use the show running-config command to view the mixed stack configuration. The following example shows the configuration of a mixed stack using the manual configuration method in which all stack members are configured from each individual device. The mixed stack contains two ICX 6610 devices in the backbone and two substacks of three ICX 6450 peripheral devices each.
Configuration verification example for a stacking star topology Configuration verification example for a stacking star topology Mixed stacking star topology configuration verification example. Use the following steps to view and verify a mixed stack star topology configuration. 1. Use the show running-config command to view the star topology mixed stack configuration. 2. Use the show stack command to verify the star topology mixed stack configuration.
Mixed Stacking The following is example output from the show running-config command after a star topology mixed stack has been configured: Current configuration: ! ver 08.0.
Configuring advanced mixed stacking 2/1| 1 |2/6==2/1| 2 |2/6 +---+ +---+ active standby --+---+ --( 1 )3/1--2/1| 6 |2/3--3/1( 2 ) --+---+ --active standby --+---+ --( 1 )3/3--2/1| 4 |2/3--3/3( 2 ) --+---+ --active standby --+---+ --( 1 )3/4--2/1| 3 |2/3--3/4( 2 ) --+---+ --active standby --+---+ --( 1 )3/2--2/1| 5 |2/3--3/2( 2 ) --+---+ --Standby u2 - protocols ready, can failover or manually switch over Current stack management MAC is 748e.f834.
Recovering a pre-stacking configuration on peripheral devices NOTE You cannot upload an ICX 6450 image from a mixed stack to a TFTP server or SCP client. Recovering a pre-stacking configuration on peripheral devices Defines a recovery strategy for peripheral devices in a mixed stack. You must execute the command used for the recovery mechanism on the active controller.
Mixed Stacking In this example, ICX 6450 peripheral devices are removed from a mixed stack. The mixed stack contains two ICX 6610 devices in the backbone, and there are two substacks containing three ICX 6450 devices each. The following show stack output shows the configuration of the mixed stack before the stack unconfigure mixed-stack command is executed. The show stack command is executed on the active controller.
Mixed Stacking connect 4/2/3 stack unit 4 module 1 icx6450-24p-poe-port-management-module module 2 icx6450-sfp-plus-4port-40g-module stack-trunk 4/2/1 to 4/2/2 stack-trunk 4/2/3 to 4/2/4 stack-port 4/2/1 4/2/3 connect 3/2/1 connect 5/2/3 stack unit 5 module 1 icx6450-24p-poe-port-management-module module 2 icx6450-sfp-plus-4port-40g-module stack-trunk 5/2/1 to 5/2/2 stack-trunk 5/2/3 to 5/2/4 stack-port 5/2/1 5/2/3 connect 2/3/1 connect 4/2/1 stack unit 6 module 1 icx6450-48-port-management-module module 2
Mixed Stacking later if stack merge or stack formation happens. To remove a stack member from the configuration, use the no stack id command. Brocade# show stack alone: standalone, D: dynamic config, S: static config ID Type Role Mac Address Pri State Comment 1 S ICX6610-24F active 748e.f891.c5b8 128 local Ready 2 S ICX6610-48P standby 748e.f834.4d14 0 remote Ready 3 S ICX6450-24 member 0000.0000.0000 0 reserve 4 S ICX6450-24P member 0000.0000.0000 0 reserve 5 S ICX6450-24P member 0000.0000.
Recovering a pre-stacking configuration on peripheral devices 144 FastIron Ethernet Switch Stacking Configuration Guide 53-1003090-02
Stacking Commands ● connect..........................................................................................................................145 ● multi-peri-port ............................................................................................................... 146 ● multi-peri-trunk ............................................................................................................. 146 ● multi-stack-port .........................................................................
multi-peri-port Examples The following example connects stack unit 3 (a peripheral device) to stack unit 1 (the active controller) and to stack unit 4 (another peripheral device). Brocade(config-unit-3)# connect 1/3/1 Brocade(config-unit-3)# connect 4/2/3 History Release Command History 08.0.00a This command was introduced. multi-peri-port Changes both ends of a trunked link between a backbone device and a peripheral device to links between untrunked ports.
multi-stack-port no multi-peri-trunk stack-unit/slotnum/portnum to stack-unit/slotnum/portnum and stack-unit/slotnum/ portnum to stack-unit/slotnum/portnum Parameters stack-unit Specifies the stack unit ID. slotnum Specifies the slot number. portnum Specifies the port number in the slot. Modes Usage Guidelines Stack unit configuration mode Use this command only when the link is live. The first port in a peripheral trunk or stack trunk must be an odd-numbered port, for example, 1/3/1.
multi-stack-trunk Examples The following example changes the trunked link between stack unit 3 (a peripheral device in a mixed stack) and stack unit 4 (another peripheral device in the mixed stack) to a link between untrunked ports. Brocade(config-unit-3)# multi-stack-port 3/2/1 and 4/2/1 History Release Command History 08.0.00a This command was introduced. This command replaces the multi-port command.
peri-trunk no peri-port stack-unit/slotnum/portnum Parameters stack-unit Specifies the stack unit ID. slotnum Specifies the slot number. portnum Specifies the port number in the slot. Modes Usage Guidelines Stack unit configuration mode This command can also be used to convert a port that is already configured as part of a peripheral trunk on a backbone device to a peripheral port. Any one backbone device supports a maximum of two single (untrunked) port connections to peripheral devices.
show chassis Examples The following example specifies two trunks on a backbone device that connect to a peripheral device in a substack. The first trunk contains ports 1 and 2; the second trunk contains ports 7 and 8. In both cases, the first port in the trunk is an odd-numbered port. Brocade(config-unit-1)# peri-trunk 1/3/1 to 1/3/2 Brocade(config-unit-1)# peri-trunk 1/3/7 to 1/3/8 History Release Command History 08.0.00a This command was introduced.
show hardware mac-entry Examples The following is the sample output from the show chassis command executed on an ICX 6610 device. Brocade# show chassis The stack unit 1 chassis info: Power supply 1 not present Power supply 2 (AC - Regular) present, status ok Model Number: 23-0000143-01 Serial Number: F00E Firmware Ver: 0 Power supply 2 Fan Air Flow Direction: Back to Front Fan 1 ok, speed (auto): [[1]]<->2 Fan 2 not present Fan controlled temperature: 64.
Stacking Commands Specifies a VLAN ID of the MAC entry to be displayed. Modes User EXEC mode Privileged EXEC mode Global configuration mode Rbridge sub-configuration mode Interface sub-configuration mode Command Output The show hardware mac-entry command output displays the following information. Output field Description Total FDB entries The total number of entries in the Forwarding Database (FDB). Index The ID of the MAC entry. MacAddress The MAC address of the entry.
stack suggested-id History Release Command History 08.0.00a This command was introduced. stack suggested-id Specifies the stack unit ID for a standalone device before joining a stack. Syntax stack suggested-id stack-unit no stack suggested-id stack-unit Parameters stack-unit Specifies the numeric stack unit ID. Modes Usage Guidelines Global configuration mode The no form of this command removes the stack unit ID. The system attempts to assign a bootup ID of a device as its stack unit ID.
Stacking Commands Specifies the stack member from which the command is executed. This option is available on all stack members. clean Specifies to remove the startup configuration and reboot to a clean unit. mixed-stack Specifies to remove all peripheral ports and peripheral trunks from the ICX 6610 devices. It also specifies to recover ICX 6450 peripheral device configurations from before they were members of the mixed stack, and reload them.
Stacking Commands Mixed stack example In this example, ICX 6450 peripheral devices are removed from a mixed stack. The mixed stack contains two ICX 6610 devices in a ring configuration in the backbone. There are two substacks of three ICX 6450 devices each in the mixed stack. The following show stack output shows the configuration of the mixed stack before the stack unconfigure mixed-stack command is executed. The show stack command is executed on the active controller.
Stacking Commands 3 4 5 6 7 8 S S S S S S ICX6450-24 ICX6450-24P ICX6450-24P ICX6450-48 ICX6450-48 ICX6450-24P member member member member member member 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000 0 0 0 0 0 0 reserve reserve reserve reserve reserve reserve active standby +---+ +---+ =2/6| 1 |2/1==2/6| 2 |2/1= | +---+ +---+ | | | |------------------------| Use the show stack command to verify that peripheral devices are no longer part of the mixed stack.
tftp-server tftp-server Configures the TFTP server location where Autocopy can download a software image. Syntax tftp-server ip-address image-location path no tftp-server ip-address image-location path Command Default Parameters No TFTP server location is configured for Autocopy downloads. ip-address Specifies the IP address of the TFTP server. image-location path Specifies directory path to the software image on the TFTP server.
Stacking Commands When a stacking port is malfunctioning, the correctional steps that an active controller can take, depend on the value of this level variable. Its value can range from 0 to 3. Modes Global configuration mode Usage Guidelines NOTE • • A non-active controller is any stack unit that is not an active controller. If you use the command and set the level variable value to 1, this configuration shows in the show run command output.
