Summit WM User Guide, Software Version 5.3 159
Enabling management traffic
If management traffic is enabled for a WM-AD, it overrides the built-in exception filters that prohibit
traffic on the Summit WM Controller data interfaces. For more information, see "Configuring filtering
rules for a WM-AD" on page 181.
To enable management traffic on a WM-AD:
1 From the main menu, click WM Access Domain Configuration. The WM Access Domain
Configuration page is displayed.
2 In the left pane WM Access Domains list, click the WM-AD you want to enable management traffic
for. The Topology tab is displayed.
3 Select the Allow mgmt traffic checkbox.
Enabling third-party APs on a WM-AD
Configuring a WM-AD for third-party APs is only available with SSID network assignment. Use this
function as part of the process defined in Chapter 8, "Working with third-party APs."
A third-party AP WM-AD allows for the specification of a segregated subnet by which non-Altitude
APs are used to provide RF services to users while still utilizing the Summit WM Controller for user
authentication and user policy enforcement.
NOTE
Third-party AP devices are not fully integrated with the system and therefore must be managed individually to
provide the correct user access characteristics. Also, third-party AP devices must be defined in bridge mode so that
user traffic is directly transposed to the third-party AP subnet and picked up by the Summit WM Controller for
forwarding and policy enforcement.
To enable third-party APs on a WM-AD:
1 From the main menu, click WM Access Domain Configuration. The WM Access Domain
Configuration page is displayed.
2 In the left pane WM Access Domains list, click the WM-AD you want to enable third-party APs for.
The Topology tab is displayed.
3 Select the Use 3rd Party AP checkbox.
The definition of third-party AP identification parameters allows the system to be able to
differentiate the third-party AP device (and corresponding traffic) from user devices on that
segment. Devices identified as third-party APs are considered pre-authenticated, and are not
required to complete the corresponding authentication verification stages defined for users in that
segment (typically Captive Portal enforcement).
In addition, third-party APs have a specific set of filters (third-party) applied to them by default,
which allows the administrator to provide different traffic access restrictions to the third-party AP
devices for the users that use those resources. The third-party filters could be used to allow access to
third-party APs management operations (for example, HTTP, SNMP).
4 To save your changes, click Save.
To Next Page
Loading...
