Meraki

cmr · ‎Jan 8 2020

It seems to have replaced 26.6 without fixing anything, is a new AP about to be released?

cmr · ‎Dec 31 2019

You can RMA it if needed, I had an MR32 replaced with a dim LED as we have remote sites and the light is a useful diagnostic for non tech savvy users.

cmr · ‎Dec 27 2019

I think there was, very briefly, a 15.22 but the whole release train has been suspended due to some issues with specific models. I have been chasing support for updates but the last I managed to get was a non-specific "soon". You can log a ticket to get support to install 15.x updates if your model isn't one of the affected ones. If it was, you should have received a message from them in the dashboard.

cmr · ‎Dec 26 2019

@PhilipDAth absolutely, we get this from some EPoS terminals that aren't used all the time.

cmr · ‎Dec 26 2019

We use MS120, 210, 220 and 225 with networks that carry surveillance streams. We mainly use Axis and Bosch cameras, though do have some Samsung so I think you'll be just fine as we've had no issues in months. In fact they are excellent for this as you get good data on the streams, we picked up one quad FHD panoramic camera with a 24Mb stream...

cmr · ‎Dec 17 2019

In the Meraki dashboard you have an Organisation and one or more networks inside it. Each network can contain switches, APs and a router (or HA pair). The switch used for the WAN split should be in a separate network to the routers (MXs).

cmr · ‎Dec 17 2019

When using the MS, you do have it in a separate network to the MXs don't you? If in the same it can cause issues.

cmr · ‎Dec 17 2019

@sebastianfrancowe also tried Purple and while the technology does work, it stopped 90% (yes ninety percent) of our customers using the WiFi so we canned it.

cmr · ‎Dec 17 2019

I think this,along with the MX15.x train disappearing suggests that Meraki have someone new in the QA team who is treating the release in a more enterprise manner. While this is good for the stable versions, I liked the flexibility of being able to try the beta versions...

cmr · ‎Dec 17 2019

For about 1 day there was an additional tab called Ports for each MX and it did contain this information (and more), unfortunately it had numerous errors for some MX models so the page was pulled, never to be seen again... 😢

cmr · ‎Dec 13 2019

You can use any LAN port on most devices, out of interest why do you need a local connection, we have never used the local connection on our MSs?

cmr · ‎Dec 13 2019

So one of the few really useful possibilities for the individual licensing model isn't available. Hopefully Meraki might rethink this.

cmr · ‎Dec 11 2019

You also have different spanning-tree bpdu-filtering settings, you have 1/23 and 5/23 the same, not 5/24

cmr · ‎Dec 5 2019

That is somewhat longer than I'd expect 😞

cmr · ‎Dec 5 2019

5 minutes is normal, sometimes up to 10 but are you seeing much longer?

cmr · ‎Dec 3 2019

@Kavethis should be posted in the switching forum. I haven't used ACLs on L2 switches but they are supposed to work. Is it simply taking 20 minutes for the changes to take effect or is packet processing slow? What firmware are you running on the MS120? If you enable or disable a switch port how long does that take to actually happen, 20 minutes or much quicker? Can you add the VLAN in the rules as all the examples have the VLAN in there.

cmr · ‎Dec 1 2019

Support confirmed that there is an issue that seems to only affect certain configurations but they didn't respond when I asked for more information...

cmr · ‎Nov 29 2019

Yes, use the mx64s at remote sites to tunnel and either send over multiple VLANs (enable VLANs on the MXs), or once the tunnel, which if the MXs are in single LAN mode will now be for corporate, is up, change the public SSID to use the mx84 as a concentrator

cmr · ‎Nov 29 2019

@AshMead if you want two separate tunnels from each remote site to the concentrator in the DC then you will need two MXs in each site and have them in two separate networks. The alternatives to this, so that you only need one MX per remote site, are sending multiple VLANs over one tunnel or setting the public SSID at each site to use the central concentrator as the termination point.

cmr · ‎Nov 28 2019

Perhaps they found a major issue and then realised it applied to previous versions so pulled the lot until it can be fixed?

cmr · ‎Nov 28 2019

I can no longer see the MX15.x release firmware train, can anyone else see it?!?

cmr · ‎Nov 28 2019

It is a big dumb box once there are no 3000 series Cisco switches connected... The MS doesn't even tell you it is connected in the GUI!

cmr · ‎Nov 28 2019

LOL, you have them pretty much bang on! We had them left over from the old 3560s that the MSs replaced. We do only use them to protect stacks of 2 switches and I've yet to test the PoE when on RPS. With the 3560s they previously powered, the PoE did work (we have 750W/1100W PSUs in them) and did switch back okay, but with older (2960) switches that used the smaller connector, they were all but useless...

cmr · ‎Nov 28 2019

@PhilipDAthI'm pretty sure we are using Cisco RPS2300 redundant power systems on our MS225s and MS210s though it's been a busy week so I might be mistaken!

cmr · ‎Nov 26 2019

It can also happen if the link is overloaded and dropping packets.

About cmr

cmr

Community Record

Badges