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
Table 6: System Health Widget Best Practices (continued)
Type Field Description
Configuration WEP encryption for network
privacy detected
The Wi-Fi Alliance™ recommends against using
WEP encryption. WEP encryption is easily broken,
often taking less than a minute to break. If you
must use WEP, apply a restrictive policy to the
associated VLAN to reduce your exposure after a
breach.
Configuration Open networks detected. Networks with Open access pose a security risk
for your organization. Consider an authentication
type such as MBA or Captive Portal.
Configuration Manufacturing Certificate A Best Practice is to enforce enablement of
Extreme PKI certificate in the establishment of
secure tunnels.
Operational Certificate Authentication Pre-installed Extreme certificates allow validation
between Extreme Campus Controller and an AP.
APs that do not support signed certificates, can
provide self-signed certificates. In this case, you
must disable Enforce Manufacturing Certificate on
Extreme Campus Controller for the AP. AP
Authentication failure messages are logged in the
Extreme Campus Controller Events Log.
Configuration Multicast filters fully open Multicast trac can have a negative impact on
performance. Ensure that multicast access is
restricted per topology. See Configuring a
Multicast Rule on page 273.
Configuration Mesh Node AP configuration For a Mesh Node (non-Root) AP, a best practice is
to configure Poll Timeout for at least 60 seconds.
Configuration Mesh Root point configured to
use dynamic RF management
policy
Mesh Root APs require fixed channel assignment
for proper access point operation.
Operational Mesh AP operating on DFS
channel.
Due to DFS procedures and mandatory ‘Stay o
Channel’ periods, APs operating on DFS channels
in a Mesh topology can result in service outages.
Configuration Mesh does not support O-
Channel Scan
Note: Supported on Extreme Campus Controller
v5.16.03 with AP v7.5.1.2 or later.
Non-root APs are configured with Mesh ACS
(Automatic Channel Selection). This allows the
non-root AP to follow the channel and width of
the uplink AP. The non-root AP scans channels to
find the best path to a root AP. Preferred Root and
Preferred Neighbor settings influence the path to
the root AP.
Dashboard System Health Best Practice Widget
Extreme Campus Controller User Guide for version 5.46.03 41










