Meraki

jdsilva · ‎Jan 21 2020

Not that I know of 😞

jdsilva · ‎Jan 21 2020

Hey @jlopez_sv81, Yes, by default the MX will NAT all LAN traffic to the single WAN interface IP. Previously, you couldn't actually disable this behavior at all, but the more recent 15.x version have a No NAT feature that's in beta that can be enabled by support.

jdsilva · ‎Jan 20 2020

**EDIT** Removing my comment. I was totally wrong and @ww called me out on it 🙂

jdsilva · ‎Jan 20 2020

Hopefully this will help?

jdsilva · ‎Jan 20 2020

@Thygesen the image you're showing us is not the Summary Report. You need to navigate to Organization > Summary reports as @ww said.

jdsilva · ‎Jan 20 2020

Yeh I'm with @NolanHerring and I wouldn't think that power changing would drop clients, but I wouldn't bet money on it since I've never dived into that topic. Interesting though.

jdsilva · ‎Jan 17 2020

Hey @jsurles , Go to Security & SD-WAN > Firewall and change this setting: This will allow you to reach the local status page from a remote location. Just don't forget to change it back when you're done! 🙂

jdsilva · ‎Jan 16 2020

Hey @ScottPR , For web stuff going to www you would forward ports 80 and 443. For mail you would forward port 25 (for SMTP, wihch is the most likely port). You don't need to do any header based forwarding for this.

jdsilva · ‎Jan 15 2020

This should be the endpoint you want: https://dashboard.meraki.com/api_docs#update-the-policy-assigned-to-a-client-on-the-network

jdsilva · ‎Jan 15 2020

Yup, Nuage is using a 1.0/2.0 version system to describe their platform. I hear lots of promises on the 2.0... But I have yet to see an actual product. This doesn't really apply to other vendors though. If you really want to see hype then check out Gartner's SASE term.

jdsilva · ‎Jan 15 2020

Congrats and welcome to the new All Stars!

jdsilva · ‎Jan 15 2020

The only SD-WAN vendor I'm aware of doing L2 right now is Nuage. I wouldn't be surprised to see others add that in the future... I know the MEF70 spec explicitly puts L2 out of scope for the first iteration, but does state it may be added in the future.

jdsilva · ‎Jan 11 2020

@cmrThat's been updated. Routed mode is now supported: https://documentation.meraki.com/MX/Site-to-site_VPN/Using_OSPF_to_Advertise_Remote_VPN_Subnets And concentrator and passthru modes are really the same modes, so passthru does work. I think the problem here is what's already been called out. This is for VPN hubs only, spokes will not advertise routes. But I haven't tested this myself.

jdsilva · ‎Jan 7 2020

IMO rootguard is not appropriate here. For Meraki AP's you can set BPDUGuard on the port facing the AP as they don't send BPDU's and can be considered an end device.

jdsilva · ‎Jan 3 2020

Well deserved @TimBecker and @Greenberet ! And a stellar effort from @PhilipDAth @BrechtSchamp @Nash & @NolanHerring ! Awesome work everyone.

jdsilva · ‎Jan 3 2020

I don't think that's correct @BrechtSchamp . I am able to claim a device in an a different Org as long as I remove it from the network in the Org where it currently resides. As well, Meraki docs seems to indicate that as long as a device is not in a network it can be claimed by anyone. https://documentation.meraki.com/zGeneral_Administration/Inventory_and_Devices/Using_the_Organization_Inventory#Claiming_Devices

jdsilva · ‎Jan 2 2020

Just remove it from the network it's in. There's also an "unclaim" button under Organization > Inventory you can use.

jdsilva · ‎Dec 21 2019

@BrandonSis correct: https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/SSID_Modes_for_Client_IP_Assignment#NAT_Mode Wireless clients cannot use Layer 2 discovery protocols to find other devices on either the wired or wireless network.

jdsilva · ‎Dec 20 2019

I believe so, yup, You got 30 days and then you better pay the man 😉

jdsilva · ‎Dec 20 2019

Yes, if you end up in an expired license situation all of the devices in your Org will cease to function.

jdsilva · ‎Dec 12 2019

Just to add to @AjitKumar 's reply, each MX must have its own unique IP address to maintain a connection to the Meraki cloud. They cannot share one IP for this function.

jdsilva · ‎Dec 11 2019

Only what's available in the local status page. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page Your other option is to call support. They can sometimes see stuff you cannot with regards to dashboard connectivity. The device may show offline but they mat still be able to access it and recover it.

jdsilva · ‎Dec 10 2019

@GraphiteJess wrote: We've been over it a few times, though I'm not sure the mask is set correctly; they have reserved IP's if they're getting it via DHCP, though I'm pretty sure we configured them manually. Are you able to compare what is configured on the PLC vs what is set up on the VLAN on the MX?

jdsilva · ‎Dec 10 2019

@GraphiteJess wrote: When the PLC ARPs for my computer's IP on the VPN, it does NOT get a response from the MX. Nor should it, unless Proxy ARP is enabled, which I'm not sure the MX supports. So what this sounds like to me is that the PLC either doesn't respect the default gateway setting or the subnet mask is configured incorrectly. The only way the PLC _should_ ARP for a device not on the subnet is if it doesn't have a default gateway (solved by Proxy ARP) or if it thinks the IP is on its local subnet when it's really not (incorrect mask). If the mask is correct and the PLC refuses to use its gateway to get to another subnet then it could be worth a try calling support to see if they can enable proxy ARP.

jdsilva · ‎Dec 9 2019

Not that I've seen, no.

About jdsilva

jdsilva

Community Record

Badges