Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About pgrovesnz
pgrovesnz
Getting noticed
Member since Apr 17, 2019
Sep 3 2021
Community Record
26
Posts
1
Kudos
1
Solution
Badges
May 31 2021
12:34 PM
Hi Has anyone had issues with aggregation between Meraki switch stack and a Cisco C4500X stack? If one of the Meraki switches in a stack reboots the remaining port in the aggregation drops and instead of negotiating the aggregation again with the Cisco it falls back to standalone. When the other Meraki switch comes back online the Cisco switch then error disables the ports due to LACP issues. To get the aggregation back the ports on the Cisco switch have to be shutdown and no shutdown to get the aggregation back up. Thanks
... View more
Nov 25 2020
1:04 PM
Fortunately this was our DR site and apart from 2 circuits to sites, everything was in maintenance. Equipment was only connected to the MS425-16 switches and I had scheduled to move equipment to the MS425-32 the following day. If I had done this the other way arround I would may have only found the issue on the 2nd day of work and caused greater issues. So, once the MS425-32 switches were disconnected we were able to bring the 2 sites back online and remove our equipment from maintenance. I then cancelled the following days work. When we have a plan to correct the issue with the MS425-156 / 32 stack I will schedule to reinstate the MS425-32 switches. I will post an update on how we proceed.
... View more
Just an update for those that are interested. We swapped all of the APs it with the same model but the issue started again 2 months later. It seems as if the radios failed and caused them to reboot. Aerials were Meraki narrow patch antennas. We then changed to MR46E APs and have been operating for months without issues. As a precaution we had the site analysed for wireless interference with all of the APs turned off just in case something was overloading the radios of the APs. That came back all clear. We even ran the arena LED lighting at full power and they had no interference. So, we are hoping that the chamber in AP model works fine.
... View more
Nov 25 2020
1:05 AM
1 Kudo
Hi Just recently we can across a big with having a mixed MS425-16 / MS425-32 stack. We set up the stack in our workshop and it worked fine. It was then moved to our server room and was still working fine. Ports 17 and 18 (qsfp) on the MS425-16 were configured as stack ports and and 33 and 34 qsfp) were configured as stack ports on the MS425-32. When the MS425-16 switches were powered down and moved, on powering back up the agreggated port configuration from ports 17 and 18 from the MS425-32 was applying to ports 17 and 18 on the MS425-16. We were getting LACP errors on the MS425-16 switches even though they were configured as stack ports. Meraki support confirmed this was happening and when the agreggated configuration on the ports of the MS425-32 was removed and MS425-16s were rebooted they joined the stack successfully. However we had aggregated ports set up on the remaining lower ports of the MS425-32 and they seemed to apply to the agreggated ports of the MS425-16 switches. We started to get stp errors on the MS425-16 ports, blocking and also errors on the lag setup in our HPE Synergy enclosure. The issue went away when the MS425-32 switches were powered off. At this stage we are waiting on Meraki support to supply more information about the bug and assist with how to remedy this. I would like to find out if anyone else has experienced this and if they have been able to implement the mixed stack. Were you able to use an older firmware or rebuild the stack to fix this? The safest option at this stage seems to run 2 stacks and not mix the switches, however this would mean that we couldn't use them as one core switch as we intended. Thanks
... View more
Dec 20 2019
3:53 PM
On our Cisco switches it is easy to see when the access points drop their data connection. Not so easy to see on a Meraki switch. Also the Meraki dashboard doesn't show these drops against the access points. Apart from 3 access points that are constantly down if I only checked the status of the access points on the Meraki dashboard it wouldn't be that noticeable. I have 3 different behaviors of APs - 3 access points that are offline most of the time and dropping network connection every 11 minutes - 8 access points that only report occasional outages and dropping network connection every 11 minutes - The rest of the access points that are okay Occasionally the issue may clear for an AP but another may play up. You really need monitor this issue from the switch to get a better idea of which access points have issues.
... View more
Dec 20 2019
2:24 AM
Hi I have a case logged at the moment as many of our MR53E access points with firmware 26.6 restart at around 11 minutes. It affects around 9 of our 21 access points. 3 are unusable and the rest work fine while they are connected. A few may play up for a while and then the issue guess away. On the Cisco switch I see the data drop and then comes back up. It also does the same on a Meraki switch. I have tried changing the switch port configuration for power and also using different internet connections. I was advised today that it may be a known bug. Had anyone else come across this and have more detail about the bug? Since the access points are high up in an arena it is difficult to get one down to assess them more. Thanks Paul
... View more
Hi Is anyone else having issues with firmware version 26.6? Since upgrading to it a couple of weeks ago our MR53 and MR53E APs are dropping their network connections. They stay powered on, but I see the LED go red and then they reconnected. On both Cisco and Meraki switches I see the data on the port drop for a few seconds. On a few APs if I disconnect them and connect again they have issues negotiating their PoE power with the switch. I have a case open with Meraki for this at the moment. Thanks
... View more
Nov 12 2019
10:57 PM
Hi Just wondering if there was any reason why Meraki would disable Air Marshall on an MR70 by default? Would there be any issues with enabling it? Thanks P{aul
... View more
Jun 19 2019
3:31 PM
@jdsilva wrote: @pgrovesnz wrote: Since I can't log in I can't create a ticket. For next time: https://meraki.cisco.com/support/ Yes, I could have phoned, but the Log In didn't work.
... View more
Jun 19 2019
2:59 PM
Hi Anyone else having issues logging into the Meraki Dashboard? It comes up with a server error and says that a message has been sent to their engineering and support teams to notify them of the problem. Since I can't log in I can't create a ticket. Thanks
... View more
May 8 2019
1:29 PM
@EMcHate wrote: What are your thoughts on running 5ghz only in all MRs? Hi, not an option. It's an events venue so will still have older 2.4GHz devices.
... View more
Apr 23 2019
2:59 PM
@BrechtSchamp wrote: I assume each of your sites is in its own network. And I also assume the subnet on each site for that vlan id is different. Then you only have to take one site into consideration as the broadcast domain would be separate on each site. Also note that the management vlan is only used for clients if you're using ssids in nat-mode or if you don't specify vlan tagging on your ssids which in your case I definitely would... So the main worry is not the number of aps, and the management vlan, but rather the number of clients and the client vlans. I believe Cisco usually recommends to stay below 254 (/24) clients per vlan. So in your case if you have 2000 clients connected to a single ssid you should split them up by using per ap multiple vlan tagging: https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging_on_MR_Access_Points#Setting_Per-SSID_VLAN_Tagging_in_Dashboard Hi We use different VLANs our desktop computers, voice, switch management, wireless APs, SSIDs, etc. Also, the SSID that can have up to 2000 devices is already split into 2 VLANs with around 1000 client limit for each. Do you have a reference to the recommendation Cisco / Meraki has for staying below 254 clients? Thanks
... View more
Apr 22 2019
1:30 PM
@PhilipDAth wrote: The amount of Meraki management traffic will not be affected by the quantity of VLANs, weather that be 1 or some other number. I tend to use the same VLAN number scheme at each site. I tend to put all the APs in the same VLAN (assuming you have 2,000 or fewer users connected at the same time). So, one site with 28 APs can have up to 2000 devices so I assume at least I should have a separate management VLAN for those APs?
... View more
Apr 19 2019
9:41 PM
Hi We have started to replace our Cisco Access Points with Meraki. We have just over 100 Access Points across a dozen sites. Does it matter if all access points are in the same vlan or is it better to have a vlan for each site. With the client tracking being synced to access points, would this create a lot of traffic on the management vlan if there was only one vlan? Thanks
... View more
Apr 18 2019
11:28 AM
@NolanHerring wrote: @GIdenJoe Is that with MESHING enabled or disabled? Probably meshing is what your still seeing being sent as it will keep sending those frames to ensure the AP can still work in repeater mode. We had already turned off meshing. We had an issue with a few access points going into the repeater mode instead of using their wired network connection, so turned it off. It seems that turning off mesh mode stops access points going into repeater mode but the radio still seems to send frames.
... View more
Apr 17 2019
2:31 PM
I understand what you say, but if you use a wireless analyser to check the channel, you will see that the channel/s are flooded and will affect any access point and client using the channel. Any device sending traffic on a channel will cause retransmissions on the channel. When there is a high density of devices the problem multiplies with clients waiting to transmit. If one device transmits at a slow rate that will cause all other devices to also transmit at a low rate. Behaviour of the Meraki APs don't reflect best practise and stop you from tuning the network for best practise.
... View more
Apr 17 2019
1:39 PM
@NolanHerring wrote: Sounds good What I will tell you is that with the 2.4GHZ radio 'OFF' and MESHING set to Disabled, the AP will still show the 2.4GHz radio power at whatever value it is going to randomly choose. So you'll just have to ignore that, and know that there isn't anything emitting from it. If it does behave like that that is terrible behavior when tuning a network at a stadium environment. We have 11 MR53E access points with narrow patch antennas. For the 2.4GHz to work better and avoid multiple APs on the same channel we want to completely disable the 2.4 on some APs (6 of them). The rest of the APs have the power level dropped to below 8. Having any AP at full power will cause issues on the other APs using the same channel. The only solution at the moment is to set the AP power on the APs to low and hopefully cause any other issues.
... View more
Apr 17 2019
10:27 AM
@NolanHerring wrote: The only way to turn off the MESHING (which should be the only traffic coming from it), is to have support give you access to enable/disable MESHING under the General settings for each Network We already have this turned off and are haven' any issues apart from the 2.4GHz at full power. I will try firmware 25.13 with meshing turned off in a test network and see how it behaves.
... View more
Apr 17 2019
10:14 AM
@NolanHerring wrote: Do you mean turn off MESHING? If your running 26.X code I would not do it, as I know first hand it is going to cause issues with stability. 25.13 should be fine (as far as I know) Yes, I will go back to 25.13 and turn meshing off. Is there any need to have meshing enabled? The wireless engineer that was tuning the network for high density, thought the behavior of the Meraki access points was extremely bad. Since he works with all other major access points I trust his assessment.
... View more
Apr 17 2019
9:52 AM
Thanks, that is the information that I need. Since, the network is being set up for a high density deployment I will ask for the ability to turn it off and see if I have issues.
... View more
Apr 17 2019
9:46 AM
Since the wireless is being set up for a high density deployment we still want 2.4GHz available on some access points so this isn't an option.
... View more
Apr 17 2019
12:40 AM
Hi, I was wondering if anyone had tried to turn off 2.4GHz on MR53 or MR53E APs? We have MR53E APs and applying a 5GHz only profile didn't turn off the 2.4GHz radio. I found that there are no SSIDs being broadcast on the 2.4GHz but the 2.4GHz isn't turned off. If I attempt to set the target power for 2.4GHz on an AP to Off, it goes to full power 29 dBm. If I monitor the AP from another AP I see that there are no SSIDs being broadcast, but see the power at -40dBm. We are using firmware 26.2 as that was recommended by Meraki. Is anyone able to try this in a test environment and see if they have the same issue? Meraki don't seem to have any other clients that have logged issues like this.
... View more
Apr 17 2019
12:31 AM
Hi, I was wondering if your 2.4GHz actually turned off. We have MR53E APs and applying a 5GHz only profile didn't turn off the 2.4GHz radio. I found that there are no SSIDs being broadcast on the 2.4GHz but the 2.4GHz isn't turned off. If I attempt to set the target power for 2.4GHz on an AP to Off, it goes to full power 29 dBm. We are using firmware 26.2 as that was recommended by Meraki.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2746 | Jun 19 2019 3:01 PM |
© 2024 Cisco Systems, Inc.
