Meraki

cmr · ‎Nov 20 2019

No, as @General-Zod and @BrechtSchamp said an MX pair is active-passive with up to two wired and one cell uplinks (depending on model).

cmr · ‎Nov 13 2019

Did it come out before Meraki PoE switches existed? The current install guide just mentions an af switch, not particularly a 3rd party one. MR66 (EOS) Installation Guide

cmr · ‎Nov 6 2019

@tomas209cawe had the same with our MX15.17/18 images when 15.20 came out, I believe as it fixes a significant performance bug. Interestingly it didn't propose to upgrade 15.14 devices. We also had similar with switches on MS11.25 as again there was what appears to be a significant bug fix. As @PhilipDAth said the auto beta off feature is just so that a stable image is not suggested to go to beta, or automatically upgraded by Meraki. We are using MX15.14 on the MX250 HA concentrators at our SD-WAN core, MX15.20 at most other sites that have HA pairs of MX100 or MX84, with a couple of the MX84 pairs on MX15.21. Our single internet access only MXs are all on MX15.21 and were on MX15.20 when it came out. We haven't, touch wood, had any issues...

cmr · ‎Nov 4 2019

We get the same on one (busy) site, so much that I made the other ISP the primary. The issue still persists, though perhaps a little less frequently. Having seen this I'll log it with support as both ISPs cannot see an issue and the users don't either. Funniest thing is that they are both MPLS links and the default routes are on the same stack at our main DC and from there they both go through the same internet firewall, even on the same rule, so not sure how one is down when the other is up...!

cmr · ‎Oct 31 2019

@redsectorAll of those APs should be able to run 25.x or 26.x, I'd upgrade as there are a lot of improvements!

cmr · ‎Oct 30 2019

@DarrenOC you have done multiple full stack Meraki installs, you must have come up against this?

cmr · ‎Oct 30 2019

@JoshRans didn't you say you stacked them? You will then just have one IP on the VLAN on the core switch stack and the other on the ASA LAN port. We do this as @Nash described with a 'firewall' VLAN that only exists between the core and the edge.

cmr · ‎Oct 30 2019

@Denathis works fine, I used to have this setup at my home with an MX64 for 3 years and it never went wrong.

cmr · ‎Oct 25 2019

For SD-WAN you can create traffic steering rules to prefer routes that don't have, for example, packet loss over 1%. We created a rule that has excatly that setting and make our VDI traffic obey it as that really doesn't like packet loss. When we have had tail circuit or provider core issues you can see the traffic all being steered to the other loss free link.

cmr · ‎Oct 25 2019

If you have Meraki suggest an upgrade at a certain time and you choose to reschedule it to an earlier time, then the upgrade happens at the new time but the dashboard warning stays there until the upgrade has completed, in your case where I'm guessing you have rescheduled to later I'm not sure what will happen, I'd have thought it will be at the new time but I'd raise a support case just to be sure...

cmr · ‎Oct 22 2019

Love the community, best resource out there. Thank you everyone 😎

cmr · ‎Oct 20 2019

For the MX series in routed mode, you can enable VLANs in the Addressing and VLANs tab. Once you have done this you can assign an access VLAN, or a trunk of multiple VLANs to each LAN port. If you also set up IP addresses for the VLANs then you can route between them. So although you cannot create a router port (in the traditional Cisco sense), you effectively can as you can have 24 VLANs with 24 IP addresses/subnets and apply one to each LAN port of the MX250.

cmr · ‎Oct 10 2019

@AndyM did you have any luck with the process we followed?

cmr · ‎Oct 8 2019

We have done several physical stacks and as @PhilipDAth said, as long as you power them up first on their own before physically stacking them, you will be okay. We have followed the following process: Create the stack in the dashboard by adding the serial numbers Plug in switches on their own with internet access and leave for a few hours Power off switches Install one of the switches in destination and power up, connect devices if needed, to free up space in panel if replacing other switches etc. Install second switch in destination and connect stacking cable(s), then power up Add third etc. if required. As long as you aren't using layer 3 features (we aren't), then it all works fine and there are no connectivity issues for clients, switch reboots etc. We did this with 10.x firmware but haven't added any more yet since moving to 11.x

cmr · ‎Oct 7 2019

Yes, we use a similar design but we use dumb layer 2 switches for the WAN side of the MXs i.e. Provider 1 -> L2 switch 1 -> WAN 1 on both MX84s. Provider 2 -> L2 switch 2 -> WAN 2 on both MX84s We have 3x IPs from each WAN provider as the HA uses the WAN, not the LAN side in SDWAN mode so that you ensure traffic continuity during failover of MX. One goes to each MX and one is the floating 'virtual' address. On the LAN side we have 1 port from each MX into two different L3 switches that are stacked together (Cisco 3850s in our case). We use a dedicated VLAN and subnet for the MX to 3850 connection but you could trunk if you prefer.

cmr · ‎Sep 25 2019

@Htahayou can stack all variants of MS225 switches with each other and also with MS210 switches. We have stacks of MS225 48 port switches mixed with MS210 24 port and MS210 48 port ones (all with PoE but that doesn't matter). They work absolutely fine together.

cmr · ‎Sep 19 2019

That does seem odd, back to using a PC (or similar), if you connect it to the trunk port and set the NIC to VLAN 347, does it get an address from the appropriate DHCP pool?

cmr · ‎Sep 19 2019

Do you have a layer 3 interface for each VLAN on the MX, I'm guessing you need it to create the DHCP pool but as all our MXs are in single LAN mode I thought best to ask..

cmr · ‎Sep 19 2019

Have you set a VLAN tag on the AP itself, we have (ahem) about 9 SSIDs all with their own VLANs and we trunk to the APs with one VLAN set as native and all others allowed. The native VLAN isn't 1, but all our APs are connected to Cisco or Meraki switches, not MXs, I do think though that you are supposed to be able to trunk from an MX

cmr · ‎Sep 19 2019

If you set a port as access VLAN 347 on the MX and plug in a device, does it get an IP from the the MX DHCP pool?

cmr · ‎Sep 16 2019

@PhilipDAthI think you are correct, it *should* show up there but there appears to be a bug where if you choose custom ports, the traffic doesn't show up...

cmr · ‎Sep 16 2019

@SFascotoh my, that is slightly under provisioned! You could put a PoE switch in the location and run cables locally I guess as one was or another you are going to need a significant number of additional APs...

cmr · ‎Sep 16 2019

Thanks @PhilipDAth That isn't ideal but would be acceptable. I gave it a go but as I need to recognise traffic on a particular port I created the below: Now on the clients screen when I look at the custom pie chart I get: More than 90% of the traffic for the network is on port 7563 and it was added last week, but it looks like the custom slices don't work with custom ports!

cmr · ‎Sep 16 2019

@-ray- which vendor are you using for the WAN devices, some of the ones we use now come with 40GbE interface cards so that might help?

cmr · ‎Sep 16 2019

Did you follow the instructions below and did you choose manual, if so what do you have for the first 3 and what are the equivalent on your router/firewall/L3 switch? 1. Connect the Ethernet cable from the theater network to the Management port on the input panel. 2. In the left navigation menu, tap Service Setup > Network Settings. 3. In the Port list, tap Management. 4. Enter the network settings: • To obtain the network settings automatically, tap Automatic. • To enter the settings manually, tap Manual and complete these fields: Field Description IP Address The IP address of the projector. Subnet Mask The subnet mask to which the IP address belongs. Gateway The IP address for the network gateway. Primary DNS The IP address of the primary DNS server. Secondary DNS The IP address of the secondary DNS server. 5. Tap Save.

About cmr

cmr

Community Record

Badges