Connectivity loss can occur for several reasons: your WAN connection goes down, a Meraki data center experiences an outage, or there is an Internet routing issue between your site and Meraki. This article describes the behavior of your wireless network under this "connectivity loss" state.
This article describes best practices for configuring DNS servers on the WAN interfaces of all Cisco Meraki products. One of the most common DNS configurations when assigning a static IP address to the MX is to use one ISP-provided DNS server and one well-known public DNS service such as Google (188.8.131.52). Many ISPs use their own hosted DNS server and may not have all records or have lookups to many publicly-accessible servers.
British Thermal Units (BTUs) are a unit of measurement used to quantify energy. Specifically, one BTU is the amount of heat required to raise the temperature of one pound of water by one degree Farenheit. Network administrators may need the power rating of Cisco Meraki products in BTUs for energy management purposes. All power consumption data for each Cisco Meraki product is listed in Watts on the following datasheets.
Customers sometimes ask whether they can comply with local telecommunications laws when using a Meraki system. Meraki Enterprise WLAN solutions allow customers to fully comply with CALEA by using bridge-mode to assign IP addresses from the customer's own DHCP server. Meraki's solution is, from the CALEA point of view, identical to any other wireless LAN provider, including Cisco and Aruba.
Cisco Meraki access points can operate in two functional modes for meshing purposes: gateway and repeater mode. All MR access points are capable of functioning as either a gateway or a repeater in a mesh network. This article outlines key differences and behaviors of gateway and repeater access points.
This article describes how Cisco Meraki access points set their link speed and duplex settings in different networking environments. When a Cisco Meraki access point detects an Ethernet link, it first attempts to use auto-negotiation as defined in 802.3 Ethernet standards and subsequent revisions. This is the only way to achieve gigabit Ethernet speeds, as auto-negotiation is required as part of 1000-BASET Ethernet.
Cisco Meraki outdoor access points support the use of external antennas to focus their signal into a particular coverage pattern. This article covers some frequently asked questions regarding the use and capabilities of antennas on MR series access points.
The Cisco Meraki MR product line has many great features, which can be used by network administrators to effectively support a company's needs. This article is a collection of common questions about the MR's features and capabilities, as well as their answers:
Below are troubleshooting steps to check the functionality of your Cisco Meraki AP. If you are using external antennas, make sure they are connected to the correct radio before you begin. Note: In some cases, it may be necessary to reset the AP to Factory Default Settings.
When connecting Cisco Meraki MR34 APs to several types of Cisco switches with PoE, insufficient power may be provided to the AP when using a default configuration. This is due to the fact that LLDP negotiation is required in order to achieve power allocation of more than 15.4W. Cisco Meraki APs will use LLDP to negotiate for additional power, but some Cisco switches do not have this enabled by default.
The Meraki Dashboard provides an XML API that lets you build applications that monitor your Cisco Meraki wireless networks and also share information with others. We also provide a KML feed that can be used to display your AP locations in Google Earth. The Public network status page is the feature in Dashboard that provides this functionality.
A normal aspect of a wireless deployment is the expectation that clients will roam between access points. Under certain circumstances a client may not disassociate gracefully when roaming (client is out of range of the original AP, wireless card was reset, etc). This can result in a period of time where two or more APs believe they have the same client associated to them, leading to multiple access points replying to the client which causes connectivity problems.
This knowledge base article covers the basic concepts of using SSID availability. This feature provides the ability to specify which AP an SSID operates on, and to specify certain times that the SSID will be available. It may be used to create a guest access SSID that only broadcasts on one AP or only during business hours.
There are some circumstances where a Cisco Meraki AP will fail to function. In some circumstances, the device has undergone hardware failure and will need to be replaced. However, many symptoms that appear to reflect a failure can be explained and resolved by troubleshooting. This article outlines common symptoms and troubleshooting steps that can be followed to determine if the AP is failed and requires replacement.
When a Cisco Meraki access point (AP) has lost its connection to the Internet but is still receiving power, it will broadcast a default service set identifier (SSID) that can be connected to for administrative tasks.
In a mesh wireless network, gateway access points are wired directly to the network, while repeater access points rely on wireless mesh links to get network connectivity. If a repeater AP goes down or has an unreliable connection, it will likely be unreachable from Dashboard. However, helpful troubleshooting information can be gathered both on-site and from nearby nodes in Dashboard. This document outlines steps to troubleshoot repeater connectivity