Meraki

Adam · ‎Jul 12 2018

We have a somewhat similar configuration and the internal IPs being used on the WAN interface should still work. It is somewhat similar to plugging in a DSL modem on the WAN port. If it isn't in bypass mode the MX gets a 192.168.x.x address and the gateway is the DSL modem 192.168.x.1. Some data points: You've said you connected the circuit directly to your laptop with the same 192.168.99.2 and .1 configuration and it worked? Are you using an identical configuration on the MX including DNS? Are you configuring the MX from the local configuration page and not the dashboard? I only ask because until the MX checks in it won't get any configuration changes.

Adam · ‎Jul 12 2018

Or if you want to see all ports in a given vlan you can go to Switch>Switch ports then click the drop down box in the search window and input the vlan number.

Adam · ‎Jul 11 2018

Thanks, this was a fun community event. The only critique I had of my first video attempt was that I talked super fast. But that is me in general. I also listen to podcasts at 2x on my phone. I look forward to participating in future community events 🙂

Adam · ‎Jul 11 2018

Glad you were able to get it figured out @Marco18

Adam · ‎Jul 10 2018

Yes that will work. It is less costly and a cleaner design in my opinion. I typically keep a spare twinax cable on hand as well if there is ever an issue but you could always failback to copper.

Adam · ‎Jul 10 2018

I have mine set for 12-54 and haven't had any trouble. I believe that is the default. But here is some documentation on the setting as well. https://documentation.meraki.com/MR/Radio_Settings/Minimum_Bitrate_Control

Adam · ‎Jul 10 2018

Thanks for following up on this. I was curious what the resolution would be.

Adam · ‎Jul 10 2018

I believe the only thing that won't get cleared by going through the above suggestions is the local static IP information which you can adjust by going to the local mgmt page.

Adam · ‎Jul 10 2018

Are you using Meraki switches and APs or a mixed environment?

Adam · ‎Jul 9 2018

I don't see anything immediately obvious. Is it throwing a specific error? Have you tried using Postman, it is free and helps design your queries and see responses a little more easily. You can also export queries in different code formats like Python etc...

Adam · ‎Jul 9 2018

I have the MA-SFP-1GB-SX in some of my switches and the port can be set to Auto or '1 Gbps Forced'. I suppose, conceptually, if the other side is less than 1G it could negotiate lower but I've never seen this since my far side is the same SFP so it is equally 1G capable.

Adam · ‎Jul 6 2018

May need to do that via LAN ports instead of WAN. Then set a default route to the vlan20 interface etc. But maybe others would have had more experience with this.

Adam · ‎Jul 6 2018

@rguthrie wrote: Thanks Adam~ I'll take a look at those links and give the install a shot. I take it you were able to get it working?

Adam · ‎Jul 6 2018

Awesome thanks

Adam · ‎Jul 5 2018

I haven't added a rule via API before but I have two observations. 1. The documentation says "Update L3 Firewall Rules" so I wonder if you are only allowed to update and not add. It doesn't clarify 2. The rules array appears to be required and make sure to pay attention that it uses a bracket instead of the curly brace so I assume the body of the postman request would be formatted similar to this { "rules": [ { "comment": "allow https - corp internet", "policy": "allow", "protocol": "tcp", "srcPort": "Any", "srcCidr": "10.0.0.0/8", "destPort": "443", "destCidr": "Any", "syslogEnabled": false

Adam · ‎Jul 5 2018

Depending on what you are looking for there are a few places to get that type of information 1. Network Wide>Traffic Analytics 2. Network Wide>Clients (Notice the pie chart on the right and click 'More') 3. Security Appliance>Route Table

Adam · ‎Jul 5 2018

Do you have a static route to get to the Cisco router interfaces? I wonder if once you create that 0.0.0.0 route it is eventually aging out some kind of cached route to the Cisco router. Although I'm not sure why bouncing the port would help this.

Adam · ‎Jul 5 2018

The equivalent setting to that in the Meraki Dashboard is under Switch>Routing & DHCP. Then you'd have to have a layer 3 interface for Vlan1 created and you can set the client addressing to "Relay DHCP to another server". In your case 10.32.1.29

Adam · ‎Jul 4 2018

I'd do what you suggested with twinax cables for high throughput.

Adam · ‎Jul 3 2018

Clearly I had to put on my Meraki socks to make this.

Adam · ‎Jul 3 2018

Setup the port as access and specify voice vlan 30 and data vlan 1

Adam · ‎Jul 3 2018

We did LACP for that purpose at one of our sites. What speed is the stack cable and how many ports are you wanting to setup in LACP?

Adam · ‎Jul 2 2018

Thanks everyone and welcome @jdsilva, I've appreciated a lot of the contributions you've made.

Adam · ‎Jul 2 2018

@diablo24 wrote: Thanks @Adam for clarifying. The documentation is a bit sparse when it comes to details about the functionality. Its difficult to understand. I agree, and in this case it is a lot different.

Adam · ‎Jul 2 2018

Meraki has a unique way of doing firewall rules compared to a traditional firewall. Here is an example. If you were trying to prevent a network server at 8.8.8.8 from being able to ping anything in your environment. On a traditional firewall you could prevent incoming icmp from 8.8.8.8. On the MX you'd instead create an outgoing rule to prevent ICMP to 8.8.8.8. It accomplishes the same thing of ultimately blocking the incoming traffic but it does it via blocking the response. It took me a while to wrap my head around this difference since I was used to traditional Cisco ACLs and Sonicwalls. A little additional info here https://documentation.meraki.com/MX-Z/Firewall_and_Traffic_Shaping/Firewall_Settings and here https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Layer_3_and_7_Firewall_Processing_Order

About Adam

Adam

Community Record

Badges