User's Guide
Table Of Contents
- Table of Contents
- Preface
- Welcome to Extreme Campus Controller
- Dashboard
- Monitor
- Sites List
- Device List
- Access Points List
- Smart RF Widgets
- Switches List
- Networks List
- Clients
- Policy
- Configure
- Network Configuration Steps
- Sites
- Add a Site
- Modifying Site Configuration
- Site Location
- Adding Device Groups to a Site
- Add or Edit a Configuration Profile
- Associated Profiles
- Associated Networks
- Mesh Point Profile Configuration
- Configure Client Bridge
- Understand Radio Mode
- Radio as a Sensor
- Advanced AP Radio Settings
- VLAN Profile Settings
- AirDefense Profile Settings
- ExtremeLocation Profile Settings
- IoT Profile Settings
- Positioning Profile Settings
- Analytics Profile Settings
- RTLS Settings
- Advanced Configuration Profile Settings
- Configuring RF Management
- Configuring a Floor Plan
- Advanced Tab
- Devices
- Networks
- Policy
- Automatic Adoption
- ExtremeGuest Integration
- AAA RADIUS Authentication
- Onboard
- Onboard AAA Authentication
- Manage Captive Portal
- Manage Access Control Groups
- Access Control Rules
- Tools
- Administration
- System Configuration
- Manage Administrator Accounts
- Extreme Campus Controller Applications
- Product License
- Glossary
- Index
The switch requires that the VLAN/I-SID mapping is unique per port per switch, therefore only one AP
per switch port is allowed.
ExtremeWireless APs connected to a Fabric-enabled switch automatically use the default management
VLAN that is configured on the switch. Moving an AP from a Fabric-enabled switch to a non Fabric-
enabled switch requires a factory default reset to connect to the new management VLAN.
Note
In a mobility scenario that includes a local and foreign Extreme Campus Controller, make sure
the Fabric Attach topology configuration is the same on each Extreme Campus Controller,
ensuring that an AP that moves between appliances has the same set of topologies.
Figure 72: Fabric Attach for FA Clients — Automated Network Services
VxLAN Topology
Extreme Campus Controller leverage VxLAN capabilities of ExtremeXOS switches to establish dierent
head-ends for tunneling trac in an enterprise. Support includes:
• Tunnel in VxLAN from AP directly to a target switch
• Bypass Extreme Campus Controller
• Abstracts interconnections.
VxLAN is a Layer 2 overlay scheme over a Layer 3 network. Overlays are called VxLAN segments and
only a VM and a physical machine (tenant) within the same segment have Layer 2 connectivity. VxLAN
segments are uniquely identified using an identifier called the VxLAN Network Identifier (VNI). The VNI
is a 24-bit identifier; therefore, an administrative domain can support up to 16 million overlay networks.
Because the scope of the MAC, originated by tenants, is restricted by the VNI, overlapping MAC
addresses across segments can be supported without trac leaking between tenant segments. When a
tenant frame traverses a VxLAN overlay network, it is encapsulated by a VxLAN header that contains
the VNI. This frame is further encapsulated in a UDP header and L2/L3 headers.
Configure
VLANS
Extreme Campus Controller User Guide for version 5.46.03 275