Meraki

Peter-Loyen · ‎Sep 7 2021

I use a dedicated heartbeat/VRRP connection between MX nodes when the LAN network is not managed by us but by a 3rd party (i.e. the customer). The LAN is then an untrusted network with no visibility or management capabilities. The dedicated connection is using a separate vlan (access port). Whatever happens on the unmanaged LAN is not taken into consideration to trigger a failover but the WAN interfaces will ALWAYS trigger a failover. If the MAIN MX looses a WAN interface, there will be a failover to the SPARE MX. Tested and working

Peter-Loyen · ‎Feb 5 2021

Hi, I finally got it properly working. changes I've made: igmp querier and BCC server in same vlan and subnet, Although the latter is not really a hard requirement, but better to do anyhow. More important and very obvious but easy to overlook, disable unknown multicast stream flooding on all switches. 🙂 Tracing shows, clients need to explicitly join the streams and block these when leaving/changing the stream. it is all IGMPv3. What I do lack is a proper overview of the clients joining particular streams. Meraki is currently the only switch vendor not showing this. I made a request to Meraki to have this incorporated in the Meraki features. Thanks to all for your feedback

Peter-Loyen · ‎Feb 2 2021

Hi, I have the following setup: 1 MS120-24P --> 1 MS220-8P --> 1 MS220-8P On the MS120-24P is an IPTV broadcast center (BCC) On the MS220-8P are IPTV clients (smart TV and laptops with VLC) All IPTV nodes are in a separate VLAN100 All IPTV nodes join VLAN 100 via access ports On MS120-24P is an IGMP Querier configured All switches have IGMP snooping enabled. Now the issue: The BCC sends about 300Mbps of multicast stream into vlan 100 If I look at my IPTV clients, I see 300Mbps of multicast going to these ports, even if these are not sending IGMP messages. In fact, there is no request for multicast streams whatsoever. So why is the 300Mbps flooded? The IGMP Querier is not really doing anything at the moment. For the sake of clarification: the IGMP querier has an IP address in the vlan 100 subnet (172.16.20.0/24) but the BCC has an IP address in subnet 10.10.10.20. I cannot change the BCC subnet right away (not under my management) So what can be done to avoid the multivast flooding? This is just a lab setup, but this will go eventually into production in large scale IPTV networks. Thanks

Peter-Loyen · ‎Jan 28 2021

Hi, After checking all formulas and documentation of Meraki, it is still not clear how it really works: Example MX100 max 250 concurrent tunnels Max 500Mbps VPN throughput Let's say, I have an SDWAN network with 84 tunnels on the MX100 What is the exact throughput per tunnel? Other side of the tunnels MX64C. Thanks to clarify Peter

Peter-Loyen · ‎Jan 28 2021

SLAAC serves LAN subnets (i.e /64 subnets). Larger deployments /subnets, or dynamic WAN IPv6 assignment, benefits from DHCPv6 and RA. Look it from the pov of an ISP / MSP I think both should be possible Do you agree?

Peter-Loyen · ‎Jan 26 2021

Meraki, please make sure your most routable device, being an MX gets IPv6 fully compliant. LAN + WAN +DHCP, DNS, VPN tunnels, and NETSEC L3 This is a very weird fact, Meraki is very reluctant to answer and provide a proper roadmap and very slow at incorporate it in their ecosystem. I understand, Meraki is an enterprise solution, but even then IPv6 cannot be ignored any longer. Competitors are much further on the IPv6 roadmap: SD-WAN configuration for IPv6 (fortinet.com)

Meraki

Community

About Peter-Loyen

Peter-Loyen

Community Record

Badges

Re: Does Meraki MX Supported LAN VRRP?

Re: IGMP Querier purpose in an IPTV setup

IGMP Querier purpose in an IPTV setup

MX 100 throughput per tunnel

Re: WE Need IPV6 Support in MX

Re: WE Need IPV6 Support in MX

Re: IGMP Querier purpose in an IPTV setup