Thanks a lot for all the advise and help, finally managed to fix it.   Apparently turned out that the ISP in this case (Aussie Broadband) uses CG-NAT (https://www.aussiebroadband.com.au/support/knowledge-base/nbn/cg-nat/). Got on a call with them and opted out of CG-NAT and everything came on track.  ... View more

Hello @Aaron_Wilson , Normally, disabling a port on the MX through Dashboard will not show green when connecting any device to the MX on the disabled port. As pointed by other users, the same behavior is not noticed on MX64s. I would definitely recommend you call into support and have them investigate. There are 3 possibilities 1) This is a UI issue and the development team will need to be engaged.  2) This is a dashboard issue and upgrading the firmware might fix the problem (I would upgrade only if recommended by Meraki support as a fix) 3) This is a one-off issue and possibly factory reset should take care of it.    Either way, I would recommend you have this documented through a case with Meraki support so they can take this up with the development team if required.  ... View more

@netminator wrote: Hi all,   Can someone advise if it is possible to gain access to a network lab/sandbox with a set of specific devices (Z3) and access it via Dashboard and API?    I would like to test deploying a medium size network using APIs, but getting multiple Z3s just to prove the concept seems to be a rather bad idea  😉   Any thoughts? Otherwise if you have a Cisco Account, you might be able to access the Cisco dCloud Meraki Demo for Partners. You won't get configuration access nor API access, but you'll be able to access a Full Stack Meraki and all topology configurations. It's primarily meant as a demo tool for partners towards end costumers.    https://dcloud2-lon.cisco.com/content/instantdemo/cisco-meraki-launchpad-v1-instant-demo-partner?returnPathTitleKey=content-view&isLoggingIn=true ... View more

@Marcel wrote: I'm a bit jeaous as don't have one yet, but it should go in this order: Gig->mGig - 10G -40G   So for your MS355-48X2 it should be 1-24 1G 25-48 mGig 49-52 10G 53-54  40G     Awesome, that is also my suspicion @Marcel. Thank you, and @PhilipDAth aswell. 🙂   It wasn't to much the switch specs, but more, which ports are GbE and which are MGig. Then I can make sure the technician onsite cables things correctly. 🙂 ... View more

SoCalRacer,   Thank you that was it, there was a random layer 3 wireless firewall rule blocking access to the local LAN. Must be a default policy because I hadn't set it.   Thanks again,   Phil ... View more

And just in case anyone else needs to do this, here's what I did.   http://blog.brokennetwork.ca/2019/05/lets-encrypt-for-meraki-webhooks-and.html     ... View more

@kYutobi wrote: @jdsilva I think you also need a CCNA equivalent or work experience for it.    Who should attend? ECMS1 is recommended for Meraki operators interested in introductory-level technical training or in preparing for the Cisco Meraki Solutions Specialist certification.   As it is a technical course, individuals should be CCNA-certified or have an equivalent level of technical expertise.   We do not recommend that those who have already attended CMNO attend this training, as the content is the same. This is mainly to ensure that participants know about networking, know what a switch is, and so on. I'd say, after attending CMNO, that participants who don't know basic networking, will not benefit from the CMNO course. That being said, CCNA is not a requirement. Only a recommendation. I attended the CMNO with a colleague of mine (Solutions Architect in datacenter), and he struggled a bit in navigating the dashboard, and typing things in correctly.... ... View more

Worked like a champ @rhbirkelund ! Thank you and very helpful, Kudos for you! ... View more

Hi @Weggy ,   When it comes to Netflow I am a newbie if there is any guide that you can provide or refer me to something, please do so. It's highly appreciated.  ... View more

Yes - I've come across similar, with store numbers, in retail chains.   I'm never a fan of doing your IP addressing based upon anything like that.  IP addressing wasn't designed for it and you often end up 'standardising' on something that then ends up with anything > 254 being non-standard.  A standard that works only some of the time is worse than knowing you have no standard - and using an IPAM tool - IMHO. ... View more

Thats normal because al traffic tunnels to you wlc/appliance. The switch does not know whats inside the tunnel packets.    https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/SSID_Modes_for_Client_IP_Assignment ... View more

Basically Meraki's DHCP server will hand out IP addresses from the range that was defined for the subnet in the Security & SD-WAN > Addressing & VLANs page.   In your case the subnet is 192.168.0.0/23. I assume you know what that /23 means, but if you don't... It means the following: -network address for the subnet is 192.168.0.0 (cannot be used) -broadcast address for the subnet is 192.168.1.255 (cannot be used) -host addresses go from 192.168.0.1 up to 192.168.1.254 (can be used) -subnet mask is 255.255.254.0   In you configuration the MX is configured to use 192.168.0.1 as its own address, so that will not be handed out to clients, the rest of the host addresses will be handed out to clients: 192.168.0.2 up to 192.168.1.254.   The Reserved IP ranges function is there for IP addresses you want to keep available for static IP configuration, or to be used by another DHCP server or... So those addresses will not be handed out to clients by Meraki MX DHCP (unless fixed assignment, see below).   The Fixed IP assignments list is for when you want to assign specific IP addresses to specific MAC-addresses via DHCP. You can use addresses from the reserved ranges here, and it's probably a good idea to do so. This list also gets edited when you assign fixed IP-addres to a client from the Network-Wide > Clients page.   The screenshot you posted shows some details about this range. We see that indeed there are 510 usable addresses in total (192.168.0.1 up to 192.168.1.254), 1 is used by the MX, and 2 are used by other clients. This leaves 507 free addreses.   Hope that's clear!   ... View more

Of course. 😊 ... View more

@PhilipDAth wrote: It sounds like the switches were not processing multicast traffic correctly.  Are you running 10.x (like 10.43) code on the switches?   Also check out this excellent post on multicast configuration when you have more than one switch. https://community.meraki.com/t5/Switching/Multicast-Basic-s/m-p/25867#M2125 I read in to this, but I'm still unsure about this.   IGMP Snooping, allows us to send and recieve multicast streams out the same ports. If this is disabled, then we cannot recieve multicast streams stemming from ports where we send out multicast streams. Basically, depending on who comes first, whichever MX will not be able to reply on multicast streams.    Flood unknown multicast traffic; will allow the switches to flood multicast traffic out all ports. But is VRRP considered unknown multicast traffic? Or maybe multicast traffic with unknown source/destination, is just flooded out all switchports? ... View more

This was actually my 1st thought but we don't have that in place... I am still puzzled. ... View more

Splitting the log file by IP address is an easy way of doing this. https://firegenanalytics.com/2018/02/configuring-rsyslog-to-split-the-logs-by-device-ip-and-rotate-the-logs-on-daily-basis/ ... View more

The MX64 is software limited to 250Mb/s.  It wont go past that.  The software wont allow it.   Consider getting an MX67.  It is software limited to 450Mb/s.  Paying the extra to go from 450Mb/s to 600Mb/s would mean going from an MX67 to an MX100 - and it's probably not worth the money.   We use an MX67 in our office and it works great. ... View more

@BrandonS wrote: @jdsilva wrote: It's a binary file. You cannot read it without knowing how to decode it 😞 That sounds like a challenge to me 😉 Neo, is that you? ... View more

@PhilipDAth Thank you  ... View more

Thanks all for your help, its works now 🙂 ... View more

Right it does not work. ... View more

I think your tough out of luck with using 2.4GHz in that environment.     The spectrum analyzer that is built into the Meraki access points is 'neat' but I've never found it to be accurate so I don't rely on it that much. With that being said it does seem to show a higher noise floor due to all the activity in that location.   If I were you, I would look to upgrade the devices that are 2.4 only with dual band chips ... View more

Additionally, from what I read, if you have a VPN to your MX (Client or Site-to-Site), you won't have to reinitialize the the VPN tunnel. Credentials are shared between the MX'es, so if one looses connectivity, you don't have to wait for the VPN tunnel. ... View more