Meraki

AjitKumar · ‎Sep 19 2018

Hi, Ideally you should consider MX84 for 160 devices. I believe you may observe slowness / degraded performance on your network while using MX64-68 for such a kind of load. You may refer to MX sizing guide (on Page 4 & 5) for more information https://meraki.cisco.com/lib/pdf/meraki_whitepaper_mx_sizing_guide.pdf Following are the excerpts from the above Sizing Guide. Although there is no hard limit on the number of client devices that can be deployed below MX Security Appliances, for purposes of this document all tests were performed with the client counts shown in the table below. Exceeding these client counts may result in performance that varies from the sizing data contained in this guide. UTM products come with a variety of security and networking features. Understanding the benefits and tradeoffs of these features is crucial to getting the maximum security benefit without unnecessary performance degradation.

AjitKumar · ‎Sep 12 2018

Perfect.

AjitKumar · ‎Sep 12 2018

Hi To verify is it possible for you to Turn Off Non Meraki AP for some time. I am with @PhilipDAth. Ideally we shall not have different make of hardware for wireless on the same floor / area.

AjitKumar · ‎Sep 9 2018

Hi @FelixJacomino Given an opportunity you must not miss the visit Meraki HQ. During my Masters session I was lucky enough to spend a week there. Amazing Environment - Great Culture - Wonderful People. Also If "museum" is the right word. There is a section where in, we have all the products of Meraki in display since inception.

AjitKumar · ‎Sep 4 2018

Congratulations Philip.

AjitKumar · ‎Aug 30 2018

Hi, I need to rectify my answer. @AdamB is correct. Network-wide->client will the display the policy as "Normal". (However I believe even if we apply a Group Policy manually that will overridden by VLAN based Group Policy) I created a LAB to test the scenario. The topology is ISP->MX64->Unmanaged Switch->POE Injector->MR18 On MX64 - Created a VLAN 100 Applied a Group Policy on VLAN 100 On MR - Created a SSID in Bridge Mode Tagging VLAN 100 Network-wide->Clients Displays my laptop in VLAN 100 but policy as "Normal" IP Address is from the desired VLAN 100. Test I Modified the Group Policy on MX. Added the Rule Deny "Social Web and Photo sharing" Result Access to Facebook is Blocked Test II Modified the Group Policy. Removed the Rule Deny "Social Web and Photo sharing" Result Access to Facebook is Allowed So the end result is In my LAB environment the Group Policy on VLAN Works.

AjitKumar · ‎Aug 28 2018

Hi Phill I understand Cisco Meraki have vMX for AWS and Azure as of now. https://meraki.cisco.com/products/appliances/vmx100

AjitKumar · ‎Aug 27 2018

Hi Franck, I understand the physical IP shall remain in MX unless we Reset or Update from the Dashboard. To move a MX we need to remove it from one network then add to another. In the process of removal do we loose the physical IP? That's is a question. https://documentation.meraki.com/zGeneral_Administration/Inventory_and_Devices/Moving_Devices_Between_Networks Excerpts from above Url. MX Security Appliances Since a Security Appliance only contains one MX device (or two identical devices in a warm spare configuration), there is rarely a need to move an MX from one network to another. As such there is no dedicated move tool. To move an MX security appliance between networks, it can be manually removed from one network and added into another. Please refer to our documentation for more information.

AjitKumar · ‎Aug 27 2018

Hi This seems to be strange. Can you verify that the policy is effecting the specified client? (Network-wide->Clients) Also match the physical MAC address of device with the MAC address detected on the dashboard.

AjitKumar · ‎Aug 25 2018

Hi Jay This seems to be challanging. Incase your issue is not solved yet. How about trying following options again? 1 Try to keep the reset button pressed for 30 seconds. 2 Instead of POE switch use a POE injector to power up the AP. Make sure you do not connect LAN into Injector. Incase you still do not see the "Meraki Scanning" SSID. Last resort I shall try is to connect AP to DHCP enabled LAN with OPEN internet. Many times I have used my Laptop along with USB datacard to create this environment enabling internet sharing feature on Windows OS.

AjitKumar · ‎Aug 24 2018

Hi, I am not sure If I could be of great help to you. The Url you posted do not contain the complete specifications of the adapter. The nearest I could locate is https://www.balticnetworks.com/meraki-ac-adapter-for-mr-wireless-access-points-12v-2-5a-us-version.html which seems to be an US version. The specifications are close to the one on the Meraki website. I believe EU version is referring to the same model. So I assume this shall be compatible. I have always been using POE injectors and POE switches to power the APs. Hence shall recommend using them unless there is a special case. Note: I have no experience of using Power adaptors with Meraki APs.

AjitKumar · ‎Aug 24 2018

Hi Erik Are you asking about applying "Group Policy" to a client device automatically when it connects to network? If yes, I can think of few options here. For 1. Wireless Client (MR) One can apply "Group Policy" on the basis of Device Type. Check the following Url. https://documentation.meraki.com/MR/Group_Policies_and_Blacklisting/Applying_Policies_by_Device_Type For 2. Wired Client (MX) One can apply "Group Policy" on the VLAN. Check the following Url. https://documentation.meraki.com/MR/Group_Policies_and_Blacklisting/Creating_and_Applying_Group_Policies#By_VLAN Also I believe one can apply Group Policies on the basis of "Active Directory Group" , "RADIUS Attribute", "Systems Manager Sentry" and "SSID". Hope this help you?

AjitKumar · ‎Aug 23 2018

Hi Jrivano, I do not see a challenge here, we are using 1G SFP's in SFP+ slots for few of our customers.

AjitKumar · ‎Aug 21 2018

Hi Matt I could not see that either on the Local status page / dashboard. I quick idea was to take a packet capture on Internet Port 2. There I got the MAC Address of the Source Interface. Hope this helps.

AjitKumar · ‎Aug 21 2018

*** Happy Birthday Meraki Community*** I am so so so happy to be part of this celebration!!!

AjitKumar · ‎Aug 20 2018

Hi, I am not sure if this is a networking issue. One idea is to "Whitelist" the printer and try to printing. (Network-wide->Clients->[Select the printer]->Click on "Policy" Drop Down->Select Whitelisted)

AjitKumar · ‎Aug 17 2018

Hi I hope you are referring to following features. 1) Flow preferences Security appliance->Traffic Shaping 2) NAT & Port Forwarding Security appliance->Firewall

AjitKumar · ‎Aug 16 2018

Hi, We have 2 options here (that I can think of). 1) You can segregate APs in two groups (Use TAGs to group APs). Assign VLAN as Per the TAGs. https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging_on_MR_Access_Points 2) You may Dynamically assign VLANs to users with the help of Radius server. https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging

AjitKumar · ‎Aug 15 2018

Hi Philip Glad to see the Network diagram. This gives a better clarity. Thank you for sharing. I believe NAT shall be the option to expose any service/application to public. Bandwidth control shall not be the problem as this can be defined in a policy and you may apply the same on the selected device. If you are seriously looking forward to assign a public ip to the device. I understand "No NAT" feature is available with latest firmware. I have not implemented this. I shall request @PhilipDAth to suggest the configuration as per your topology. Lets wait for his comments.

AjitKumar · ‎Aug 14 2018

Hi Philip MX 100 is a Security Appliance (Firewall/UTM). MS 425 is a L3 Switch (Top end offer from Meraki with various Features. Ideally for Distribution). There is no MX425 product I am aware of. 2 x 2960 for core and other 4 x 2960 for Access. This seems fine. Why do we need public ip for core switches? What shall be the role of MS425? Where will you define VLANs? Core Probably. Who will be the gateway? I may have many more such crazy questions. Ideally one should need to define the roles of each device and shall design the network accordingly. Well this is my understanding with the limited knowledge I got. Certainly there are many community members to assist you with there exceptional experience.

AjitKumar · ‎Aug 14 2018

Hi Philip, That shall be easy. You may simply create a "Policy" with the desired parameters and apply the same on device A or Device B. Find the following url for more information https://documentation.meraki.com/MR/Group_Policies_and_Blacklisting/Creating_and_Applying_Group_Policies

AjitKumar · ‎Aug 10 2018

Hi, I hope below checks are made. 1. Ideally the Access Point shall be connected on a Trunk Port. 2. The Native VLAN on the Trunk shall have DHCP enabled and have Internet Access. (Unless you want to configure it manually from the Local Status Page) 3. Firewall If Any, on the Native VLAN shall allow access to Meraki Cloud. You shall also consider the inputs from Philip. 1. Verify the messages on the Local status of the AP. Specially "Ethernet", "Internet" and "Cisco Meraki cloud" sections under Access Point Details. 2. Verify the IP Address allocated to Access Point on your DHCP Server. Is the IP Address Pingable? Is the firewall blocking any kind of access for that IP? 3. Factory reset the device and try again. (Optional)

AjitKumar · ‎Aug 7 2018

Hi, I believe the smaller hardware will have low specifications as they are meant for less load/users. If not MX100 you may consider to upgrade to MX84 that may work out more economical. https://meraki.cisco.com/products/appliances#models

AjitKumar · ‎Jul 31 2018

Hi, "Track by IP" is not currently supported in combined networks. You need to "Split" the combined network under Organization->Overview. You may also refer to following urls for more information https://documentation.meraki.com/zGeneral_Administration/Organizations_and_Networks/Combined_Dashboard_Networks https://documentation.meraki.com/MX-Z/Monitoring_and_Reporting/Client_Tracking_Options

AjitKumar · ‎Jul 30 2018

Hi My understanding is Meraki have 2 Gateway products 1. MX.xx 2. Z.x MX.xx are security appliances meant for Small, Medium and Large Enterprise supporting two WAN Links. Z.x are for Teleworker (Work from Home) kind of environment supporting one WAN Link. Both of the products fully support Auto VPN. One can have combination of them or can have only MX.xx or Z1.x in a network.

About AjitKumar

AjitKumar

Ajit

Community Record

Badges