Meraki

rhbirkelund · ‎Sep 9 2020

I wonder if they are trying to ignore the missing NoNAT documentation. 😉 @CameronMoodyany news?

rhbirkelund · ‎Sep 1 2020

I would probably also consider doing a hard reset on the MX..

rhbirkelund · ‎Aug 30 2020

Is the vlan trunked all the way out to the AP? The vlan is being tagged on the switchport?

rhbirkelund · ‎Aug 30 2020

Rumour has it, it's a major routing loop. https://www.reddit.com/r/networking/comments/ijb8tn/global_as3356_level3_outages/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

rhbirkelund · ‎Aug 30 2020

Before we start the blaim game, let's wait and hear what actually happened.. If it is anything like the downtime from thursday in Europe, it' wasn't actually Meraki's fault, but a BGP peering issue from BT. That was a fun hour..

rhbirkelund · ‎Aug 30 2020

I'd be surprised if you're having a Complete Network Down scenario. It seems it's the cloud connection that has been lost, and all Meraki devices are designed to be able to continue switching - even in the case of lost cloud connectivity, after devices have been claimed, configured, and deployed. Are your clients experiencing a network down aswell? Are they not able to access company network ressources/internet, @Spack?

rhbirkelund · ‎Aug 27 2020

Seems dashboard is back online again? Devices coming back online.

rhbirkelund · ‎Aug 27 2020

Correction - I can log in, and get to MSP portal, but no Orgs in Chrome Incognito. My iPhone safari works, though. Also orgs.

rhbirkelund · ‎Aug 27 2020

I can access Dashboard when in Chrome Incognito mode.

rhbirkelund · ‎Aug 27 2020

Dashboard is up on my iPhone browser, and in Chrome Incognito? Denmark. Everything is still switching - seems like a dashboard outage.

rhbirkelund · ‎Aug 27 2020

Dashboard is not the only thing I lost. I got alerts that my entire CMNA kit just went offline?

rhbirkelund · ‎Aug 19 2020

Note that MR84 has dual band antenna ports. MR74 does not. So for MR74, you’ll need one antenna per band.

rhbirkelund · ‎Aug 13 2020

Well, it's Cisco best practice to use 192.0.2.1 as virtual ip for web authentication. So one could argue, that it should be allowed. 😉

rhbirkelund · ‎Aug 13 2020

The block is reserved for testing, I should still be able to configure it on an interface, that is not being used for traffic.

rhbirkelund · ‎Aug 13 2020

Today, while modifying a completely different VLAN this error showed up for a dummy vlan of mine: I was not able to continue, untill I changed the IP scope of this dummy vlan. Since when has this been a thing?

rhbirkelund · ‎Aug 12 2020

I tend to see "DNS is misconfigured" even while the configuration is verified, and correct. Often, it's due to some sort of caching going on, so I'd wait a couple of hours and see if it goes away on it's own.

rhbirkelund · ‎Aug 6 2020

2.4 GHz only is not a standard available feature, but you can just request it via Meraki Support, and they will enable it. Honestly, I doubt there is actually a live person activating it, when it comes to 2.4 GHz. Probably just a bot...

rhbirkelund · ‎Aug 5 2020

Try and create a dummy VLAN 999 with Subnet 192.168.255.0/24 and MX IP 192.168.255.1. Then set that dummy VLAN 999 as Native on ports 2, 3 and 4. Then make sure that all inter-switch links (links between switches) are trunk, with native vlan 999, and all VLANs are allowed on the trunk.

rhbirkelund · ‎Aug 2 2020

Hah... I was actually looking at that post earlier. Didn't see the he mentioned the Make A Wish..

rhbirkelund · ‎Aug 2 2020

Hey Where does one provide feedback on bugs in the Meraki Public Beta App? Just the Make A Wish? I have two screenshots to accompany.

rhbirkelund · ‎Jul 23 2020

I believe what @JimmyPhelan is trying to convey is that Meraki Autovpn feature only works between Networks within the same Organizations, in terms of Meraki. If you have MX'es at all locations, but they are not in the same organization, you'll have to treat the Site-to-Site VPN as third party VPNs. You will not be able to leverage Meraki's AutoVPN feature.

rhbirkelund · ‎Jul 23 2020

Are you perhaps able to share the configuration as shown in Uplink Selection and SD-WAN policies, found under Security & SD-WAN -> SD-WAN & Traffic Shaping?

rhbirkelund · ‎Jul 22 2020

Thanks for the appreciation. 🙂

rhbirkelund · ‎Jul 15 2020

In principle, as long as Juniper abides by the 802.3 Ethernet standard there shouldn't be any interoperability issues. Make sure the SP provides a /30 (or /29 for Warm Spare setup), and a RJ45 jack, assuming anything lower than MX250.

rhbirkelund · ‎Jul 7 2020

Since you are replacing an ASA with an MX, I'll just have to say this. A Meraki MX100 is not a Cisco ASA firewall. So don't be surprised if there is some functionality in an ASA that isn't present on an MX. I've had my fair share of rogue Sales persons, thinking an MX can simply replace an ASA, without having looked into the running configuration. You can not assign an IP address to an physical interface of an MX (or any other Meraki product). So in order to obtain what you are depicting, you'll have to create a VLAN on the MX, and assign it an IP, and a SVI interface on your core switch. Just as others already have mentioned. Basically, what you are doing is, a Layer 3 topology as described in https://documentation.meraki.com/Architectures_and_Best_Practices/MX_and_MS_Basic_Recommended_Layer_3_Topology Assuming you are handling DHCP somewhere else, then creating the VLAN on the MX, remember to disable the DHCP server, that is created by default.

About rhbirkelund

rhbirkelund

Community Record

Badges