LWAPP to Controller communications

[mdeloach]

We are installing our first NM-AIR-WLC6 module. The router has very strict ACLS applied to the AP facing fast ethernet interface.

The LWAPP documentation list the ports required to be open for WCS to WLS communications, but does not list the ports needed for LWAPP to WLS.

We'd like to use IP subnet discovery, but even with DHCP option 43, we'll still need a list of ports that need to be open.

[smalkeric]

When you are installing a Layer 3 access point on a different subnet than the Cisco Wireless LAN Controller, be sure that a DHCP server is reachable from the subnet where you will be installing the access point, and that the subnet has a route back to the Cisco Wireless LAN Controller. Also be sure that the route back to the Cisco Wireless LAN Controller has destination UDP ports 12222 and 12223 open for LWAPP communications. Ensure the route back to the Primary, Secondary, and Tertiary Cisco Wireless LAN Controller allows IP packet fragments. Finally, be sure that if address translation is used, that the access point and the Cisco Wireless LAN Controller have a static 1-to-1 NAT to an outside address. (Port Address Translation is not supported.)

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_quick_start09186a00805100f5.html

[a.raaz]

Hi,

I am having a similar issue - 192.168.x.x is the Cisco Wireless LAN Controller and APs will be in 10.180.x.x subnet... dhcp is available (windows 2000) in 10.180 subnet...but still APs will not be able to connect to Cisco Wireless LAN Controller. Where do you set "route back" in my case. Is it on DHCP server or where ??

thankyou

A

[mccallur]

Hi,

there are two problems that we have identified;

1. The VCI string in the manual is wrong. It should be: "Airspace.AP1200" it is case sensitive and the dot is part of the string.

After having fixing the above problem and the AP get the correct DHCP reply meaning an ip address, correct subnet, the gateway ip address and via option 43 the ip address of the 4400 controller. The following is seen on the analyser trace:

2. The AP does a layer 2 broadcast to connect the wifi controller, then a layer 3 IP broadcast on the local subnet. The AP is looping between those two.

It is poor coding to still have the AP do a layer 2 Bcast and a layer 3 IP local Bcast on the same subnet while it has received a DHCP reply telling it that the WiFi controller is on a differend subnet.

Btw we're using the latest version for the 4400, released early March 2006.

The only thing we haven't tried yet is to fall back to layer 2 mode and have the AP connect to the 4400 and get new firmware. We'll try that this afternoon.

If needed I can sent the analyser trace, we're using ethereal.

Regards,

Henk Kruisbrink

email: henk.kruisbrink@healthalliance.co.nz

[a.raaz]

Hi Henk

Yes, That's right and more detailed information can be found in WLC deployment guide for 4400 series controllers.

Thanks

A