Defining Policy Rules for the Third-party APs

1. Because the third-party APs are mapped to a physical topology, you must define the Exception filters on the physical topology, using the Exception Filters tab. For more information, see Exception Filtering.
2. Define policy rules that allow access to other services and protocols on the network such as HTTP, FTP, and SNMP (Simple Network Management Protocol).
3. On the Multicast Filters tab, select Enable Multicast Support and configure the multicast groups whose traffic is allowed to be forwarded to and from the VNS using this topology. For more information, see Multicast Filtering.

In addition, modify the following functions on the third-party AP:

• Disable the AP's DHCP (Dynamic Host Configuration Protocol) server, so that the IP address assignment for any wireless device on the AP is from the DHCP server at the controller with VNS information.
• Disable the third-party AP's layer-3 IP routing capability and set the access point to work as a layer-2 bridge.

The following are the differences between third-party APs and APs on the Extreme Networks ExtremeWireless system:

• A third-party AP exchanges data with the controller's data port using standard IP over Ethernet protocol. The third-party access points do not support the tunnelling protocol for encapsulation.
• For third-party APs, the VNS is mapped to the physical data port and this is the default gateway for mobile units supported by the third-party access points.
• A controller cannot directly control or manage the configuration of a third-party access point.
• Third-party APs are required to broadcast an SSID unique to their segment. This SSID cannot be used by any other VNS.
• Roaming from third-party APs to wireless APs and vice versa is not supported.