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
Configure Switch Adoption Rule
Specify a site when creating a switch adoption rule. The device group does not apply to switches.
1. Go to Configure > Adoption > Add.
The New Rule dialog displays.
2. To create a rule for switches, select Switch.
3. For Action, select one of the following values:
• Allow
• Deny
•
Redirect
4. Select a site.
5. Select a filter parameter, and then select .
Related Topics
Adoption Rule Filters on page 285
Configure Device Redirection on page 285
Pattern-Based Matching
In standard adoption rules, a site and device group are explicitly specified. In Pattern-Based matching,
site and device group assignment is defined based on variables that represent the FQDN and DNS-
Sux of the device. The device reports to Extreme Campus Controller. The assignment is based on the
matching criteria for the $FQDN or $DNS-SUFFIX variables.
Note
Before you define a Pattern-Based adoption rule, you must create a site and device group
using a name that will match the name defined by the variables. Coordinate your variable
definitions with the names of your existing sites and device groups. Then, create the adoption
rules configuring variables with specific index definitions that will result in a match to the site
name or device group name that you created.
An adoption rule is comprised of a filter definition and a site and device group definition. First, the rule
matches the device attributes to the defined filter criteria. Then the rule assigns those devices to a site
or device group based on the $FQDN or $DNS-SUFFIX variable values that match existing sites and
device groups.
The FQDN and DNS sux must follow a consistent format for Pattern-Based matching to be successful.
One Pattern-Based rule definition can assign devices to any number of configured sites and device
groups based on successful variable matches. When the defined pattern does not match an existing site
or device group, an error is logged and Extreme Campus Controller continues evaluating the next
adoption rule.
Examples: Variable Definitions
$FQDN[x:y]
Uses the sub-string of the Fully-Qualified Domain Name reported by the device, from character at
position x to character at position y. The first character is position 1 (not 0). The value of y must be
greater than or equal to the value of x.
Site example — Use this variable $FQDN[x:y] to specify a site. My existing site is named
SITE_RDU. I define my site variable pattern as SITE_$FQDN[6:8]. The AP reports the FQDN as
Adoption Rules
Configure
282 Extreme Campus Controller User Guide for version 5.46.03