Meraki MR36

[DonW]

I am currently in a POC with a Meraki MR36. When connecting the AP to the network, it is not getting an IP address.

Does the port on the switch have to be configured as a trunk port?

Thank you

Don

[KarstenI]

Ultimately, it will likely be a Trunk to have VLANs for your SSIDs. But for the AP itself, it requests a DHCP address untagged, and an Access-Port would be enough to show up in the dashboard.

[GreenMan]

It doesn't have to be, but in many solutions it would be.  You have to ensure that DHCP will function properly natively on the access VLAN.   Did you try factory resetting the AP?

[DonW]

Thanks for your replies. The port on the switch works just fine with a laptop. The AP starts to boot up and the LED on the side stays amber, indicating that the AP is unable to get to the Internet. The AP is brand new out of the box so its hard to tell what is going on. I will try to configure the port as a trunk port and see if that helps.

[PhilipDAth]

Have you added the AP to a network in the Meraki Dashboard?

[DonW]

If I check DHCP I do no see an IP issued to the AP

[GreenMan]

Is it a Meraki switch it's connecting to?

[DonW]

The AP is connecting to a Cisco 2960. I configured the port as a trunk port and the AP is getting an IP now. At the moment I do not see the AP in the dashboard yet

[thomasthomsen]

What exact model of a C2960 is it connected to ?

What happens if you enable LLDP on that switch ? (Can LLDP "see" the AP ?)

Also, please give us a "show run int (the port the AP is connected to)" from the switch, because that could be interesting to see.

[GreenMan]

If it doesn't come up in due course, check your upstream firewall rules are allowing the AP to communicate with the necessary Dashboard resources;   these are available under ? > Firewall info, top right of the Dashboard.

[DonW]

It finally came up. I reached out to support and requested documentation as well.

I have some reading to do. Thanks again for you help!

[kmcgaugh]

What are you trying to set up?

It ultimately depends. If you need to carry multiple SSIDs with different VLAN tags, then yes, the port on the switch needs to be configured as a trunk. If not, then you can set it to access and the AP should get a DHCP address automatically.

Confirm that there is nothing wrong with the DHCP server, the switch port is enabled, assigned to the VLAN you want the AP to be on (preferably management VLAN which should be the native VLAN if its a trunk), and ensure DHCP traffic can pass through that VLAN.

[DonW]

Kaleb I was setting up a POC and after configuring the switch port as a trunk I am getting an IP on the AP now.

Thanks!

[redsector]

We always use trunk to the accesspoints, then you can use one SSID for internal VLAN, a guest SSID for Guest VLAN and one VLAN as native VLAN for the Accesspoints.