1810w/1815w LAN ports fail to link 'local'

[David Ritter]

WLC 5520 8.5.171.0

according to the documentation,

4 AP1810W (and 1815w) has 3 LAN ports, which are configured through "Ports/Module"

5 OEAP1810 LAN1/LAN2 are configured through "Ports/Module," with RLAN "None" represents local port. LAN3 is always a local port

To me, local means AP's attached data segment.  Currently it seems that if RLAN 'None'  the ports go DEAD!.  even when they are explicitly checked on.  In the past one could plug a 'w' into the wall jack, with ports enabled "none" and the 'switch' would lite up 3 LAN ports on the inbound data segment.  

This nolonger seems to be the case..  and since the 'local' data segment is NOT a defined interface in the WLC I now have to add a couple hundred new/more interfaces to the WLC which is NOT going to happen.

Anyone else discover this problem ?

[Rich R]

We've never used those ports - have you followed https://www.cisco.com/c/en/us/support/docs/wireless/aironet-1810w-series-access-points/200630-AP1810W-LAN-Port-Mapping.html and https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-4/b_AP_1815_wall_plate_deployment_guide.html ?

[David Ritter]

Yes.  Surprise, we use them as easy to mount/wire AP's also.  Real RLAN's work fine.  Usually I link the 'rlan' to the same segment as the wlan ssid.  Thus the interface/vlan exists at the WLC.  However if the rlan/vlan is not specified the port (if enabled) is supposed to link the local segment.  Oh well I added the requisite vlan/segment to the WLC trunk yesterday as the Core router hosts all.  Strangely enough as I enabled this new interface, all 333 AP's bounced.

So I have a workaround.

Thank you.