Meraki

Jabettan · ‎Aug 2 2024

As per the Legacy products notice for version 18.107.11: This firmware version is only available for MX64(W), MX65(W), MX84, MX100, and vMX100 appliances. Any other devices configured to this firmware version will not upgrade. The devices we are using are not in this list. Regards

Jabettan · ‎Aug 2 2024

We updated from 18.107.2 to 18.211.2 on 2024-07-05 This is on an HA pair of MX68. There were no issues at first but over time the connection got progressively worse. On both WAN1 and WAN2 we were getting an additional 300ms of latency. Jumping anywhere from between 5-100mbps on both upload and download on a pair of 500mbps circuits. When removing all downstream devices except for a single laptop connected to a test port the latency and bandwidth improved a bit but nothing close to what we were getting prior. Called support and downgraded back to 18.107.2 and all issues disappeared. As per-support we were at 100% utilization. Post downgrade we were under 40% We will wait a few days then path to 18.107.10

Jabettan · ‎Dec 11 2019

Oh boy . . . here we go . . . SSL VPN client and/or WireGuard VPN client and/or Cisco AnyConnect VPN client. IPv6 on WAN and LAN. The ability to split out client VPN logs from Site to Site VPN logs. The ability to assign a group policy to a static route. not just a VIF. The ability create aliases for objects and assign firewall rules to those objects, not just IPs. The ability to set up more than 2 WAN connections. and for the things that can actually be implemented: Layer 7 firewall allow rules, eg. deny all video and streaming but allow youtube. Configuration changes backup and restores. Alert when the secondary WAN is down, not just the primary.

Jabettan · ‎Jun 19 2019

I have just tested this with a Z1 and confirmed at the minimum it could hand out 500 leases over 4x /25 subnets @Patrickpu wrote: How did you run 100-200 computers off of 1 Z1? These things have a cap of IPs that they can utilize...right? I believe they can only run a /29.

Jabettan · ‎Jul 26 2018

Create a VLAN for the MPLS. Take another LAN port and set it as an access port for the MPLS VLAN. Plug the MPLS into that port. Create your routes.

Jabettan · ‎May 10 2018

HI @MerakiDave, @Bovie2K I just tested this today. The Z3 is artificially throttled in firmware to 100mb/s. Tested a Z1 with the same config on the same ISP and are getting a little over 200mb/s. As a confirmation I called up support and opened a ticket. Support confirmed this is intended behavior and that the Z1 will be functionally faster in some scenarios.

Jabettan · ‎Mar 27 2018

So I was able to kludge together a working solution but I wanted to know if there is a better way. Put the MX in Track Clients by IP address mode Create VLAN on the L3 switch for clients Create VLAN for routing on the MX for communication with the L3 switch Create the same VLAN for routing on the L3 switch for communication with the MX Create Group Policy on the MX and apply to the Routing VLAN Create Static Route for the VLAN behind to the switch using the VLAN routing to the switch Create PBR (policy based routing) on the L3 switch using the MX's "VLAN for Routing" interface as the Default Gateway Here is a screenshot for what it looks like MX side: (Obviously PBR is different based on your switch vendor).

Meraki

Community

About Jabettan

Jabettan

Community Record

Badges

Re: 18.211.2 Out - Promoted to Stable/ Several Fixes

Re: 18.211.2 Out - Promoted to Stable/ Several Fixes

Re: A Guest Community Challenge!

Re: Z3 Throughput

Re: WAN 1 and LAN PORT

Re: Z3 Throughput

Group Policies per static route for clients behind a Layer 3 switch

Re: Z3 Throughput

Group Policies per static route for clients behind a Layer 3 switch