DHCP & Static IP wlc 5520

[nstr1]

I have a WLC 5520 v8.3.150.

My access point is in FlexConnect mode.

My SSID is WPA + Mac Filtering.

Printers were recently added to my network (bixolon ticket printer).

My problem is the following;

When I try to connect my printer by DHCP it takes IP and connects to the network, but when I assign a fixed IP to the printer it fails to connect.

I checked the SSID configuration and I see that I have the "Learn Client IP Address" option enabled. My theory is that this option should be disabled so that my printers with static IP addresses can connect to the network.

Is my theory correct or should I look for some other problem in my network?

[Flavio Miranda]

Hey @nstr1 

For start, if not yet, Just make sure 'DHCP Addr. Assignment' is not checked as 'Required'. This is found under WLANs > Click WLAN id > Advanced tab.

[Rich R]

Also refer to the passive client feature for static IP devices:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-3/config-guide/b_cg83/global_traffic_forwarding_configurations.html#passive-clients

[nstr1]

Thanks for your suggestions, I'm reviewing and I'll do some tests.

Another thing that I have noticed, (my APs are 2602, 2702, 3702 and 3802), with the 2602, 2702 and 2702 models the connection is established when I have a fixed IP but in the 3802 model with a fixed ip nobody connects (this is what I found My partner commented and it will be something that I will validate)

Based on what they have shared with me, the DHCP Addr. Assignment and it is configured in the SSID so the behavior must be the same for different APs correct ??? Or is there some different behavior between these models of APs???

[David Ritter]

why not let the printer do dhcp, and grab an IP.  then have the DHCP team reserve that IP by MAC for you device.  Thuse it always wakes up and receives the same IP and the IP is protected.  In our WLAN's, dhcp is required, so reservations accomplishes the same result.

[Rich R]

Absolutely second that @David Ritter - good suggestion.

> Or is there some different behavior between these models of APs???
Well the 2602, 2702, 3702 APs run Cisco IOS while the 3802 runs Cisco AP COS - different operating systems, and also different chipsets.  So it's entirely possible that a bug can affect 3802 but not those other APs.
8.3.150.0 is *VERY* old now!  3802 was still very new in 8.3 so plenty of bugs to be expected.  In fact they're still trying to sort out bugs on those Wave 2 APs (see Leo's link below)! For your best hope at getting a bug fix for 3802 you should upgrade to 8.5.182.11 (link below).

[nstr1]

@David Ritter Your suggestion helps a lot and at the moment we are working in this way.