Meraki

rhbirkelund · ‎Mar 15 2019

I might just be me, who is unable to google it. But when will the Meraki Documentation be updated with the new MX Beta feature on NAT Exceptions?

rhbirkelund · ‎Mar 15 2019

My local Meraki man: https://www.instagram.com/p/BvAKe_tBOxzAiGpfY7FzKvmxgC/ 😉

rhbirkelund · ‎Mar 13 2019

On the MX64, only LAN4 can be converted to WAN, and requires access to the Local Status Page, inorder to conver the port. https://documentation.meraki.com/MX/Installation_Guides/MX64_Installation_Guide#Setting_up_secondary_WAN_interface_(dual_WAN)

rhbirkelund · ‎Mar 13 2019

The MX67C/MX68CW contains a 3G/4G modem which can be used for cellular failover (3rd WAN interface-ish). Otherwise, no. All MX'es support only 2 WAN interfaces. MX250 and up, have two dedicated ports. MX100 and below, has one dedicated port, and one shared, which can be converted.

rhbirkelund · ‎Mar 13 2019

Unfortunately, no. The MX64 supports only two WAN interfaces.

rhbirkelund · ‎Mar 5 2019

Huh... That's odd... I'm getting the same error... I'm certain I've done this earlier...

rhbirkelund · ‎Mar 5 2019

Looking forward to more technician focused education on Meraki, rather than Sales focused pitches!

rhbirkelund · ‎Mar 4 2019

It is whether or not you are utilizing IEEE802.1Q to tag frames. Leaving the VLAN ID field empty, you are not tagging the frames, but they are still using 802.1q trunking. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Fundamentals_of_802.1Q_VLAN_Tagging

rhbirkelund · ‎Mar 4 2019

@Anonymous wrote: [...] All SA ports are in Trunk - Native VLAN 10 - Allowed VLANs: all [...] If VLAN10 is native try keeping the VLAN ID field empty on the AccessControl Page for the SSID, but keep VLAN tagging enabled.

rhbirkelund · ‎Mar 4 2019

Every time I'm in a situation where I need to clear a DHCP lease on Meraki, I hit this button so hard... There is no way (that I know of) to clear a DHCP lease manually in Meraki. Best is to lower lease time, in the DHCP server, and wait for the leases to renew, to the shorter lease time.

rhbirkelund · ‎Feb 28 2019

@JordanNolan wrote: Trying to find the quickest way to locate a bandwidth hog in real time going through the MX100. Sometimes I see in Appliance Status -> Uplink I am hitting 125 MB of my 200 MB connection. Checking the total MB for the clients for the past 2 hours is not very helpful because I am seeing file server and database traffic to an from clients over the switches as well. I just want to see how much is going through the MX in the last few minutes and the break down of who is doing it. I would like to avoid having to download packet captures and counting the bytes if I can. Something I can do right in the interface would be great. If you feel like messing around with the Meraki API, you might find som inspiration here; https://github.com/meraki/automation-scripts/tree/master/topusers

rhbirkelund · ‎Feb 26 2019

You can verify the DHCP stats, by clicking on Security & SD-WAN -> Monitor -> Appliance Status, and then going to DHCP tab.

rhbirkelund · ‎Feb 25 2019

Of course. 😊

rhbirkelund · ‎Feb 25 2019

Looks good 😊

rhbirkelund · ‎Feb 25 2019

What you are doing there, is basically the reverse. If you want to hand out addresses 0.2 - 0.254, and 1.1-1.254, You would have to reserve 192.168.0.1 and 192.168.0.255. In reserved IP ranges, put; 192.168.0.1 , 192.168.0.1 and 192.168.0.255 , 192.168.0.255.

rhbirkelund · ‎Feb 25 2019

@MerakiDave wrote: If I understand the earlier power question correctly, then no, the MR30H should require 3at power on its uplink port in order to come up AND be able to pass through 3af power on port 1. It should NOT be able to uplink with 3af power and simultaneously have 3af passthrough on port 1. That is also what I meant, I believe. I was just unable to word it properly. Thanks. 🙂 Inorder to power 3af out it's LAN ports, it must be power itself with 3at. 🙂

rhbirkelund · ‎Feb 25 2019

@DrewF; If the LAN port is set to the same VLAN as AP management, you could run an Guest SSID with MEraki DHCP on a daisy chained AP. I think. Without having tested it. Meraki DHCP NATs directly on the AP, with the APs mgmt IP address. So assuming your AP mgmt vlan is 10, setting that as access port on the MR30H LAN port, would allow for the daisy chained AP to NAT to that address and vlan. Again, without having tested it.

rhbirkelund · ‎Feb 25 2019

I had a discussion with a customer and Account Manager the other day, whether this was possible or not, and whether the solution would be "good". From what I read, the MR30H requires 802.3af but with .3at recommended, and gives .3af out the LAN ports. The customer is having a scenario where he would like to run two MR30H in daisy chain from one switch, rather than running them both down to the switch. I kept trying to say that I doubt it would work, yet I was unsure completely. Usually the AM only hears "maybe" and automatically assumes that as a "sure, it works".

rhbirkelund · ‎Feb 25 2019

Does anyone have any experience with daisy chaining MR30H APs? Is it possible at all? I'm not expecting that it can fully power tiered APs, but with a power injector, it should be possible power-wise. Can the ports on the MR30H trunk?

rhbirkelund · ‎Feb 11 2019

@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?

rhbirkelund · ‎Feb 3 2019

I have a customer atm installing ANT-27 and ANT-3-F5. Waiting for him to finish up the installation, and then I might have him take a couple of pictures.

rhbirkelund · ‎Jan 29 2019

I cannot speak for Meraki, but on our Exchange/ActiveSync, there was a policy which would enforce a factory reset, when inputting the wrong code on iPhones too many times. Some of my colleagues learned of the policy the hard way, while lending their phone to their children.

rhbirkelund · ‎Jan 25 2019

@PhilipDAth We upgraded both switch and MX to latest beta release, to no luck. I'll have a look at that forum post. @AndyPan All links are trunk and allowed all VLANs, except for my Internet uplink. That is a dedicated vlan, on access ports (which not by my good will is allowed on the trunk). So no vlans are pruned along the way. They grey links on the drawing by the way, indicate links that are physical in place but disabled. Since we got it working, all links are enabled, and continue on working.

rhbirkelund · ‎Jan 25 2019

So for the last couple of months I have been troubleshooting an issue with two MX64s Warm Spare. My two MX'es kept going into Dual Master Mode, thus exhibiting a Split-Brain situation. I have had Meraki Support with me on this one, and we just couldn't seem to discover why this was happening. Layer 1, -2 and -3 connectivity has been verified. All links are trunk, and no VLANs were being pruned. MX'es could ping eachother, and VRRP messaging was being recieved by eachother - they were just not reacting to the VRRP messages. This was confirmed via packet captures. Connecting the two MX'es directly to eachother, remedied the issue, but since this is not best practice we disconnected them again. Dual Master mode back. Yesterday, we had a breakthrough. After enabling "Flood unknown multicast traffic" my two MX'es more or less instantaneously went into Master/Passive. Now I'm trying to determine why this is neccessary, because I have another installation that is also running Warm Spare, and this setting is _not_ enabled. Why? What does "Flood unknown multicast traffic" do? I might not be all to keen on multicast, but I'm trying to understand why this is neccessary.

rhbirkelund · ‎Dec 30 2018

@PhilipDAth wrote: From an external point of view syslog, syslog-ng and rsyslog all look identical (when using udp/514). You can just use rsyslog. You wont need to install any otehr syslog daemon at the same time. That is also my plan. To just use rsyslog, since it is native with the RPi. But I want to split the meraki events to a separate log file, so I don't end up cluttering the RPi events with Meraki events. As well as, maybe do some Linux best practices. I was hoping someone had any experience with rsyslog and Meraki, and perhaps be willing to share a conf-file.

About rhbirkelund

rhbirkelund

Community Record

Badges