Meraki Community

glydeen · ‎Dec 28 2023

I eventually brought in my Meraki sales representative. In my situation, Meraki believes the antenna is at fault, indicating to the AP the wrong antenna model. They intend to replace all 20 of the F6 antennas. I will hold off on forming an opinion until I try this solution, but I'll defer to their expertise for now. I expect these replacements to arrive in a couple of weeks, and I will provide an update on the status after testing and installation.

glydeen · ‎Dec 5 2023

Sorry for the late reply. A ticket has been opened with the original order number of the Antenna and APs. I discovered a crude workaround that worked on one unit, but due to the time and service disruption, I have decided to wait for a fix. I have left the others untouched. The "fix" involved unclaiming the device, factory resetting, re-claiming, configuring, manually setting the antenna, and placing the AP back in service. This resulted in about an hour of work on a lift and in the IT workroom to make necessary changes. My company prohibits electronic devices on scissor lifts which added time. Model Number Installation

glydeen · ‎Dec 5 2023

I opened a support ticket but haven't received an update in 5 days. As of now, there's no fix.

glydeen · ‎Nov 16 2023

I am having some issues with my MR46E devices in a warehouse setting. Each device is equipped with the Narrow Patch (MA-ANT-3-F6) antenna, but I have noticed that all of them are auto-detecting the Wide Patch (MA-ANT-3-E6) antenna. Despite my attempts to manually change the settings, the Dashboard indicates that the devices are auto-configured. I have already sought assistance from Meraki support, but they have not been able to provide any solution. For your reference, my devices are running on firmware MR 29.7.1. Has anyone experienced this behavior before in their installations or have any other solutions to offer?

glydeen · ‎Sep 5 2023

I have a scientific device I am attempting to join one of our networks, I am finding this device will successfully join only if I am advertising the SSID over one AP. If I'm roaming with more than one AP the device will never authenticate. This device uses a TI Z64-CC3220MOD Radio, WPA2 PSK with 2.4 GHz support. The SSID is being broadcast and not hidden. Other devices are functioning normally. I am using MR56 and MR46E Access Points and MR 29.6.1 firmware. I'll concede the device is most likely the issue, but I'm looking for any suggestions.

glydeen · ‎Sep 11 2021

Someone please clarify. Using Layer3 outbound rules, I'm blocking all outbound traffic using with a catch all rule as my last rule. I'll then be allowing access to certain sites by using allow rules with the site(s) FQDN. Do I use an "*" asterisk as a wildcard such as *.google.com or do I drop the asterisk when defining a FQDN I've seen conflicting information. Another question: In the list of required Google URLS is *.clients[N].google.com. Where "[N]" is a number, in this case 1-6. ie. *.clients1.google.com, *.clients6.google.com etc., Is there a way to to easily catch this in a Wildcard. In testing *.google.com didn't seem to catch this and allow traffic to these URL's to pass. Any advice would help. Thanks

glydeen · ‎Aug 25 2021

Very new to Meraki and how Meraki handles Firewall rules etc... I need to create a segment on the network blocking all outbound access except for what I explicitly allow. I am looking for advice on how to handle allowing access to Office 365. Do I need to create a policy Object and include all the FQDN's for Office 365 (The lengthy list), or is there a simpler approach? Any advice would be appreciated.

Meraki Community

About glydeen

glydeen

Community Record

Badges

Re: MR46E detecting wrong Antenna type

Re: MR46E detecting wrong Antenna type

Re: MR46E detecting wrong Antenna type

MR46E detecting wrong Antenna type

Client unable to connect TI Z64-CC3220MOD Radio

Layer3 Outbound Rules

Permitting access to Office 365