User's Manual

2. The MR33 will turn on and the LED will glow solid orange. If the unit does
not require a firmware upgrade, the LED will turn solid white within 30
seconds.
* If the unit requires an upgrade, the LED will cycle rainbow until the
upgrade is complete, at which point the Power LED will turn solid white. You
should allow about an hour for the firmware upgrade to complete,
depending on the speed of your internet connection.
3.3 Check and Configure Firewall Settings
If your network will be located behind a firewall, it must allow outgoing
connections on particular ports to particular IP addresses in order for the
MR33 to be able to seamlessly communicate with the Cloud Controller. The
most current list of outbound ports and IP addresses can be found here:
goo.gl/t1Jd0E
3.4 Assigning IP Addresses to MR33s
All gateway MR33s (MR33s with Ethernet connections to the LAN) must be
assigned routable IP addresses. These IP addresses can be dynamically
assigned via DHCP or statically assigned.
3.4.1 Dynamic Assignment
When using DHCP, the DHCP server should be configured to assign a static
IP address for each MAC address belonging to a Meraki AP. Other features
of the wireless network, such as 802.1X authentication, may rely on the
property that the APs have static IP addresses.
3.4.2 Static Assignment
Static IPs are assigned using the local web server on each AP. The
following procedure describes how to set the static IP:
1. Using a client machine (e.g., a laptop), connect to the AP either wirelessly
(by associating to any SSID broadcast by the AP) or over a wired
connection. If using a wired connection, connect the client machine
to the MR33 either through a PoE switch or a Meraki PoE Injector. If
using a PoE switch, plug an Ethernet cable into the MR33’s Ethernet
jack, and the other end into a PoE switch. Then connect the client
machine over Ethernet cable to the PoE switch. If using a Meraki PoE
Injector, connect the MR33 to the “PoE” port of the Injector, and the
client machine to the “LAN” port.