About AjitKumar

AjitKumar

Hi @MMoss For us, this works. Could you please try updating the firmware - if already not?

AjitKumar

Hi @gumuxisi I believe this should be fine. We have the following available interfaces on MX67C: WAN: 1 × 1 GbE LAN: 4 × 1 GbE (1 optionally available for WAN connectivity) 1 x CAT 6 LTE Cellular Modem USB: 1 × USB 2.0 for 3G/4G failover (supported devices) Check the following thread for more details https://documentation.meraki.com/MX/Cellular/3G%2F%2F4G_Cellular_Failover_with_USB_Modems However looks like Aircard is modems are compatible on MX and/or Z-Series appliances, but are no longer available for sale from their respective carriers or manufacturers.

AjitKumar

Hi @sankar This can be be achieved with the help of APIs. However we need to have good programming skills.

AjitKumar

Hi @Xavier_o , Looks like this should be possible with the configuration of Traffic Shaping. Security & SD-WAN->SD-WAN & Traffic Shaping -> SD-WAN policies-> VPN traffic -> Add a preference

AjitKumar · ‎12-03-2020

Hi @NishikaKamat As both the SSIDs are in bridge mode. Is there anything in between the network blocking the contents (Firewall / Proxy)? Are the APs management IPs whitelisted (Unrestricted) as Guest SSID can access every content? How is the network connectivity? Data Flow?

AjitKumar · ‎12-03-2020

Hola @WERC_COLOMBIA La comunicación con las IP de Meraki Cloud es confiable. No vemos una amenaza aquí. Para el invitado, puede elegir el contenido / categorías en Seguridad y SD WAN según sus necesidades comerciales.

AjitKumar · ‎12-03-2020

Hola @WERC_COLOMBIA Supongo que la única solución podría ser crear una política separada para los AP. Permitir el acceso a la subred de AP para acceder a cualquier destino. Esto permitirá el acceso COMPLETO a Internet, incluida la comunicación a la nube.

AjitKumar · ‎12-02-2020

Hi @Kasking I believe this option will appear only if we have a Meraki L3 Switch in our network. How is the output when you select "only switch clients" under Network-Wide > Clients.

AjitKumar · ‎12-02-2020

Hi Jim, This looks like more or less Plug and Play. I believe you are moving the devices physically. This means we need no changes on the Dashboard. We simply need to make sure the MX64W is live (connected to Direct Internet - with no Firewall) at your new branch office. You may follow this thread on - How to configure the IP Address. https://documentation.meraki.com/MX/Other_Topics/Static_IP_Assignment Rest of the configuration is already there in the cloud - Your Branch Office should be live.

AjitKumar · ‎11-13-2020

Hi @Andy66 I am not sure if would like the solution but seems like disabling Javascript is the only way as of now. https://support.google.com/websearch/thread/4928129?hl=en https://support.google.com/websearch/thread/28301966?hl=en Native Features on the Firewall may not help. May be Cisco Umbrella can be some rescue here - We need to explore this.

AjitKumar · ‎11-13-2020

Hi @imovaffagh This is my understanding. 1. In one Organization all the firewall (MXes) should have of one license type. [Enterprise / Adv / SDWAN] 2. We need to have separate set of license for every Organization. 3. We can always have Site-to-Site VPN between two Organizations - but this will be a 3rd Party VPN configuration. AutoVPN will not be possible. I also understand we need public Static IPs at both the ends for this configuration.

AjitKumar · ‎11-01-2020

Hi @Boyan1 I understand the upgrade will impact the complete network and devices. One idea could be to create a new network and apply the licenses and Invite your selected devices to this network.

AjitKumar · ‎10-29-2020

Hi @Thygesen Just to confirm if this is firmware issue - Is it possible for you to roll-back and observe the network - (If you have already not done this?)

AjitKumar · ‎10-29-2020

Hi @thirty2 I can think of 2 ideas. 1. You may expose the server on Internet on port 514. There after integrate the dashboard as per the syslog configuration (NOT RECOMMENDED) 2. You may establish VPN between your office and AWS. There after integrate the dashboard as per the syslog configuration Having said in all my deployment I have used onsite servers - which are locally present - I do not see a great advantage on uploading all the traffic on AWS. (This is my personal opinion)

AjitKumar · ‎10-29-2020

AjitKumar · ‎10-26-2020

Hi @Brill MX 84 is a solid BOX. However for Mining Area - I guess we shall look towards Industrial Wireless Units. https://www.cisco.com/c/en/us/products/wireless/outdoor-wireless/index.html I am not sure how suitable Meraki could be for such an environment? I have not deployed - May be we shall seek feedback from a member who has already installed Meraki in such conditions.

AjitKumar · ‎10-23-2020

Hi @SchoolITMan As everyone is suggesting "interference" could be the primary reason. Also seems like we have a new Firmware release - MR 27.5.1. You may give it a shot - if already not upgraded. https://community.meraki.com/t5/Wireless-LAN/New-MR-27-5-1-firmware/m-p/101264

AjitKumar · ‎10-23-2020

Hi @johnnyngena What are your thoughts on "syslog" service. https://documentation.meraki.com/zGeneral_Administration/Monitoring_and_Reporting/Syslog_Server_Overview_and_Configuration

AjitKumar · ‎10-22-2020

Hola @CCL_CO Si te entiendo correctamente. Esto no debería ser un desafío. 1. Su punto de acceso debe estar conectado a un puerto troncal. 2. Se permitirá la "VLAN" deseada en el puerto troncal. 3. Etiquete el SSID con la "VLAN" deseada. Eche un vistazo a la captura de pantalla como referencia.

AjitKumar · ‎10-22-2020

Hi @Thomas2 A few Ideas here. 1. How about try connecting another Laptop? 2. How about connecting the Laptop on other Port 4 / 5?

AjitKumar · ‎09-22-2020

Hi Friends, Is the following configuration possible on MX100 (IPSec) The Customer is going to connect to their client's network (The client's network might have ASA / Fortigate). Question 1 From Branch-1 to Client-1 Site-to-Site VPN (IKEv1) on Primary ISP From Branch-1 to Client-1 Site-to-Site VPN (IKEv1) on Secondary ISP From Branch-1 to Client-2 Site-to-Site VPN (IKEv1) on Primary ISP From Branch-1 to Client-2 Site-to-Site VPN (IKEv1) on Secondary ISP From Branch-1 to Client-3 Site-to-Site VPN (IKEv2) on Primary ISP From Branch-1 to Client-3 Site-to-Site VPN (IKEv2) on Secondary ISP From Branch-1 to Client-4 Site-to-Site VPN (IKEv2) on Primary ISP From Branch-1 to Client-4 Site-to-Site VPN (IKEv2) on Secondary ISP Question 2 Also please confirm NAT (Network Address Translation) is possible over Site-to-Site VPN Phase2 as interesting traffic? Question 3 SSL based remote access VPN is possible? If yes, please confirm the SSL VPN traffic can be rerouted to existing Site-to-Site VPN of Branch-1 clients Example: End User-1 connect branch-1 SSL VPN and access Client-1 Site-to-Site VPN (IKEv1) End User-2 connect branch-1 SSL VPN and access Client-3 Site-to-Site VPN (IKEv2) Regards Ajit

AjitKumar · ‎09-13-2020

Hi @LeonJVR Welcome to the community. You may post your queries right here. Regarding VPN configuration I believe it will work the way you are expecting. (I have never configured though) Hope you have read the following thread. https://documentation.meraki.com/SM/Profiles_and_Settings/Systems_Manager_VPN_Configurations_and_Sentry_VPN

AjitKumar · ‎09-01-2020

Hi Vishal, I do not see any change in the way users have been accessing the internal server. The sessions created to access internal servers will go via the same path .i.e WAN1 with the available bandwidth of 50 Mbps.

AjitKumar · ‎08-27-2020

Hi Asif I believe this will be difficult. I shall recommend reaching support right away.

AjitKumar · ‎08-26-2020

Welcome, Kovac. Meraki is a great solution and for sure you will enjoy working on it.

AjitKumar

Community Record

Badges