Meraki

alemabrahao · ‎May 25 2023

Have you already done a test with configuring an external DNS? Just to confirm if it could be something DNS related (which I find difficult). What type of authentication are you using?

alemabrahao · ‎May 25 2023

https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades

alemabrahao · ‎May 24 2023

I suggest you open a support case.

alemabrahao · ‎May 24 2023

Before You Begin You must have the following before you begin: An Azure virtual network (vNET, also known as a VPC) where you will deploy the vMX. This vNET and its corresponding resource group can be the same one as the resources you plan to access across the Meraki VPN or a different one. Refer to this Azure document for creating these resources. You MUST have an "SD-WAN" subnet inside the vNET where the vMX will be deployed which is separate from the subnet(s) where the resources you plan to access through the VPN are hosted. Ex. If your apps and resources are located in the "production" subnet, you will deploy a second subnet in the same vNET called "SD-WAN" in which the vMX will be deployed. DO NOT deploy the vMX inside the production subnet alongside the other resources as this can result in a routing loop and packet loss within the Azure environment. A NOTE FROM AZURE: Deploy a virtual appliance into a different subnet than the resources that route through the virtual appliance are deployed in. Deploying the virtual appliance to the same subnet, then applying a route table to the subnet that routes traffic through the virtual appliance, can result in routing loops, where traffic never leaves the subnet. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview#user-defined

alemabrahao · ‎May 24 2023

What is the power consumption displaying for the port where the AP is. Remember that the MR46 needs at least 30w (802.3at required)

alemabrahao · ‎May 24 2023

There is some documentation that will help you. https://documentation.meraki.com/Architectures_and_Best_Practices/Recommended_Topologies/MX_and_MS_Basic_Recommended_Layer_3_Topology https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MS_Switching/General_MS_Best_Practices https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/General_MX_Best_Practices https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/VoIP_on_Cisco_Meraki%3A_F.A.Q._and_Troubleshooting_Tips

alemabrahao · ‎May 24 2023

I believe this will not work unless you have recently changed your password. Are 802.11r and 802.11w enabled on the SSID by any chance? If so, have you tried disabling these features?

alemabrahao · ‎May 24 2023

Why don't you want to use Windows server as DHCP? Anyway, the Ideal is that you keep this in your Network Core, so I don't see any sense in creating SVIs in MS just to enable the resource. DHCP Specify allowed DHCP servers to protect against rogue servers In a warm spare configuration, the load balancing mechanism for DHCP, in some case, may be inefficient and cause an issue where devices may try to get an address from a member with no leases remaining. This is addressed in a stacked configuration, where this issue will not occur.

alemabrahao · ‎May 24 2023

It depends, if you configure it for the same VLAN that already exists in the Catalyst Switch, it is likely that there will be an election of the ROOT STP. Excuse the question, but I believe that the Catalyst Switch is your network core, why do you intend to enable L3 in MS? Remember to check if the STP is properly configured.

alemabrahao · ‎May 24 2023

Enabling Client VPN will not affect your network.

alemabrahao · ‎May 23 2023

Can you share the screen?

alemabrahao · ‎May 23 2023

Have you opened a support case?

alemabrahao · ‎May 23 2023

As far as I know, it's not possible to configure. Maybe you should open a support case.

alemabrahao · ‎May 23 2023

Maybe it will help you. https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance/Managing_and_Troubleshooting_AnyConnect_Certificates

alemabrahao · ‎May 23 2023

I'm not sure about MX, but for MG you can find it on local satus page > configure. Configure Configure section contains options for modifying bearer settings such as APN, PIN, and authentication. The ICCID of the SIM card and IMEI of the of the MG cellular gateway can also be found in this section as well. Safe Mode portion allows you to reconfigure port 1 into a WAN role for troubleshooting. To toggle the port 1 from default operating mode into "safe mode" on the MG, check the box to Enable Safe Mode and save.

alemabrahao · ‎May 22 2023

@KarstenII'm assuming he knows that.

alemabrahao · ‎May 22 2023

I have no experience with Wire guard, but you can Google it. Something like (Wireguard VPN Client to site setup)

alemabrahao · ‎May 22 2023

I suggest you to open support case. It's probably a dashboard issue.

alemabrahao · ‎May 22 2023

As far as I know it will only return the Auto VPN status, for non-Meraki peers it is not possible to return this information.

alemabrahao · ‎May 22 2023

Do you have any firewall in the way that might be blocking the communication? Please provide more details.

alemabrahao · ‎May 22 2023

Yes, you can, I have clients that use pfSense VPN, you will probably need to create a NAT for the server, because I believe that you will not configure a public IP directly on the server, correct ?

alemabrahao · ‎May 22 2023

You can only see it in the details of the clients page.

alemabrahao · ‎May 22 2023

@DPJW Check the documentation. I think that it will help you. https://documentation.meraki.com/MR/Encryption_and_Authentication/Sponsored_Guest

alemabrahao · ‎May 22 2023

Is this new Non-Meraki VPN Peer with Azure too? That wasn't clear. Anyway, you cannot route two Non-Meraki VPN Peers for them to communicate, if you want another non-Meraki peer to reach the Azure devices and vice versa, it is necessary to configure a tunnel directly with Azure.

alemabrahao · ‎May 22 2023

There is a level of functioning of the network this is not a problem. The bigger question is if you have any internal services that you need to publish to the internet (Like a web server). Ideally, each MX would have a public IP, but if that's not possible, that's fine, that's one of the advantages of using SD-WAN, you don't depend on a dedicated link.

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges