Home > Wireless LAN > Monitoring and Reporting > Static IP Assignment on a Cisco Meraki Access Point

Static IP Assignment on a Cisco Meraki Access Point

Cisco Meraki Access Points can use either dynamic (DHCP) or static IP configuration to connect to a network. Although DHCP is recommended, you may configure a static IP address on a Cisco Meraki AP either from the Dashboard or locally on the device.

Static IP Assignment via Dashboard

Note: This method requires that the AP is an active gateway. This means that the AP needs to be online in Dashboard and have either an active DHCP lease or a currently functioning static IP address. This method does not work for devices acting as repeaters.

  1. Browse to dashboard.meraki.com and login to Dashboard.
  2. Navigate to Wireless > Monitor > Access Points and click the name of the AP you would like to configure.

     
  3. On the device status page, click the Edit icon to the right of the current IP information to expand the configuration for that device.

     
  4. Input the appropriate connection information and click the "Save" button.

As soon as the AP updates its' configuration to include the new static IP it will attempt to use that IP on the network. If the AP is not able to reach the configured default gateway on this static assignment, it will fail back to DHCP. Please inspect the static configuration and the VLAN configuration being used on the network if this happens.

Note: If a VLAN is specified in the static IP configuration, management traffic from the AP will be sent out with an 802.1q tag for that VLAN. In this case it is expected that return Management traffic should also be tagged appropriately.

Local IP Assignment

  1. Connect to the Access Point and open the Local Status Page.
  2. On this page, click 'Configure'
  3. The page should now prompt for login credentials. If local login credentials were configured via Dashboard, please use these credentials. Otherwise, the default login is the device's serial number as the username and a blank password.  
  4. On the Configure page, input the new static IP information, then click 'Save'
    Static IP Assignment on a Cisco Meraki Access Point.png

Note: If a VLAN is specified in the static IP configuration, management traffic from the AP will be sent out with an 802.1q tag for that VLAN. In this case it is expected that return Management traffic should also be tagged appropriately.

Please note that your wireless connection to the device may be interrupted if the AP is in a scanning mode, causing it to change its channel. Before saving any changes you may wish to verify you are still connected to the correct SSID and AP. 

Access Points with Multiple LAN Ports 

The MR12, MR58, MR52, and MR53 include a secondary LAN port to connect to the network with, however only the Primary Ethernet port can have a Static IP configured.

Identifying the primary Ethernet port

MR12

The primary Ethernet port is directly adjacent to the power connector and is labeled as Uplink.

c1ae22c2-6a06-4caf-b8d5-c386ee763ad3

 

MR58

The primary Ethernet port is located on the bottom-left side of the AP and is labeled as ETH0.

0463d31b-cf61-42d1-866a-9a4b35fb40ee

 

MR52/53

The MR52 and MR53 both feature 2 Ethernet ports:

 

     

  The labeled “PoE” accepts 802.3at and 802.3af power and should be used as the primary uplink to your LAN/WAN.

 

 

  The 2nd port may be used for LACP bonding with the PoE port

The second Ethernet port can be used in a bonded configuration with the "PoE" port. Ensure that the AP is plugged into 2 switch ports on the same Ethernet switch that have been configured for LACP bonding. Keep in mind that the maximum bonded aggregate bandwidth is 2.0 Gbps. See the MR Link Aggregation Configuration Guide for more details

Note: Link aggregation is only supported on the MR52/53. 

Behavior Differences between Primary and Secondary Ports (MR12 & MR58)

Primary (Ethernet 0)

This interface is capable of receiving power using PoE and can be assigned a static IP address. It is also capable of 10/100/1000Mbps speeds. It is intended for connecting the MR12 to the rest of the network.

Secondary (Ethernet 1)

This interface can only receive an IP from DHCP and is not able to receive power using PoE. It is only capable of 10/100 speeds. It is still able to connect to the Meraki Cloud Controller if the Primary connection is down, but is intended for used by a wired client. To allow use by a wired client, please refer to our documentation regarding Extending the LAN with a Wireless Mesh Link.

Determining which port is being used

The simplest way to determine which port is being used is to physically look at the device, and refer to the diagrams above. If you are not near the device, the easiest way to determine if the secondary port is being used is by looking at the AP Dashboard. Navigate to Monitor > Access points and click the AP in question. Look under Status for LAN IP #. If the # = 1, then the AP is connected using the primary port. If # = 2, then the AP is connected using its secondary port. 

Additional Resources

For more information about configuring a new MR Access Point, please check out our MR Quick Start article. 

Last modified

Tags

Classifications

This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 6779

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community