Find Technical Content
  • Home
  • Ruckus Support Portal
  • Ruckus Networks
  • Table of Contents
  • Dark Mode

Powered by Titania Delivery

⚠ This cached page may be outdated. Click refresh to get the latest content.
Cached Version You are Offline

You are viewing a cached version of this page.

You are currently offline. This page was loaded from cache.

Ruckus FastIron Campus Fabric Configuration Guide, 08.0.91 53-1005606-03

  • 1 Copyright Statement
  • Preface Ruckus
    • 3 Preface
      • 3.1 Document Conventions
      • 3.2 Command Syntax Conventions
      • 3.3 Document Feedback
      • 3.4 Ruckus Product Documentation Resources
      • 3.5 Online Training Resources
      • 3.6 Contacting Ruckus Customer Services and Support
  • About This Guide_Campus Fabric
    • 4 About This Guide
      • 4.1 Supported hardware and software
      • 4.2 What’s new in this document
  • 5 Campus Fabric Overview
    • 5.1 Campus Fabric
    • 5.2 FastIron devices and Campus Fabric communication
    • 5.3 Campus Fabric roles and communication protocols
      • 5.3.1 Control and Status Protocol
    • 5.4 Campus Fabric data path
    • 5.5 Campus Fabric terminology
  • 6 Planning Considerations for a Campus Fabric Domain
    • 6.1 Campus Fabric licensing
    • 6.2 Handling SPX links with different speeds
    • 6.3 Campus Fabric scalability
    • 6.4 SPX port combinations
    • 6.5 Control bridge considerations
    • 6.6 Port extender considerations
    • 6.7 Campus Fabric topology overview
      • 6.7.1 Topologies not supported by Campus Fabric
      • 6.7.2 Topologies handled by zero-touch or SPX interactive-setup
  • 7 Campus Fabric Configuration Overview and Interactive Configuration
    • 7.1 Campus Fabric configuration overview
      • 7.1.1 Differences in Campus Fabric configuration practices
    • 7.2 Protecting a unit from being discovered
    • 7.3 Zero-touch and SPX interactive-setup topology requirements
      • 7.3.1 Invalid topologies that can be handled by SPX interactive-setup
      • 7.3.2 Special cases where a link can be removed to select all new units
      • 7.3.3 SPX LAG splits and merges
        • 7.3.3.1 Detecting new links and converting PE chains to rings
    • 7.4 Zero-touch and SPX interactive-setup deployment considerations
    • 7.5 Zero-touch configuration
      • 7.5.1 Using zero-touch to add PE units
    • 7.6 SPX interactive-setup
      • 7.6.1 Changing PE IDs with SPX interactive-setup
      • 7.6.2 Configuring SPX to move PE units without changing IDs
      • 7.6.3 Converting a stack to a PE chain or ring
      • 7.6.4 Converting a PE chain or chains to a ring
      • 7.6.5 Downloading images to new units before converting them to PEs with SPX interactive-setup or zero-touch provisioning
  • 8 Campus Fabric Manual Configuration
    • 8.1 Enabling and configuring the control bridge
      • 8.1.1 Adding a reserved PE configuration on the CB
    • 8.2 How PE units join a Campus Fabric domain
    • 8.3 Manually enabling and configuring PE units
      • 8.3.1 SPX port and LAG configuration rules
      • 8.3.2 Configuration changes in PE mode before joining the CB
      • 8.3.3 Regular, Provisional-PE, and PE mode
      • 8.3.4 Dynamic versus static SPX configuration
    • 8.4 Campus Fabric detailed manual configuration example
  • 9 Campus Fabric Considerations for Layer 2, Layer 3, Multicast, Security, and QoS
    • 9.1 Campus Fabric Layer 2 considerations
    • 9.2 Campus Fabric Layer 3 unicast considerations
    • 9.3 Campus Fabric and IP multicast considerations
      • 9.3.1 Considerations for multicast forwarding on PE units
    • 9.4 Campus Fabric security considerations
    • 9.5 Campus Fabric QoS considerations
  • 10 Campus Fabric Management
    • 10.1 Logging in through the console port
    • 10.2 Using the remote CB console
      • 10.2.1 PE console port behavior
    • 10.3 Changing the speed on an SPX link
      • 10.3.1 Converting 1-Gbps SPX links on downstream PEs to 10-Gbps links
      • 10.3.2 Converting attached PE candidate speed by physically disconnecting the units
    • 10.4 Handling nonoperational PE units
    • 10.5 Assigning an ID to a PE unit
      • 10.5.1 Assigning a PE ID that has been taken
    • 10.6 Replacing a PE unit
    • 10.7 Replacing PE units with the zero-touch or SPX interactive utility
    • 10.8 Moving a PE unit and retaining its ID (manual methods)
      • 10.8.1 Method 1: Prepare a new topology by reconfiguring PE IDs on the CB
      • 10.8.2 Method 2: Allow suggested ID or previous unit ID assignment
    • 10.9 Removing a PE ring and its configuration
    • 10.10 Configuring SPX ports and LAGs on a live system
    • 10.11 Campus Fabric (SPX) image upgrade
      • 10.11.1 Disabling or re-enabling the auto image copy process for a Campus Fabric (SPX) configuration
      • 10.11.2 Configuring a TFTP server for Campus Fabric (SPX) auto image copy
      • 10.11.3 Manual upgrade of Campus Fabric (SPX) images using a manifest file
    • 10.12 Unconfiguring the CB stack or PE units
    • 10.13 CB stack merges and breaks
    • 10.14 Displaying Campus Fabric (SPX) information
      • 10.14.1 SPX information in show running-config output
      • 10.14.2 SPX information in show configuration command output
      • 10.14.3 Displaying regular mode configuration from a PE unit
      • 10.14.4 Displaying information with the show spx command
      • 10.14.5 Using show commands for operational analysis
    • 10.15 Campus Fabric mirroring overview
      • 10.15.1 Mirroring in a Campus Fabric domain
    • 10.16 MIB support for Campus Fabric 802.1br SPX configurations
  • 11 Campus Fabric Troubleshooting
    • 11.1 Enabling and using SPX monitoring
      • 11.1.1 System validation of network changes
      • 11.1.2 Sample show spx-mon output indicating issues
      • 11.1.3 Sample show spx-mon history output
      • 11.1.4 The SPX monitoring PE join checklist
    • 11.2 Troubleshooting PE data ports
    • 11.3 Campus Fabric general troubleshooting checklist

Campus Fabric Considerations for Layer 2, Layer 3, Multicast, Security, and QoS

In this section:

  1. Campus Fabric Layer 2 considerations
  2. Campus Fabric Layer 3 unicast considerations
  3. Campus Fabric and IP multicast considerations
    In a Campus Fabric domain, forwarding decisions always occur in the CB, even for incoming traffic on a PE port.
  4. Campus Fabric security considerations
  5. Campus Fabric QoS considerations

Did you find what you were looking for?

Thanks!

Ruckus Wireless

© 2026 Ruckus Wireless LLC All rights reserved.

  • Accessibility
  • Privacy & Cookies
  • Do Not Sell My Information
  • Trademarks
  • Terms
  • Feedback