Hi @synrst to add to the other answers, I wanted to clarify if this was going to be a true mesh link between two APs or if you're just hoping to have the wireless client device at the far end.  From your description it sounds like a true wireless backhaul link between two APs, the house is the gateway AP and at the gate you have the mesh AP, with the camera getting back over that backhaul/mesh link.    Like @Ryan_Miles said the MR78 isn't intended for this purpose, but might actually work "good enough" given the 260-foot distance. So yes, this can work, but perhaps not that well, possibly not  at all, and if it does it's much less than ideal. When we have typical outdoor mesh networks with MR76/86 and ANT-20 omni antennas, we typically stick to 100 to 200-foot max spacing.    That said I'd also be inclined to recommend MR76 as @PhilipDAth mentioned for this purpose, with a band-specific sector antenna like the ANT-21 5GHz sector antenna.  This way you could ensure the APs will choose the 5GHz band for mesh backhaul (they would anyway because you're using the 5GHz ports on a 76) and you can manually configure a non-DFS 80MHz channel on a 5GHz-only SSID for the mesh link. If it's an MR76 you could also leave the 2.4GHz radio turned off and put some weatherproof 'N' caps over the 2.4GHz ports.   And you may actually only need an MR76 on one side, which is not typical design practice, but you would have antenna reciprocity going for you. What I mean is if you have an MR76 and ANT-21 out at the gate, that is going to both transmit and collect a lot of signal to/from the MR78 on the house and give you a better reach and SNR scenario versus if it was 78-to-78 (omni-to-omni).  Or the reverse, depending on mounting options or aesthetics, you could have the MR76 and ANT-21 on the house and an MR78 out at the gate.   This is all assuming the camera is not wireless capable?  Because if this was a Meraki MV camera or any other camera that has wireless capability, I'd advise no mesh link and no AP at the gate.  Rather a single MR76 or 86 on the house with sector antenna(s) aimed at the gate, that would be no problem at a few hundred feet for a wireless device at the gate to associate directly back to the house AP.  But it sounds like the scenario you are describing is that you might have a wired camera and would have to get it's wired connection into the mesh AP to get back over the backhaul.   Hope that helps!  Ping us back for follow up. ... View more

Confirmed @WB  that Tx power is the IR itself.  Hope that helps! ... View more

Hi @JohnDH. As @ww mentioned, those are the default values and AutoRF will tend to balance things out, but rarely would you want to leave the max set to 30dBm, that's one full watt of Tx power and no client device will ever match that anyway.    In many many deployments I typically see customers leave the default of 8 and bring down the max to perhaps 23 to 25dBm for example.  Of course the proper answer is always found via site survey but as a rule of thumb remember that you DO need some cell overlap, for example your walk-through may reveal cell edges at -67dBm with minimum data rate of 12Mbps with 20% cell overlap, then use band steering to 5GHz, perhaps disable every other 2.4GHz radio, and then additional tweaks as needed.  If you get as far as adjusting RXSOP (which we say is like putting "ear muffs" on the AP) then do that LAST, that is only meant to be leveraged in a deployment that has already been fairly well tuned.    Perhaps a first step would be for you to drop that RF Profile down 3dB at a time and observe your results over the course of a day.  Remember the AutoRF changes will not be immediate, there is an algorithm with timers and limits to how many dB can be increased/decreased in a given time, in order to prevent a ripple effect throughout the coverage area.  So even if you bumped an RF profile max Tx power from 30 all the way down to 20dBm, it would take some time to get there, by design.  ... View more

@johnny_5 if you only have MR56 to work with and we're talking about installing the APs up at the peak of the "A" shape of the ceiling, I'd advise against that for anything over 20 feet as a rule of thumb.  As @GIdenJoe mentioned, the best answer is always "site survey" as no two deployments will ever be quite the same.    That may not be what you wanted to hear, the 40 to 50-foot spacing is fine but if the peak is 30+ feet then most/all of the RF energy is going to far above where the clients will be, except perhaps in the rear top-most rows of the bleachers.  Will there be signal down at the floor level, sure there will be some but it could be far from optimal and give a poor experience, lower data rates therefore higher airtime utilization, etc.    So your options may boil down to wall-mounting those MR56 APs at a more reasonable height, or leveraging MR46E with semi-directional antennas like the E6 wide patch.  Hope that might help!  ... View more

Hi @GregErnest  A couple of possible views that would help but in different places in Dashboard.    If you navigate to Network-Wide > Monitor > Maps and floorplans, if you have uploaded floorplans and placed your APs accordingly, then you can view any/all floorplans and the placement of devices (not just APs but any Meraki equipment).  You can enable/disable any of those to only have APs visible on the floorplan.  Then you can also change the marker value to be the name of the AP, the model of the AP, the # of connected clients, etc.     For example:   In addition, if you're talking about the blue dot client placement on top of a floorplan, that would be under each individual client's status page which would include an approximate location info, like this for example:     Next, if you navigate to Wireless > Monitor > Location Heatmap, that can provide you with a playback of client density and how clients moved around the environment over time and you can see playbacks 24 hours at a time for example.  You can view associated clients (blue dots) and unassociated clients (gray circles) as well a Bluetooth devices.  For example:       And finally, you have the Organization > Monitor > Location Analytics where you can examine proximity (or capture rate) and engagement (or median visit length) and loyalty (repeat visitor rate) and you can also compare this across different sites/networks.  For example:     As Brandon mentioned, if you are looking for an actual RF heat maps, that is best left to sophisticated 3rd party tools such as Ekahau or similar to import your floorplans, specify all the details like building materials, ceiling heights, etc and generate more formal predictive reports..   One last point is a reminder that you can also leverage the LSP (local status page, unless you intentionally disabled them) and as long as your associated to an SSID, you can point a browser to ap.meraki.com and see your client's info, the AP's info, neighboring BSSIDs and on that LSP there is also a speed test button and graphs for 2.4 and 5GHz channel utilizations.  So you can leverage that built-in LPS to walk around the environment and conduct you own mini site survey with that one particular client, find coverage holes, etc.   For example:   Here are some links for more info: https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Using_a_Floor_Plan_or_Custom_Map_in_Dashboard https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Placing_Devices_on_the_Map_in_Dashboard https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page   Hope that helps!     ... View more

@Lourdes is sounded like you were looking for a high level explanation and that is simply that you are leveraging DFS channels (UNII-2 channels from 52 through 144) and in that particular frequency range there is the possibility of interference with RADAR systems.  So DFS, Dynamic Frequency Selection is required.  If the AP detects a RADAR event, they are required to change channels and remain off the channel where the RADAR was detected for a period of time.    This is not necessarily a problem, and there may not be anything to resolve necessarily, left alone it will self-resolve. But it depends on what your channel plan currently looks like, how much you depend on DFS channels to accommodate a certain channels plan, how often RADAR events occur, etc.  In some cases you might decide to allow DFS events to play out naturally and perhaps are non-disruptive, alternatively you might decide there are frequent DFS events that become disruptive to performance or a reasonable channel plan and possibly decide to disable DFS channels in the RF profile.  More details are in the documentation here https://documentation.meraki.com/MR/Radio_Settings/Dynamic_Frequency_Selection_(DFS)   Hope that helps.     ... View more

@GIdenJoe is correct, there isn't an install guide specific to the ANT-25 and it comes with the mounting hardware included for either wall or mast mounting for example.  Depending on the AP in use (like MR76 vs MR86) and depending on the use case (if it's a mesh link for example) then you might have one or two ANT-25 installed on the AP.  More information in the FAQ is needed. https://documentation.meraki.com/MR/Other_Topics/Frequently_Asked_Questions_regarding_Cisco_Meraki_Antennas   ... View more

@CodyNetworkGuy you are ok to do this in your case without requiring an intermediary firmware version.  In the event there *is* an intermediary version, Dashboard will flag that as an "upgrade barrier" and disallow the change. Also, I would consider going with 14.33 which is the current SRC and should be promoted to GA sometime soon.  ... View more

Hi @jx12345 you are correct that is not available in the API yet but I will check for a status.  I wonder if in the meantime, if you want to force it in a way, if you just force a group of APs into an alternate RF profile and then back again. But also note that toggling the rfProfileId also clears any manual overrides, but then again, if you want to run a fresh update auto-channel perhaps the manual overrides aren't needed and wouldn't be wanted anyway. Will let you know if I hear an update on a way to update auto channels via API.    ... View more

@ls08 you are correct, today there is only the /networks/{id}/wireless/airMarshal endpoint for listing out the most recent scanning results from Air Marshal.  I'll check if there's an FR in place (or add one) to get the ability to configure Air Marshal and/or configure those dual-radio APs to dedicated scanning mode and back off.     Note that you don't necessarily have to turn them into dedicated scanners if it acceptable to have Air Marshal run opportunistically once a day without having to disrupt client connectivity.  More info in the documentation. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal   ... View more

@jbright  Agreed, like the 72/72X they do want/need AT power at boot (regardless of temperature) for the on-board chassis heater element.  To some extent, the camera itself can almost act like its own heater but only up to a point of course.  I'm closer to the east coast in the NJ/NYC area and have seen a few heater events hit the event log for mine, right around the freezing mark as expected.  ... View more

@Guillaume6hat understood, it's basically acting the way you might expect if you were looking at a flex table in the UI and typed MYTAG into the search box.  I'll take a look and submit a feature request if there already isn't one for exactMatch versus contains.  ... View more

Hi @Rob_Jandausch the most recent firmware upgrades/downgrades are maintained in a "Most recent changes" table on the Organization > Monitor > Firmware Upgrades page.  Beyond that, Meraki Support can assist with historical firmware data, which firmware was running when, in case that type of historical info be required. So yes that info is maintained but on the back-end and available via simple support ticket if needed.  ... View more

Hi @MendezJeCoOfEP this sounds like a typical wireless mesh config most likely with MR76 APs.  I have some outdoor public park deployments and can give you a hand with that if you want to private message me, I'll have some questions on the details and it would be helpful to have a few photos and an overhead/satellite image or perhaps a quick cell phone video of the area to be covered and the central building it would backhaul to. ... View more

Correct, a full org admin can remove a device from a network and unclaim it from the org, at which point it could be re-claimed into another org, perhaps by a completely different full org admin. In this case it seemed like Anna claimed devices into an org and then somehow were no longer in the org, so trying to figure what went on and where these serials existed and when and how they were purchased to try to determine if some online 2nd hand seller was running a scam.  ... View more

Hi @AnnaB like @Ryan_Miles I can see the APs in another customer's Dashboard organization (actually two Orgs), as if they were never unclaimed from those Orgs, however they were never online or in use.  When you say they gave you the codes, do you mean the serial numbers, or maybe an order number and/or a license key?  And you say you claimed these 7 APs and they did in fact populate into your Organization > Inventory?    If so, and you did not unclaim them yourself, nobody else would have been able to claim them, it would give the same error that the devices were "in use" because they're already claimed in your Org.    You'll probably have to open a case with Meraki Support and the partner/reseller you purchased the APs through.  Meraki Support should be able to investigate the order history and if and how these APs were ever claimed into your Org and/or removed from your Org and how they ended up in another customer's Org.   ... View more

@nickydd9 @DarrenOC  I think the official answer on Visio Stencils is https://meraki.cisco.com/product-collateral/cisco-meraki-visio-stencils/ but like with most vendors they tend to range from out-of-date to painfully out-of-date.  My colleagues and I have made this known internally, not sure what the mechanism is for keeping the stencils up to date, I will look into it again and make some noise.    But I'd like to try to help regardless. There’s generally enough in the .vss to make useful drawings but you might need to leverage the MR52 stencil to represent the MR56 for example and update the properties (if object properties matter or even get used).     We do have the Meraki Collateral Library and you can search it with the keyword "photograph" here https://meraki.cisco.com/collateral/?sortby=by-name&keyword=photograph which has more current product images if that's helpful in some way.    Also, I know that some customers (rather than waiting for Visio stencil updates) have actually used the images from our Meraki sizing tool to create their own Visio stencils in a much easier way than manually creating them. Check out the images here for example, click into an MS390-48UX2 and one of the uplink modules if desired and there's a pretty good and accurate depiction of the switch, in case this might help. https://merakisizing.com/#/ms   The new MX75/85/95/105 models don't have photographs posted quite yet but they did already make it into the sizing tool.    ... View more