User's Guide

Table Of Contents

Session Persistence

Session Persistence applies to the session state on the AP. RADIUS authentication is always handled

through the appliance — this can be the local Extreme Campus Controller or a third-party appliance.

Associated clients remain unaected by a lack of connectivity to the appliance.

When using MBA or 802.1x, the authenticating appliance must be visible. When enabling MBA, the

selected ‘MBA Timeout Role’ provides the default role to which users are automatically assigned. The

role can be permissive or restricted, depending on the administrative conﬁguration. See WLAN Service

Settings on page 221. When using 802.1x, if none of the appliances are available, then likely there is no

path-to-authentication and new clients will be unable to authenticate on the wireless network. If the

network association is set to OPEN or PSK SSIDs, no authentication is required and the AP will associate

the device based on the ‘Default Non-Auth’ Role setting conﬁgured for the network.

Conﬁguring RF Management

RF Management proﬁles are AP model dependent and reusable. Default proﬁles are intended to make

RF Management easy, getting you up and running without having to conﬁgure an RF policy. However,

you can always create additional proﬁles based o of default RF Management proﬁles. The RF

Management support is dependent on the AP model.

The following AP models are supported:

• AP39xx supporting ACS Policy for RF Management

• AP4000, AP3xx, AP4xx, and AP5xx supporting Smart RF Policy for RF Management