Release Notes

Extreme Campus Controller Customer Release Notes
8/6/2021 P/N: 9036846-05 Subject to Change Without Notice Page: 12 of 21
F0615-O
Known Restriction or Limitation
I.D
must be configured on a/n/ac (disable ax) until all clients will upgrade to the latest
driver.
Default router/gateway should be configured with a next hop associated with one of
the physical interfaces. Pointing the default route to the Admin interface will lead to
issues because access points will not get the correct services from the data plane.
We recommend setting the default route via data ports, and if necessary, configuring
static routes on the Admin port for administration level access.
Info
Before installing a new Extreme Campus Controller license, you must configure
Network Time Protocol (NTP) Server settings. Licensing management is dependent
on accurate NTP configuration. Configure NTP via the Extreme Campus Controller
Initial Configuration Wizard, or go to Admin > System > Network Time to configure
and verify the NTP settings.
Info
For AP deployments in remote locations where access points and controllers may
need to be discovered and connected over firewalls, a best practice is to leverage
DNS or DHCP Option 60/43 methods for zero-touch-provisioning discovery. These
methods provide direct connectivity to the defined IP address. DHCP Option 78,
which refers to the controller as a Service Location Protocol Directory Agent (SLP-
DA), requires the exchange of SLP protocol between the AP and the appliance at the
core, necessitating that UDP 427 be allowed by any firewall in the path. For such
installations, discovery over DHCP Option 78 assist is not recommended.
When using SLP, for an AP to establish connection with a controller, it must first
exchange SLP Directory Agent registration before IPSEC establishment with the
eventual controller. That means that SLP UDP 427 must be open along the path.
Further issues can occur if Network Address Translation (NAT) is involved. While this
method is popular and widely deployed within a homogenous campus, it may result in
inadvertent complications for remote connections. Therefore, it should not be used in
favor of an alternate method (DHCP 60/43, DNS, or static override).
Info
When configuring system for NTP time assignment, ensure that the NTP server is
properly configured. Incorrect time settings (like timestamps far in the future) may
adversely affect system operation, such as certificate expiration that may trigger
failures in device registration or system instability.
Info
nse0003696
Appliances in a High-Availability pair must be of the same model and at the same
exact software revision (and time synched) for configuration synchronization to
propagate to the peer. During the upgrade process of a High-Availability pair, any
configuration changes made while only one appliance has been upgraded (and
therefore resulting in a version mismatch) will not be propagated until the peer is
correspondingly upgraded to the same revision. We recommend that you NOT
perform configuration changes to one of the members of a High-Availability pair while
the peer has a different software revision.
Info
nse0005086
For High-Availability configurations, during upgrade phases or configuration restore
operations, wait until the availability link is established and synchronized before
attempting to make any new configuration changes. The Availability status will only
re-establish to Synched status when both appliances are running the exact same
firmware revision.
During upgrade periods, the Availability link will only re-establish when both the
appliance status of availability link and synchronization status can be found.
Go to:
· “Network Health" widget on the Dashboard, or
· Administration -> System -> Availability
Info
ECA-776