Meraki

SoCalRacer · ‎May 31 2019

I don't have any but I am pretty sure it won't because there is a device type for Xbox and it isn't listed in the groups to filter. Meraki uses LLDP to identify devices some its not always correct. The way I would check would be just change the Group Policy for Windows devices to a blank group policy that does nothing except defaults. Then go track the Xbox device down in the dashboard, check the device type it is listed as and what group policy is applied to it. If none then I would say you are safe to change the blocked policy on Windows device types.

SoCalRacer · ‎May 30 2019

A única maneira que eu acredito é via RMA. O MR16 está à venda há quase 5 anos. https://meraki.cisco.com/lib/pdf/eol/meraki_eol_mr16.pdf

SoCalRacer · ‎May 30 2019

I believe the below applies to the vMX also. https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX I am assuming the VM is on the LAN behind the vMX? Are you able to ping from the vMX to the VM you are trying to port forward to? If not you probably need to look at the NSG rules on the VM.

SoCalRacer · ‎May 28 2019

I found a doc with some info on Jive that might be of use. https://jive.com/resources/support_page/onboarding/network-readiness-2/quality-service-qos/ Now I don't have clients with Jive, but I do have clients with RingCentral on Meraki and using wireless and also using YeaLink phones. Attached is the a working config we have used with RC and Meraki.

SoCalRacer · ‎May 28 2019

OFDMA is exciting and the performance capabilities with increased devices on the network looks to be very appealing. Also excited to see the help on device's battery performance with TWT (Target Wake Time).

SoCalRacer · ‎May 23 2019

@PhilipDAth Nice job! I didn't get mine submitted, but we had very similar topology. Kind of interested why you left 8 MR55 at the branch office with 50 users. I had relocated the webserver to HQ along with the MR55 to be connected to the mGig switches and replaced the 8 at Branch 1 with 10 MR42. Also interested in the unused MX84, couldn't it be swapped with the MX67W and then have the MX67W be a cold spare. Then move some MR18 over there for better wireless coverage/bandwidth?

SoCalRacer · ‎May 23 2019

Very interested to see what the deal is with this. I have this on my list to convert scripts/webhooks.

SoCalRacer · ‎May 23 2019

In my experience with Dynamic Public IP from the ISP they don't change all the often. Usually only on a reboot and even then not always does the IP change. Is your provider changing the IP regularly? Is static not an option?

SoCalRacer · ‎May 22 2019

As far as my experience you can create a VPN to MX devices across different organizations and use a Dynamic IP, you will just have to update it when the VPN goes down, which you could setup alerts on and even update via a script.

SoCalRacer · ‎May 22 2019

@drgnslyr Looks like 4 more classes came available this morning!

SoCalRacer · ‎May 22 2019

If you can filter then by say OS in the dashboard you can select them and mass apply the group policy. How many clients are we talking about?

SoCalRacer · ‎May 22 2019

Sounds like a good time to give some swag away 🙂

SoCalRacer · ‎May 21 2019

https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/Z3_and_Z3C_Overview_and_Specifications Just something to note EE is not a tested carrier with the Z3C. I am pretty sure many people have been able to get it to work, but just noting it may not work out of the box.

SoCalRacer · ‎May 21 2019

Looks like I was able to get registered for next weeks class. Registration must open by 9:00AM PST

SoCalRacer · ‎May 21 2019

1) Confirm is that it is a WW (Worldwide) model and not the NA (North American) model. 2) The device has been plugged into a WAN and is on the most up to date firmware

SoCalRacer · ‎May 21 2019

@kYutobi @MeredithW @CarolineS Can any of you confirm what time ECMS1 registration opens today?

SoCalRacer · ‎May 21 2019

Update Client Name using API You might check and see if that helps.

SoCalRacer · ‎May 21 2019

@drgnslyr Any luck this morning for you? I went in just a couple mins ago and sessions are full.

SoCalRacer · ‎May 20 2019

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware Appliance Network with Two MXs in an HA Configuration When MX appliances configured to operate in High Availability (HA) (either in NAT/routed mode or when operating as one-armed VPN concentrators), the dashboard will automatically take steps to minimize downtime when upgrades are performed to ensure a zero-downtime MX upgrade. This is achieved through the following automated process: The Primary MX downloads firmware The Primary MX stops advertising VRRP The Secondary MX becomes master The Primary MX reboots The Primary MX comes online again The Primary MX starts advertising VRRP again The Primary MX becomes Master Again The Secondary MX downloads firmware (approximately 15 minutes after the original upgrade is scheduled) The Secondary MX stops advertising VRRP The Secondary MX reboots and comes back online

SoCalRacer · ‎May 20 2019

Scheduling Firmware Upgrades Keeping up-to-date on firmware allows administrators to utilize the latest features and ensures that the latest security enhancements are running on their hardware. Admins can upgrade to the latest stable or latest beta firmware. Follow the steps below to schedule a firmware upgrade. Navigate to Organization > Monitor > Firmware upgrades. Click the All networks tab in the upper-left. Select the devices or networks to be upgraded by clicking the checkboxes beside the network names. Admins can specify upgrades on a per-network or per-device type basis by using the Device type, Current version, and/or Firmware status dropdown selectors. Click the Schedule upgrades button. Select the firmware version that should be upgraded to using the Target firmware version selector. Select either Perform the upgrade now or Schedule the upgrade for, specifying a specific date and time for the upgrade. Review the Change Summary and select Schedule change for network. Note: When downgrading from a beta firmware to a stable firmware, a feedback request page will be presented. Please select any options that reflect the downgrade reason before selecting Schedule change for network.

SoCalRacer · ‎May 20 2019

@BrechtSchamp Actually an MX isn't required a Z3 does PPPoE. @Ciscoguy7 Also another product to consider to swap with the MR33 would be a Meraki Go GR10 Access Point, not sure that it does PPPoE, but it might be more suited for a small cafe. Also about 80% cheaper.

SoCalRacer · ‎May 15 2019

https://documentation.meraki.com/SM/Monitoring_and_Reporting/Managing_Systems_Manager_Location_Services_for_iOS According to that I don't believe so, but I believe you can set a policy that if there is no check in it loses connection or disables connection.

SoCalRacer · ‎May 15 2019

It almost sounds like you have the North American model and not the Worldwide model. Another thing to test would be a usb modem with that sim plugged into the MX67C

SoCalRacer · ‎May 14 2019

To summarize: You have some MX67C working and some not working with the same provider SIMs You know you have LTE coverage where the MX is You don't have this issue with any MX68CW Questions: Are these recently deployed? Have you checked the config log to see if anything stands out or is different from the working ones? Is a factory reset an option on a test 67C?

SoCalRacer · ‎May 14 2019

Have you verified cellular coverage in the physical are the MX is located in?

About SoCalRacer

SoCalRacer

Community Record

Badges