MR36 Access Points IP addresses not changing to static when instructed but are within switch page

[phelimmc]

Hi,

Can anyone advise please why the IP address of an AP is not changing to static when instructed within their web portal but shows within the switch page as the correct static IP address.

For example within Wireless->Access Points->AP1 displays as LAN IP (DHCP) even though it has been changed to a static IP address. 

When you select Switch->Switches below Clients AP1 displays as the static IP address you have assigned it. What can be causing this mismatch of the switch recognising the correct AP address but the AP not within it's page?

[Ryan_Miles · Accepted solution]

Are you setting it to a static IP on the same VLAN it's using the DHCP IP from? Or, changing to an entirely different subnet/VLAN? Typically this happens when the address you're attempting to use is failing to work and the AP (or even a switch or MX) will defer back to using DHCP.

I think I found your network. If this is yours I see you have the AP static IP set and VLAN 13 specified. You also have native VLAN 13 on the upstream port. You can't tag the AP mgmt IP and have it native/untagged on the switch. Easiest fix just delete the VLAN tag on the AP static IP config.

[phelimmc]

Yes it's the same VLAN we are using DHCP from, all the switches revert to static IP without issue but for some reason the AP's don't or don't reflect the change to static addressing on the relevant AP page. 

[Ryan_Miles]

You read the second paragraph of my response yes?

[phelimmc]

Fantastic well done! you have sorted it 🙂 just assigning the static IPs to the relevant APs. Much appreciated. For my knowledge why can't you tag the AP mgmt IP and have it native/untagged on the switch?

[Ryan_Miles]

Basic .1Q trunking rules. Your switch was expecting untagged VLAN 13 traffic. If you send it tagged from the AP the switch is going to see a mismatch.

In short, if it's the native VLAN = no tag. Anything besides the native = tagged.

[phelimmc]

Thank you