About AjitKumar

AjitKumar · ‎05-11-2020

Hi @Aamir The scenario is interesting however a little complex though. I do not see a great advantage of placing "MXes" at a distant sites. Ideally you may place "MXes" at the same location and have the second site as a VPN Location. Anyhow. You rightly said "One Armed" concentrators in HA requires, the WAN Interface IPs from the same Subnet / VLAN and reach ability among themselves. I understand different internet connection shall not be a problem. As the fail over detection is via VRRP on the LAN. I hope I am not wrong.

AjitKumar · ‎05-09-2020

Hi @NJacobe Few more ideas. 1. Could you please try updating the firmware? If already not. 2. Could you please try Negotiating the the WAN Interface speed Manually by logging into the Local Status page? ( I think we have the option to configure this. Not sure though) 3. Hope the Transceivers are from Meraki?

AjitKumar · ‎04-27-2020

Hi @BP17 Appreciate your findings. I believe Meraki Team will note this and fix the bug if any. There were few bugs reported in 14.50 by some of the user before too. https://community.meraki.com/t5/Security-SD-WAN/MX-14-50-problem-communication-between-wireless-and-wired/td-p/74184

AjitKumar · ‎04-10-2020

Hi @Sleiman I understand we need more information about your Idea. May be a diagram will help. However, Question 1. We shall be needing 3 IPs from the same subnet for HA (2 for Physical Devices 1 Virtual IP Acting as the SPOC) Question 2. Fail-over is Automatic. We need not do any configuration to achieve this. If you prefer, you may read the following blog to understand a little more on connectivity to achieve HA on Meraki MX https://www.ciscomerakiindia.com/post/mx-warm-spare-ha-pair

AjitKumar · ‎04-08-2020

Hi @Visakh_v_r I would prefer "Single" VLAN across floors.

AjitKumar · ‎04-08-2020

Hi @Absolute-an I understand this should work smoothly.

AjitKumar · ‎03-05-2020

Hi @Qing I understand "Splash Page Frequency" settings might help you here. Kindly check the following thread for more information. https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Splash_Page_Frequency

AjitKumar · ‎03-05-2020

Hi @Garret_Cook There seems to be some challenge for "MG21" in reaching Meraki Dashboard. Kindly check the following Url for complete information https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Upstream_Firewall_Rules_for_Cloud_Connectivity#Devices_Using_the_%27backup_Cloud_connection%27 Excerpts from the above thread: Devices Using the 'backup Cloud connection' While devices will primarily connect to Dashboard using UDP port 7351 for their tunnel, they will attempt to use HTTP/HTTPS if unable to connect over port 7351. When devices are operating like this, a message will be displayed on the device's status page indicating that the 'Connection to the Cisco Meraki Cloud is using the backup Cloud connection.' If this is observed, please ensure that port 7351 is being allowed outbound through the firewall or security appliance traffic from the Cisco Meraki devices will pass through.

AjitKumar · ‎03-05-2020

Hi @BFrança There seems to be some mistake. As for as I understand there is no method / means / configuration that can be uploaded to Meraki Dashboard and will automate the settings for us. The only methods I am aware of is Manual / via APIs.

AjitKumar · ‎02-20-2020

Hi @munaf I shall suggest go for "Advanced Security License". You may have look at the following Url (To know the difference between both the License Types) https://www.syndicateinfo.com/post/what-is-the-difference-between-the-enterprise-and-advanced-security-licenses-for-mx

AjitKumar · ‎02-19-2020

Hi @jhonrojas ¿Podría verificar si su red puede alcanzar los servidores DNS 8.8.8.8 / 4.4.2.2? Intente también actualizar los detalles de DNS del dispositivo con "Google DNS".

AjitKumar · ‎02-19-2020

Hi @MeganMartin There are many tutorial on this. You may google. One of them is could be the below given https://www.youtube.com/watch?v=dpmlFCpussA Note: Your query is not pertaining to the subject of this "Community" .

AjitKumar · ‎02-18-2020

Hi @renanmonteiro In my configuration "Core" Management IP is part of the "Transport" VLAN i.e /29. For other elements "Yes" I too have Management VLAN on the core. I understand this configuration "Works" unless Community Members suggests any other better Method.

AjitKumar · ‎02-18-2020

Hi @SamanthaLu Welcome to the Community. Certainly Meraki is an "Awesome" solution. Let us know if we can offer you any "Guidance". Have a great day ahead.

AjitKumar · ‎02-06-2020

Hi @route_map I understand this will hard to give an estimate on coverage. The Meraki documentation talks about 100 meter in general. Hope you have referred the following documents. https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Access_point_range_and_signal_strength_maximization https://documentation.meraki.com/MR/Other_Topics/MR_Access_Point_FAQ

AjitKumar · ‎02-06-2020

Hi @Patrick777 I understand "No". They are seems to be dedicated for Internet Links.

AjitKumar · ‎02-06-2020

Hi @Aamir I believe the understanding is We can have a FULL Tunnel / SPLIT Tunnel. [We may send All / only the Remote Subnet Traffic via the Tunnel] Tunneling There are two tunneling modes available for MX-Z appliances configured as a Spoke: Split tunnel (no default route): Send only site-to-site traffic, meaning that if a subnet is at a remote site, the traffic destined for that subnet is sent over the VPN. However, if traffic is destined for a network that is not in the VPN mesh (for example, traffic going to a public web service such as www.google.com), the traffic is not sent over the VPN. Instead this traffic is routed using another available route, most commonly being sent directly to the Internet from the local MX device. Split tunneling allows for the configuration of multiple hubs. Full tunnel (default route): The configured Exit hub(s) advertise a default route over Auto VPN to the spoke MX. Traffic destined for subnets that are not reachable through other routes will be sent over VPN to the Exit hub(s). Exit hubs' default routes will be prioritized in descending order.

AjitKumar · ‎02-06-2020

Hi @renanmonteiro I understand "Dashboard" will take care of this challenge with Zero downtime. Could you please refer the following Url (If already not) https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware#Best_Practice_for_MX_Firmware

AjitKumar · ‎02-06-2020

Hi @renanmonteiro Entendo que o "Painel" resolverá esse desafio com o tempo de inatividade Zero. Você poderia consultar o seguinte URL (se já não estiver) https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware#Best_Practice_for_MX_Firmware

AjitKumar · ‎02-06-2020

Hi @guzgerardo Is it possible for you to connect a PC directly to MX and Test?

AjitKumar · ‎02-06-2020

Hi @cgibson777 "switch taking care of the Vlan routing/tagging and the firewall just doing internet traffic is perfect, I just can't seem to get it right." If I understand you right. The requirement is 1. All the VLANs shall reside on the switch 2. MX shall be the gateway for internet access Possible configuration could be On MX 1. Create a Transit VLAN Security & SD-WAN > Addressing & VLANs > Routing 2. Create reverse route for VLANS on the switch Security & SD-WAN > Addressing & VLANs > Static routes On Switch 1. Create a Transit VLAN Switch > Routing & DHCP 2. Create Default Route towards MX Switch > Routing & DHCP

AjitKumar · ‎02-06-2020

Hi @guzgerardo I understand if AD Integration is successful with Dashboard. We can MAP the AD Groups with Respective Meraki Group Policy and this shall work. Kindly refer the following image for more information.

AjitKumar · ‎02-06-2020

Hi @petermlamont My understanding is Internet will terminate on WAN1 and SIP MPLS will terminate on LAN Port (You will create a VLAN on MX).

AjitKumar · ‎02-05-2020

Hi @petermlamont Certainly MX68 can accommodate 2 external WAN links simultaneously. Yep, The links can work as fail over / load balancing. Also we can define rules to send traffic of specific source (IP Address) to exit via a select Link (WAN1 / WAN2). Is this the answer to your question? I am not sure.

AjitKumar · ‎02-05-2020

Hi @Slider I understand MDM Sentry Policies Feature may help here. https://documentation.meraki.com/SM/Other_Topics/Configuring_Sentry_Policies

AjitKumar

Community Record

Badges