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.95 53-1005651-02

  • 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