No part of this content may be reproduced in any form or by any means or used to make any derivative work (such as translation,
transformation, or adaptation) without written permission from Ruckus Networks (“Ruckus”). Ruckus reserves the right to revise or change
this content from time to time without obligation on the part of Ruckus to provide notification of such revision or change.
Destination Control Statement
These products and associated technical data (in print or electronic form) may be subject to export control laws of the United States of
America. It is your responsibility to determine the applicable regulations and to comply with them. The following notice is applicable for all
products or technology subject to export control:
These items are controlled by the U.S. Government and authorized for export only to the country of ultimate destination for use by the
ultimate consignee or end-user(s) herein identified. They may not be resold, transferred, or otherwise disposed of, to any other country or to
any person other than the authorized ultimate consignee or end-user(s), either in their original form or after being incorporated into other
items, without first obtaining approval from the U.S. government or as otherwise authorized by U.S. law and regulations.
Disclaimer
THIS CONTENT AND ASSOCIATED PRODUCTS OR SERVICES ("MATERIALS"), ARE PROVIDED "AS IS" AND WITHOUT WARRANTIES
OF ANY KIND, WHETHER EXPRESS OR IMPLIED. TO THE FULLEST EXTENT PERMISSIBLE PURSUANT TO APPLICABLE LAW,
RUCKUS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, FREEDOM FROM COMPUTER VIRUS,
AND WARRANTIES ARISING FROM COURSE OF DEALING OR COURSE OF PERFORMANCE. Ruckus does not represent or warrant that
the functions described or contained in the Materials will be uninterrupted or error-free, that defects will be corrected, or are free of viruses
or other harmful components. Ruckus does not make any warranties or representations regarding the use of the Materials in terms of their
completeness, correctness, accuracy, adequacy, usefulness, timeliness, reliability or otherwise. As a condition of your use of the Materials,
you warrant to Ruckus that you will not make use thereof for any purpose that is unlawful or prohibited by their associated terms of use.
Limitation of Liability
IN NO EVENT SHALL RUCKUS, ARRIS, OR THEIR OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIES, LICENSORS AND
THIRD PARTY PARTNERS, BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, EXEMPLARY OR
CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER, EVEN IF RUCKUS HAS BEEN PREVIOUSLY ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES, WHETHER IN AN ACTION UNDER CONTRACT, TORT, OR ANY OTHER THEORY ARISING FROM
YOUR ACCESS TO, OR USE OF, THE MATERIALS.
If you are dissatisfied with the Materials or with the associated terms of use, your sole and exclusive remedy is to discontinue their use.
Because some jurisdictions do not allow limitations on how long an implied warranty lasts, or the exclusion or limitation of liability for
consequential or incidental damages, some of the above limitations may not apply to you.
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. Other names and brands mentioned in these materials may be claimed as the property of others.
Wi-Fi Alliance®, Wi-Fi®, the Wi-Fi logo, the Wi-Fi CERTIFIED logo, Wi-Fi Protected Access® (WPA), the Wi-Fi Protected Setup logo, and
WMM® are registered trademarks of Wi-Fi Alliance. Wi-Fi Protected Setup™, Wi-Fi Multimedia™, and WPA2™ are trademarks of Wi-Fi
Alliance.
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-113
Notes, Cautions, and Warnings.......................................................................................................................................................9
Online Training Resources.................................................................................................................................................................... 10
Contacting Ruckus Customer Services and Support............................................................................................................................11
What Support Do I Need?.............................................................................................................................................................11
Open a Case.................................................................................................................................................................................11
About This Guide........................................................................................................................................................................................ 13
What’s new in this document................................................................................................................................................................13
How command information is presented in this guide...........................................................................................................................14
Traditional stacking...............................................................................................................................................................................15
Network management and stack configuration............................................................................................................................. 16
Switching and routing advantages................................................................................................................................................ 16
Brocade traditional stacking terminology.............................................................................................................................................. 19
Stack unit roles............................................................................................................................................................................. 19
Building a Stack.......................................................................................................................................................................................... 21
Planning to build a traditional stack...................................................................................................................................................... 21
Traditional stack requirements.......................................................................................................................................................21
Brocade traditional stacking topologies.........................................................................................................................................21
FastIron stacking distances and optics by device..........................................................................................................................21
Traditional stacking configuration guidelines.................................................................................................................................. 25
Planning to build a stack with 802.1br switch port extender capability..................................................................................................25
Traditional stack construction methods................................................................................................................................................ 26
The secure-setup utility................................................................................................................................................................. 26
Using secure-setup to configure a traditional stack in a ring topology............................................................................................27
Scenario 2 - Automatically configuring a three-member traditional stack in a ring topology........................................................... 35
Scenario 3 - Manually configuring a three member traditional stack in a ring topology...................................................................39
Verifying a traditional stack configuration.............................................................................................................................................. 40
Displaying information on stack connections........................................................................................................................................ 42
Traditional Stacking by Device..................................................................................................................................................................... 45
Reconfiguring ICX 7250 1-Gbps ports as 10-Gbps ports.............................................................................................................. 48
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-115
Changing default ports on the ICX 7250........................................................................................................................................48
Displaying basic information for an ICX 7250 stack....................................................................................................................... 51
Displaying detailed information for an ICX 7250 stack................................................................................................................... 52
Configuring 10-Gbps stacking ports on the ICX 7450................................................................................................................... 58
Creating stacking trunks on the ICX 7450..................................................................................................................................... 60
Displaying basic information for an ICX 7450 stack....................................................................................................................... 71
Displaying details for an ICX 7450 stack........................................................................................................................................72
Installing the ICX 7750 in a remote stack.......................................................................................................................................78
ICX 7750 trunk formation during secure-setup.............................................................................................................................. 82
Removing stacking ports from an ICX 7750.................................................................................................................................. 86
Creating an ICX 7750 stacking trunk in a production environment.................................................................................................86
Converting an ICX 7750 trunk to a port connection in a live stack................................................................................................. 87
Restoring a data port from an ICX 7750 trunk in a live stack......................................................................................................... 87
Displaying basic information for an ICX 7750 stack....................................................................................................................... 88
Displaying details for an ICX 7750 stack........................................................................................................................................88
Supported hitless stacking protocols and services............................................................................................................................... 93
Hitless stacking configuration notes and feature limitations...................................................................................................................95
What happens during a hitless stacking switchover or failover..............................................................................................................95
Real-time synchronization among all units in a stack..................................................................................................................... 95
Standby controller role in hitless stacking............................................................................................................................................. 96
Support during stack formation, stack merge, and stack split.............................................................................................................. 98
Executing a hitless stacking switchover.......................................................................................................................................102
Displaying information about hitless stacking......................................................................................................................................106
Displaying information about stack failover.................................................................................................................................. 107
Displaying information about link synchronization status..............................................................................................................107
Syslog messages for hitless stacking failover and switchover............................................................................................................. 108
Traditional Stack Management.................................................................................................................................................................. 111
Managing a traditional stack through one IP address..........................................................................................................................111
Enabling or disabling stacking mode.................................................................................................................................................. 111
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........................................................................................................................................... 113
Traditional stack CLI commands................................................................................................................................................. 114
Configuring default ports on FastIron devices.....................................................................................................................................115
Traditional stack management MAC address......................................................................................................................................115
Manually allocating the traditional stack MAC address................................................................................................................ 116
Traditional stack device roles and elections........................................................................................................................................ 117
Active controller.......................................................................................................................................................................... 117
Active controller and standby controller elections........................................................................................................................ 118
Active controller and standby controller resets............................................................................................................................ 119
Standby controller selection based on priority configuration........................................................................................................ 120
Traditional stack unit priority............................................................................................................................................................... 121
Changing the priority of a stack unit............................................................................................................................................ 122
Traditional stack software images.......................................................................................................................................................122
Confirming traditional stack software versions.............................................................................................................................122
Minor mismatch for stack units................................................................................................................................................... 123
Major mismatch for stack units................................................................................................................................................... 124
Configuration mismatch for stack units....................................................................................................................................... 124
Auto Image Copy for stack units................................................................................................................................................. 126
Copying the flash image to a stack unit from the active controller................................................................................................127
Configuring stacking trunks in a live environment................................................................................................................................127
Error messages encountered when configuring a stacking trunk................................................................................................. 128
Adding, removing, or replacing units in a traditional stack...................................................................................................................129
Installing a new unit in a traditional stack using secure-setup...................................................................................................... 129
Installing a new unit using static configuration............................................................................................................................. 129
Removing a unit from a traditional stack......................................................................................................................................130
Replacing traditional stack units.................................................................................................................................................. 130
Moving a unit to another stack.................................................................................................................................................... 131
Removing an active controller from a powered stack...................................................................................................................131
Configuration notes for renumbering stack units .........................................................................................................................132
Reloading a stack unit........................................................................................................................................................................132
Managing traditional stack partitioning................................................................................................................................................133
Merging traditional stacks.................................................................................................................................................................. 133
Unconfiguring a traditional stack........................................................................................................................................................ 134
Syslog, SNMP, and traps for stack units............................................................................................................................................. 135
Configuring SNMP for a traditional stack.....................................................................................................................................135
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-117
SNMP engine IDs for stackable devices...................................................................................................................................... 135
Displaying traditional stack information...............................................................................................................................................135
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 .......................................................................................................................... 140
Displaying general or detailed information about stack members.................................................................................................142
Displaying IPC statistics for a stack.............................................................................................................................................144
Displaying reliable IPC statistics for stack units............................................................................................................................145
Displaying information about stack neighbors............................................................................................................................. 146
Displaying stack port information................................................................................................................................................ 146
Displaying stacking port statistics................................................................................................................................................147
Displaying stacking port interface information..............................................................................................................................147
MIB support for traditional stack configurations..................................................................................................................................148
Traditional Stack Troubleshooting.............................................................................................................................................................. 149
Problems commonly diagnosed with stack formation.........................................................................................................................149
Background problem diagnosis..........................................................................................................................................................149
Troubleshooting an unsuccessful stack build......................................................................................................................................150
Troubleshooting unit replacement issues............................................................................................................................................ 153
Checking hardware after an upgrade failure........................................................................................................................................153
Configuration, startup configurationfiles, and stacking flash...............................................................................................................154
Stacking unit role transition considerations.........................................................................................................................................155
Port down and aging..........................................................................................................................................................................155
•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
ConventionDescriptionExample
monospace
boldUser interface (UI) components such
italics
Identifies command syntax
examples.
as screen or page names, keyboard
keys, software buttons, and field
names
Publication titlesRefer to the
device(config)# interface ethernet 1/1/6
On the Start menu, click All Programs.
Ruckus Small Cell Release Notes
for more information
Notes, Cautions, and Warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of increasing severity of potential
hazards.
NOTE
A NOTE provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.
CAUTION
A CAUTION statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware,
software, or data.
DANGER
A DANGER statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels
are also attached directly to products to warn of these conditions or situations.
Command Syntax Conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of parameters and their logical
relationships.
Convention
bold textIdentifies command names, keywords, and command options.
Description
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-119
Preface
Document Feedback
ConventionDescription
italic
textIdentifies a variable.
[ ]
{ x | y | z }A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select
x | yA vertical bar separates mutually exclusive elements.
< >
...Repeat the previous element, for example,
\Indicates a “soft” line break in command examples. If a backslash separates two lines of a command input,
Syntax components displayed within square brackets are optional.
Default responses to system prompts are enclosed in square brackets.
one of the options.
Nonprinting characters, for example, passwords, are enclosed in angle brackets.
member[member
enter the entire command at the prompt without the backslash.
...].
Document Feedback
Ruckus is interested in improving its documentation and welcomes your comments and suggestions.
You can email your comments to Ruckus at: docs@ruckuswireless.com
When contacting us, please include the following information:
•Document title and release number
•Document part number (on the cover page)
•Page number (if appropriate)
•For example:
–Ruckus Small Cell Alarms Guide SC Release 1.3
–Part number: 800-71306-001
–Page 88
Ruckus Product Documentation Resources
Visit the Ruckus website to locate related documentation for your product and additional Ruckus resources.
Release Notes and other user documentation are available at https://support.ruckuswireless.com/documents. You can locate
documentation by product or perform a text search. Access to Release Notes requires an active support contract and Ruckus Support
Portal user account. Other technical documentation content is available without logging into the Ruckus Support Portal.
White papers, data sheets, and other product documentation are available at https://www.ruckuswireless.com.
Online Training Resources
To access a variety of online Ruckus training modules, including free introductory courses to wireless networking essentials, site surveys,
and Ruckus products, visit the Ruckus Training Portal at https://training.ruckuswireless.com.
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 https://www.ruckuswireless.com and select Support.
What Support Do I Need?
Technical issues are usually described in terms of priority (or severity). To determine if you need to call and open a case or access the selfservice resources use the following criteria:
•Priority 1 (P1)—Critical. Network or service is down and business is impacted. No known workaround. Go to the Open a Case
section.
•Priority 2 (P2)—High. Network or service is impacted, but not down. Business impact may be high. Workaround may be available.
Go to the Open a Case section.
•Priority 3 (P3)—Medium. Network or service is moderately impacted, but most business remains functional. Go to the Self-Service
Resources section.
•Priority 4 (P4)—Low. Request for information, product documentation, or product enhancements. Go to the Self-Service
Resources section.
Open a Case
When your entire network is down (P1), or severely impacted (P2), call the appropriate telephone number listed below to get help:
•Continental United States: 1-855-782-5871
•Canada: 1-855-782-5871
•Europe, Middle East, Africa, and Asia Pacific, toll-free numbers are available at https://support.ruckuswireless.com/contact-us and
Live Chat is also available.
Self-Service Resources
The Support Portal at https://support.ruckuswireless.com/contact-us offers a number of tools to help you to research and resolve problems
with your Ruckus products, including:
Using these resources will help you to resolve some issues, and will provide TAC with additional data from your troubleshooting analysis if
you still require assistance through a support case or RMA. If you still require help, open and manage your case at https://
support.ruckuswireless.com/case_management
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1111
•What’s new in this document................................................................................................................................... 13
•How command information is presented in this guide..............................................................................................14
Supported hardware
The following devices from the Ruckus FastIron product family support stacking in FastIron release 08.0.40 and later releases:
•Ruckus ICX 7250 Series (ICX 7250)
•Ruckus ICX 7450 Series (ICX 7450)
•Ruckus ICX 7750 Series (ICX 7750)
For information about the specific models and modules supported in a product family, refer to the hardware installation guide for that
product family.
What’s new in this document
The following tables provide descriptions of new information added to this guide for FastIron software release 08.0.40, 08.0.40a, and
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. The
change first appears in the
TABLE 2 Summary of enhancements in FastIron release 8.0.40b
FeatureDescriptionLocation
ICX 7750 simultaneous front and rear stacking ICX 7750 module 2 and module 3 can be used for
TABLE 3 Summary of enhancements in FastIron release 8.0.40a
FeatureDescriptionLocation
Long-distance stacking capability40-Gbps eSR4 optics are available on the ICX 7750
TABLE 4 Summary of enhancements in FastIron release 8.0.40
FeatureDescriptionLocation
Long-distance stacking capabilityMore models now support stacking distances of up
and ICX 7450. A 40-Gbps bi-directional optic option
is available for the ICX 7750. The bi-directional
option is available for data-only use on the ICX 7450
as well. A table showing 4 X 10-Gbps LR optic
options for the ICX 7450 has also been added.
to 10 KM using LR4 optics.
on page 73.
Refer to FastIron stacking distances and optics by
device on page 21.
Refer to FastIron stacking distances and optics by
device on page 21.
.
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1113
About This Guide
How command information is presented in this guide
TABLE 4 Summary of enhancements in FastIron release 8.0.40 (continued)
FeatureDescriptionLocation
12-port stacking on the ICX 7750Two six-port trunks, one on the front and one on the
rear of the ICX 7750, can be configured
simultaneously.
Hitless stacking merge enhancementsWith hitless failover enabled, active controller and
standby controller elections for two-member stacks
are based on slightly different criteria. The changes
reduce traffic disruption during a reset and better
support two-unit stacking.
ICX 7450-32PThe new ICX 7450-32P model supports 1 Gbps/10
Mbps/100 Mbps on the first 24 ports as other ICX
7450 models. On ports 25 through 32, the new
model supports 2.5 Gbps/1 Gbps/100Mbps
operation.
Switch Port Extender (SPX)
(also known as Campus Fabric)
SPX configures an ICX 7750 in a traditional stack to
serve as a control bridge (CB) for attached ICX 7450
units configured as port extenders (PEs). This makes
network management from a single point possible
and extends port capacity to 768 PE ports.
Refer to ICX 7750 stack configuration overview
on page 73.
Refer to Active controller and standby controller
elections on page 118, Traditional stack unit
priority on page 121, and Hitless stacking
behavior on page 91.
Related changes occur throughout the guide. For
detailed information on the new hardware, refer to
the
Brocade ICX 7450 Switch Hardware
Installation Guide
Refer to Campus Fabric on page 16 and
Planning to build a stack with 802.1br switch port
extender capability on page 25 for an
introduction. Refer to the new
Switch Port Extender Configuration Guide
information on topology and configuration.
.
Brocade FastIron
for
How command information is presented in this guide
For all new content supported in FastIron release 08.0.20 and later, command information is documented in a standalone command
reference guide.
In the
Ruckus FastIron Command Reference
parameters, mode, usage guidelines, examples, and command history.
NOTE
Many commands introduced before FastIron release 08.0.20 are also included in the guide.
, the command pages are in alphabetical order and follow a standard format to present syntax,
•Brocade traditional stacking terminology................................................................................................................. 19
Traditional stacking
A stack is a group of devices that operate as a single chassis.
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.
The members of a traditional stack may be located together. For example, Top-of-rack switches can form a stack that acts as a single
switch to manage data center access. Stack members can be physically separated, and the distance between stacking members depends
on the type of connector cables used.
Certain fiber optic options increase the potential distance between stacks, which allows members of the same stack to reside in different
wiring closets, on different floors of one building, or in different buildings across the campus as illustrated in the following figure. Refer to
FastIron stacking distances and optics by device on page 21 for more information.
Brocade stackable devices are connected either through dedicated stacking ports or through ports that can be configured for either
stacking or data. The location of stacking ports and configuration options differ by device type. Refer to the section on each device type for
more information.
FIGURE 1 Distributed campus stacking topology
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1115
Stacking Overview
Campus Fabric
Network management and stack configuration
Even when all the switches within a stack are physically distributed, you can manage them as a single entity, enabling one-touch
configuration changes via a single IP address.
The active controller manages the other stack units. It maintains the information database for all stack members and downloads software
images as needed to all stack units. Each stack also has a standby controller for stack redundancy, and the stack can fail over seamlessly
to the standby.
Configuring the stack through the stack secure-setup utility is straightforward and secure. Custom configuration can be combined with
automated setup if, for example, you want to add units, move stacking ports, create trunks, or transform a default stacking port into a data
uplink port.
Switching and routing advantages
Packet switching between ports on stack units is handled by the hardware. All protocols operate with traditional stacking in the same way
as on a chassis system.
You can use stack connections to link distributed switches instead of standard inter-switch links with Layer 2 Spanning Tree Protocol (STP)
or Layer 3 routing. Using stack connections has significant advantages:
•Layer 2 simplicity. Stack links do not need to be considered as part of the overall network topology, which means that they can be
used to provide resiliency, and Layer 3 routing is not needed to manage trafficflows.
•No closed links. Because the stack links are internal to the switches, they are not seen as part of a Layer 2 network. This means
that all links can remain open and can be used to carry traffic simultaneously, maximizing throughput.
•Fast failover. The rapid detection and recovery techniques used on stack links mean that failure of a link or a switch results in
hitless failover, with no impact on user services.
The next section describes Switch Port Extender technology, which is based on an ICX 7750 core stack. Refer to the
Switch Port Extender Configuration Guide
for more information.
Brocade FastIron
Campus Fabric
Campus Fabric is sometimes referred to as Switch Port Extender (SPX).
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. The ICX 7750 control bridge (CB) provides a single point of management for the extended network. Active
and standby controller functions are retained and continue to provide hitless recovery as well as extended administrative functions. Campus
Fabric greatly increases the number of access devices that the network can support. The distributed CB at the center of Campus Fabric
architecture manages PE units and hundreds to thousands of ports at the network edge.
PE units are standards-based devices. Typically lower in cost, PE units rely on the CB for most network functions. As the network expands,
new PE units can be detected and added to the network automatically using defined Campus Fabric communication protocols. PE units
also inherit Premium-license features from the CB, which further reduces cost.
Campus Fabric architecture simplifies network management by unifying core, aggregation, and access functions. As illustrated in the
following figure, a core stack (distributed chassis) serving as the CB connects to downstream Campus Fabric (PE) units that aggregate large
numbers of access devices.
FIGURE 2 Campus Fabric domain build-out from an ICX 7750 CB stack
Stacking Overview
Campus Fabric
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-1117
Stacking Overview
Brocade stackable models
FIGURE 3 Distributed campus network formed from connected Campus Fabric domains
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)
units. Refer to the
Refer to the following sections for information on the ICX 7250:
•ICX 7250 stacking topologies on page 46.
•ICX 7250 stack configuration overview on page 45.
Refer to the following sections for information on the ICX 7450:
•ICX 7450 stacking topologies on page 54.
•ICX 7450 stack configuration overview on page 53
•Planning to build a stack with 802.1br switch port extender capability on page 25.
Refer to the following sections for information on the ICX 7750:
•ICX 7750 stacking topologies on page 74.
•Configuring an ICX 7750 traditional stack on page 73
•Planning to build a stack with 802.1br switch port extender capability on page 25.
For information about physical installation of each type of device, refer to the appropriate hardware installation guide.
Brocade FastIron Switch Port Extender Configuration Guide
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
Refer to the
extender (SPX) capability.
Stack unit roles
•Active controller - Handles stack management and configures all system- and interface-level features.
–Future active controller - The unit that will take over as active controller after the next reload, if its priority has been changed to
•Standby controller - The stack member with the highest priority after the active controller. The standby controller takes over if the
current active controller fails.
•Stack member - A unit functioning in the stack in a capacity other than active controller or standby controller.
•Stack unit - Any device functioning within the stack, including the active controller and standby controller.
–Upstream stack unit - An upstream unit is connected to the first stacking port on the active controller. (The left port as you
–Downstream stack unit - A downstream unit is connected to the second stacking port on the active controller. (The right port
Brocade FastIron Switch Port Extender Configuration Guide
the highest priority. When a priority for a stack unit is changed to be higher than the existing active controller, the takeover
does not occur immediately to prevent disruptions in stack operation.
face the stacking ports.)
as you face the stacking ports.)
for terms specific to IEEE 802.1br and switch port
NOTE
The terms "upstream port" and "downstream port" have special meanings in an 802.1br SPX configuration. Refer to the
FastIron Switch Port Extender Configuration Guide
for more information.
Stacking terms
•Bootup role - The role a unit takes during the boot sequence. This role can be standalone, active controller, standby controller, or
stack member. The active controller or a standalone unit can access the full range of the CLI. Until a stack is formed, the local
consoles on the standby controller and stack members provide access to a limited form of the CLI, such as the show stack and a
few debug commands. When the stack is formed, all local consoles are directed to the active controller, which can access the
entire CLI. The last line of output from the show version command indicates the role of a unit (except for standalone units) as
shown in the following example:
My stack unit ID = 1, bootup role = active
•Clean unit - A unit that contains no startup flashconfiguration or runtime configuration. To erase old configuration information,
enter the erase startup-cong command and reset the unit.
•Control path - A path across stacking links dedicated to carrying control traffic such as commands to program hardware or
software image data for upgrades. A stack unit must join the control path to operate fully in the stack.
•Default ports - FastIron devices use the default-ports command to define stacking port candidates.
•Dynamic configuration - A unit configuration that is dynamically learned by a new stack unit from the active controller. A dynamic
configuration disappears when the unit leaves the stack.
•Interprocessor Communications (IPC) - The process by which proprietary packets are exchanged between stack unit CPUs.
Brocade
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1119
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.
•Non-Functioning stack unit - A stack unit that is recognized as a stack member, and is communicating with the active controller
over the Control Path, but is in a non-functioning state. A non-functioning stack unit will drop or discard traffic from non-stacked
ports. This may be caused by an image or configuration mismatch.
•Reserved / provisional unit - A unit configuration number that has no physical unit associated with it.
•Secure-setup - A software utility that establishes a secure stack.
•Sequential connection - Stack unit IDs, beginning with the active controller, are sequential. For example, 1, 3, 4, 6, 7 is sequential
if active controller is 1. 1, 7, 6, 4, 3 are non-sequential in a linear topology, but become sequential in a ring topology when counted
from the other direction as: 1, 3, 4, 6, 7. Gaps in numbering are allowed.
•Stack path - A data path formed across the stacking links to determine the set of stack members that are present in the stack
topology, and their locations in the stack.
•Stack slot - A
slot
in a stack is synonymous with a
line model
in a chassis.
•Stack topology - A contiguously-connected set of stack units in an IronStack that are currently communicating with each other. All
units that are present in the stack topology appear in output from the show stack command.
•Stacking link - A cable that connects a stacking port on one unit to a stacking port on another unit.
•Stacking port - A physical interface on a stack unit that connects a stacking link. Stacking ports are point-to-point links that
exchange proprietary packets. Stacking ports cannot be configured for any other purpose while operating as stacking ports. The
number of available stacking ports depends on the platform. Some ports can be configured as either stacking ports or regular
data ports. Refer to the hardware installation guide for the specific device for more information.
•Standalone unit - A unit that is not enabled for stacking, or an active controller without any standby controller or stack members.
•Static configuration - A configuration that remains in the database of the active controller even if the unit it refers to is removed
from the stack. Static configurations are derived from the startup configurationfile during the boot sequence, are manually
entered, or are converted from dynamic configurations after a write memory command is issued.
•Trunked stacking port (trunk) - A trunk consists of multiple stacking ports and is treated as one logical link. It provides more
bandwidth and better resilience than individually connected ports.
•Unit replacement - The process of swapping out a unit with a clean unit. No configuration change is required.
•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.
Software requirements
All units in a traditional stack must be running the same software version.
Maximum configurationfile size for any stack is 1 MB.
Traditional stack requirements
Traditional stacks must contain devices of the same type or product line. For example, a traditional stack cannot combine ICX 7250, ICX
7450, and ICX 7750 devices. However, a traditional stack can contain any combination of devices from the same product line, for example,
any combination of ICX 7250 devices.
NOTE
A core stack for an 802.1br (SPX) configuration is a traditional stack that contains only ICX 7750 devices, although the stack may
contain different types of ICX 7750 devices. Refer to the
information.
Brocade FastIron Campus Fabric Configuration Guide
for more
Brocade traditional stacking topologies
Brocade traditional stacking technology supports linear and ring 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. Unicast switching follows the shortest path in a ring topology. When the ring is broken,
the stack recalculates the forwarding path and then resumes the flow of traffic within a few seconds.
In a ring topology, all stack members must have two stacking ports; however, in a linear topology, both end units use only one stacking
port, leaving the other port available as a data port.
FastIron stacking distances and optics by device
Because Brocade devices use Ethernet for the inter-switch stack connections, the deployment options are greatly increased. If standard
copper stacking cables are used, the inter-switch connections can be up to 5 meters, which is usually sufficient for locally distributed
stacks, such as in Top-of-Rack (ToR) applications. For broader distribution, fiber-optic cables should be used, allowing a stack to be
deployed across multiple physical locations, such as in the wiring closets of an office building, or in different buildings on a campus.
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1121
Building a Stack
Planning to build a traditional stack
Cables that support different distances can be combined in the same stack. For example, you can use LR4 Single Mode Fiber (SMF) optics
at both ends of a stacking connection, and the maximum distance is extended to 10 kilometers. Other stacking ports in the same stack can
use other optics, such as SR4, at both ends. The maximum distance for such a connection is 100 meters.
NOTE
The same optics (for example, LR4) must be used on both ends of a connection. If the optics do not match on both ends, the
ports will not come up.
The following table shows copper and fiber-optic options approved for stacking and stacking distance combinations. For more information
on Brocade cable options, refer to
The Brocade Optics Family Datasheet
on the Brocade website.
TABLE 5 Copper and fiber-optic options and stacking distances
DeviceStacking portCopper optionsFiber-optic optionsFiber-optic maximum
stacking distance
ICX 77506 X 40-Gbps
Front and rear stacking
and uplink
ICX 7450 (rear)1 X 40-Gbps stacking and
uplink on slots 3 and 4
ICX 7450 (front)4 X 10-Gbps stacking on
slot 2 with the
icx7400-4x10GF module
only
ICX 72504 X 10-Gbps stacking
from dedicated or uplink
ports
4 X 10F SFP+ uplink ports:
No-PHY
4 X 10F SFP+ stacking
ports: With re-timer
capability
0.5- or 1-meter passive copper
1-, 3-, or 5-meter QSFP-QSFP
active direct-attach copper, 7 or 10meter QSFP-QSFP AOC
0.5- or 1-meter passive copper
3
1-, 3-, or 5-meter QSFP-QSFP
active direct-attach copper
1-, 3-, or 5-meter SFP+ active
direct-attach copper, 7 or 10-meter
SFP+ AOC
1-, 3-, or 5-meter active cables10GE SR SFP+
40G-QSFP-SR4100 meters
40G-QSFP-BiDi
40G-QSFP-eSR4300 meters
40G-QSFP-LR4
40G-QSFP-LR410 kilometers
40G-QSFP-SR4100 meters
40G-QSFP-eSR4300 meters
10G-SFPP-USR100 meters
10G-SFPP-SR300 meters
10G-SFPP-LR10 kilometers
10GE USR SFP+
10GE LR SFP+
1
10 kilometers for ICX
7750-26Q, ICX 7750-48C,
and ICX 7750-48F
2
devices
300 meters
100 meters
10 kilometers
Long-distance stacking ports
Only certain FastIron stacking devices support long-distance stacking. FastIron models and 40-Gbps ports that can be used for longdistance data and stacking connections are listed in the following table.
TABLE 6 FastIron long-distance 40-Gbps ports
Product and modelPorts that support 1X40-Gbps opticsLong-distance stacking ports
ICX 7450 (all models)1/3/1, 1/4/11/3/1, 1/4/1
1
LR4 optics can be used only on specified ICX 7750 ports. Refer to "Long-distance stacking ports" in this guide.
2
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.
3
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
Long-distance stacking ports are not default stacking ports. If you are using only long-distance stacking ports, you cannot use the
stack secure-setup utility to configure your stack because the secure-setup utility probes for other potential stack members only
on default stacking ports.
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.
TABLE 7 FastIron long-distance 4X10-Gbps ports
Product and model10-Gbps ports that support LR opticsLong-distance stacking ports
ICX 7450 front (all models, with 4X10GF
module)
ICX 7450 back (all models, with 4X10GF
module)
1/2/1 through 1/2/41/2/1 through 1/2/4
1/3/1 through 1/3/4 and 1/4/1 through 1/4/4 (data only)1/3/1 through 1/3/4 and 1/4/1 through
1/4/4
For general information on all long-distance stacking options for all FastIron stacking models, refer to FastIron stacking distances and optics
by device on page 21. For details on setting up for long-distance stacking, refer to Installing the ICX 7750 in a remote stack on page 78.
Displaying information on supported distances
Use the show media command to display information on stacking connections and supported distances. You can specify any interface
within a stack or SPX configuration as shown in the following examples. You can also designate a stack to display all media attached to the
stack. Without parameters, the command displays all media attached to the device.
The following example displays information for an interface with an LR4 optic.
ICX7750-48F Router# show media ethernet 4/2/6
Port 4/2/6: Type : 40GE-LR4 10km (QSFP+ LC)
Vendor: BROCADE Version: 2
Part# : 57-1000263-01 Serial#: LDJ21325C230002
The following command output is for an interface with a 40-Gbps active copper optic with a maximum distance of 10 meters.
ICX7750-48F Switch# show media ethernet 3/2/1
Port 3/2/1: Type : 40GE-Active Copper 10m (QSFP+)
Vendor: BROCADE Version: A
Part# : 57-1000306-01 Serial#: NEA11510000003S
The following output is for an interface with a 40-Gbps ESR4 optic.
ICX7750-48F Switch# show media ethernet 1/2/3
Port 1/2/3: Type : 40GE-ESR4 300m (QSFP+)
Vendor: BROCADE Version: A
Part# : 57-1000296-01 Serial#: LVA115150000004
The following example displays information about the media attached to the device.
device# show media
Port 1/1/1 : Type : 1G M-C (Gig-Copper)
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1123
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 : Type : 1G M-C (Gig-Copper)
Port 1/1/8 : Type : 1G M-C (Gig-Copper)
Port 1/1/9 : Type : 1G M-C (Gig-Copper)
Port 1/1/10: Type : 1G M-C (Gig-Copper)
Port 1/1/11: Type : 1G M-C (Gig-Copper)
Port 1/1/12: Type : 1G M-C (Gig-Copper)
Port 1/1/13: Type : 1G M-C (Gig-Copper)
Port 1/1/14: Type : 1G M-C (Gig-Copper)
Port 1/1/15: Type : 1G M-C (Gig-Copper)
Port 1/1/16: Type : 1G M-C (Gig-Copper)
Port 1/1/17: Type : 1G M-C (Gig-Copper)
Port 1/1/18: Type : 1G M-C (Gig-Copper)
Port 1/1/19: Type : 1G M-C (Gig-Copper)
Port 1/1/20: Type : 1G M-C (Gig-Copper)
Port 1/1/21: Type : 1G M-C (Gig-Copper)
Port 1/1/22: Type : 1G M-C (Gig-Copper)
Port 1/1/23: Type : 1G M-C (Gig-Copper)
Port 1/1/24: Type : 1G M-C (Gig-Copper)
Port 1/2/1 : Type : 10GE SR 300m (SFP +)
Port 1/2/2 : Type : EMPTY
Port 1/2/3 : Type : 1G Twinax 1m (SFP)
Port 1/2/4 : Type : 1G Twinax 1m (SFP)
The following example shows output for the specified stack.
device# show media stack 1
Port 1/1/1 : Type : EMPTY
Port 1/1/2 : Type : EMPTY
Port 1/1/3 : Type : EMPTY
Port 1/1/4 : Type : EMPTY
Port 1/1/5 : Type : EMPTY
Port 1/1/6 : Type : EMPTY
Port 1/1/7 : Type : EMPTY
Port 1/1/8 : Type : EMPTY
Port 1/1/9:1 : Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/9:2 : Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/9:3 : Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/9:4 : Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/10 : Type : EMPTY
Port 1/1/11:1: Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/11:2: Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/11:3: Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/11:4: Type : 4x10GE Active Copper 1m (QSFP+)
Port 1/1/12 : Type : EMPTY
Port 1/1/13 : Type : EMPTY
Port 1/1/14 : Type : EMPTY
Port 1/1/15 : Type : EMPTY
Port 1/1/16 : Type : EMPTY
Port 1/1/17 : Type : EMPTY
Port 1/1/18 : Type : EMPTY
Port 1/1/19 : Type : EMPTY
Port 1/1/20 : Type : EMPTY
Port 1/2/1 : Type : EMPTY
Port 1/2/2 : Type : EMPTY
Port 1/2/3 : Type : EMPTY
Port 1/2/4 : Type : EMPTY
Port 1/2/5 : Type : EMPTY
Port 1/2/6 : Type : EMPTY
Port 1/3/1 : Type : 40GE-SR4 100m (QSFP+)
Port 1/3/2 : Type : EMPTY
Port 1/3/3 : Type : EMPTY
Port 1/3/4 : Type : EMPTY
Port 1/3/5 : Type : EMPTY
Port 1/3/6 : Type : EMPTY
Planning to build a stack with 802.1br switch port
extender capability
If you are planning to create an 802.1br SPX configuration with an ICX 7750 core stack, there are a few considerations.
In general, Brocade traditional stacking and 802.1br SPX configuration are independent. Here are a few details to keep in mind:
•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.
•While a traditional stack may include up to 12 units, a CB stack of no more than four units is recommended.
•ICX 7750 breakout ports can be used with an 802.1br SPX configuration; however, they can be enabled only in a standalone ICX
7750 unit.
•SPX runs over LLDP protocol at Layer 2. When you enable SPX with the spx cb-enable command, the lldp run command is also
executed if LLDP has not previously been enabled.
•You will need to plan a server location from which images and manifest files can be downloaded to PE units.
•In general, ICX 7750 devices in the CB retain all capabilities. The feature set of ICX 7450 devices operating as PE units, however,
may be affected.
For detailed information on 802.1br SPX configuration, including protocol considerations, refer to the
Extender Configuration Guide
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1125
.
Brocade FastIron Switch Port
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.
There are three ways to build a traditional stack.
1.The secure-setup utility. Secure-setup gives you control over the design of your stack topology and provides security through
password verification. For the secure-setup procedure, refer to Using secure-setup to configure a traditional stack in a ring
topology on page 27.
2.Automatic stack configuration. With this method, you enter all configuration information, including the module type and the
priorities of all members into the unit you decide will be the active controller and set its priority to be the highest. When you enable
stacking on the active controller, the stack then forms automatically. This method requires that you start with clean units (except for
the active controller) that do not contain startup or runtime configurations. Refer to Scenario 2 - Automatically configuring a three-
member traditional stack in a ring topology on page 35.
3.Manual stack configuration. With this method, you configure every unit individually and enable stacking on each unit. Once the
units are connected together, they automatically operate as a traditional stack. With this method, the unit with the highest priority
becomes the active controller, and ID assignment is determined by the sequence in which you physically connect the units. Refer
to Scenario 3 - Manually configuring a three member traditional stack in a ring topology on page 39.
The secure-setup utility
NOTE
Secure-setup works for units within a single stack. It does not work across stacks.
NOTE
Long distance stacking ports are not default stacking ports. If you are using only long distance stacking ports, you cannot use the
stack secure-setup utility to configure your stack because the secure-setup utility probes for other potential stack members only
on default stacking ports.
Secure-setup lets you easily configure your entire stack through the active controller, which propagates the configuration to all stack
members. Secure-setup is the most secure way to build a traditional stack. It gives you the most control over how your stack is built. For
example, secure-setup offers three security features that prevent unauthorized devices from accessing or joining a traditional stack:
•Authentication of secure-setup packets provides verification that these packets are from a genuine Ruckus stack unit. MD5-based
port verificationconfirms stacking ports.
•A superuser password is required to allow password-protected devices to become members of a traditional stack.
•The stack disable command prevents a unit from listening for or sending stacking packets. When a unit is stack-disabled, no
other device in the network can force the unit to join a traditional stack.
Secure-setup can also be used to add units to an existing traditional stack and to change the stack IDs of stack members.
Secure-setup and the active controller
When secure-setup is issued on a unit that is not already the active controller, the unit becomes the active controller. If this unit does not
already have an assigned priority and if no other unit in the stack has a priority higher than 128, secure-setup assigns the unit a priority of
128 by default. However, if another unit in the stack has a priority of 128 or higher, secure-setup gives the active controller a priority equal to
the highest priority unit in the stack (which is by default the standby controller). When the active controller and the standby controller have
identical priorities, during a reset, the old active controller cannot reassume its role from the standby controller (which 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. If you do not want the previous active controller to remain the active controller, you can
set the same priority for both active and standby controllers (equal to or higher than128).
Using secure-setup to configure a traditional stack in a ring topology
The following figure shows three ICX 7750 stacking units connected in a ring. The secure-setup example that follows is for 12 ICX 7750
units in a ring topology. However, the procedure can be used for any stackable ICX device and any size traditional stack.
FIGURE 4 Traditional stack with ring topology
1.Connect the devices using the stacking ports and stack cabling. For more information, refer to the appropriate hardware
installation guides.
2.Power on the units.
3.Connect your console to the intended active controller. The unit through which you run secure-setup becomes the active controller
by default.
4.Issue the stack enable command on the intended active controller.
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-1127
Building a Stack
Traditional stack construction methods
5.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. Secure-setup can detect up to 11 units in
each direction (22 units total); however, you must select a total number of units that is less than the maximum stack size for the
device because the controller is also part of the stack.
NOTE
During the secure-setup process, after one minute of inactivity, authentication for stack members expires, forcing you to
restart the process.
NOTE
To exit the secure-setup, enter ^C at any time.
The following example shows the suggested discovered topology.
ICX7750-48F Router# stack secure-setup
ICX7750-48F Router# Discovering the stack topology...
Current Discovered Topology - RING
Available UPSTREAM units
Hop(s) Id Type Mac Address
1 new ICX7750-48XGF cc4e.246d.8d80
2 new ICX7750-48XGF cc4e.246d.9b00
3 new ICX7750-48XGF cc4e.246d.9c80
4 new ICX7750-20QXG cc4e.2439.2a80
5 new ICX7750-20QXG cc4e.2439.3700
6 new ICX7750-20QXG cc4e.2439.3880
7 new ICX7750-20QXG cc4e.2439.2d00
8 new ICX7750-48XGC cc4e.2439.1a00
9 new ICX7750-48XGC cc4e.2439.1680
10 new ICX7750-48XGC cc4e.2439.1d80
11 new ICX7750-48XGC cc4e.2439.1280
Available DOWNSTREAM units
Hop(s) Id Type Mac Address
1 new ICX7750-48XGC cc4e.2439.1280
2 new ICX7750-48XGC cc4e.2439.1d80
3 new ICX7750-48XGC cc4e.2439.1680
4 new ICX7750-48XGC cc4e.2439.1a00
5 new ICX7750-20QXG cc4e.2439.2d00
6 new ICX7750-20QXG cc4e.2439.3880
7 new ICX7750-20QXG cc4e.2439.3700
8 new ICX7750-20QXG cc4e.2439.2a80
9 new ICX7750-48XGF cc4e.246d.9c80
10 new ICX7750-48XGF cc4e.246d.9b00
11 new ICX7750-48XGF cc4e.246d.8d80