MR36 Setup

acarty
Conversationalist

MR36 Setup

I have an MR36 that pulled a bad ip because the port was configured with the wrong vlan. I removed the unit from the dashboard, reconfigure the port. The unit is pulling the right address now  but when it get imported into the dashboard it shows the wrong IP and i cannot configure it. 

6 Replies 6
Brash
Kind of a big deal
Kind of a big deal

To clarify, does the AP now have the correct IP address or the old one?

The dashboard can sometimes be delayed in showing the correct AP status.

How/where are you setting the VLAN that the AP should use?

acarty
Conversationalist

The switch port is set up as a trunk port. 

 

      interface GigabitEthernet1/0/38
                description WiFi AP test port
                switchport trunk native vlan 26
                switchport trunk allowed vlan 7,26
                switchport mode trunk

 

Vlan 7 is what i wan t the SSID to use

Vlan 26 is the AP management interface

 

The AP interface is drawing the correct IP because I can see it in the DHCP server. I did a reservation. 

DarrenOC
Kind of a big deal
Kind of a big deal

As above, your config on the switchport looks correct. This could be a cosmetic issue with the dashboard taking a little bit of time to catch up.

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
PhilipDAth
Kind of a big deal
Kind of a big deal

I assume the AP is showing as online in the dashboard?

acarty
Conversationalist

The AP shows offline in the dashboard with the WRONG ip address. 

ChrisJ2
Meraki Employee
Meraki Employee

Hi,

 

Please ensure you do not tag the native VLAN the management (LAN) IP section; this field should be blank:

 

ChrisJ2_0-1744616899986.png

this is effectively 'double tagging' and will prevent the AP from receiving a DHCP IP lease in the correct VLAN. 

 

You can tag the SSID with the VLAN chosen for client traffic by navigating to Wireless > Configure > access control, selecting the SSID from the dropdown menu, and scrolling to the bottom of the page:

 

ChrisJ2_1-1744617189876.png

 

If the above is configured correctly, and you are seeing the lease assigned from the server logs, try rebooting the AP by cycling the upstream switchport.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.