Meraki

Mloraditch · ‎Nov 16 2023

https://documentation.meraki.com/MR/MR_Installation_Guides/CW9163E-MR_Installation_Guide The marketing pages haven't posted yet on cisco.com or meraki.cisco.com (it's dual identity) but it's available to order. A number of caveats with regards to 6Ghz actually running because of regulatory stuff, Details in the doc. Regardless, if you are working on outdoor coverage you can at least be a little bit more forward ready now and have the hardware.

Mloraditch · ‎Nov 16 2023

Important notes HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect. While Meraki switches have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MS 15.1+ we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the Help > Firewall Info page is allowed through any firewalls or security filtering devices that may be deployed upstream of your Meraki switches. These requirements have been updated on Nov 2022, so it’s important that you review them. MS 15.23 is the same as MS 15.22 for all models except the MS130 switch models New feature highlights IPv6 management interface support Ms130 fixed issues Cable length is reported as double the actual length during cable tests in some scenarios (always present) Cable tests may fail on non-mGig ports (always present) If a device is rebooted in quick succession, ports may fail to initialize correctly resulting in packet loss (always present) Devices may be provided incorrect firmware download URLs resulting in firmware images failing to be downloaded and devices remaining on the prior release General known issues Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12) Non-MS390 switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 unless the bundles are configured on the MS390 first. All Non-MS390 ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present) In rare instances, the port status will fail to update to dashboard until the system reboots (present since MS 14) Ms120 known issues Switches in extremely rare instances upon reboot will experience persistent reboots every few minutes, failed firmware upgrade, or fail to reconnect with dashboard (present since MS 11) Switches may fail to provide PoE power to legacy access points (always present) Ms125 known issues The local status page cannot be accessed from the management port (always present) Ms12x known issues Ports with an odd-numbered MTU value fail to initialize (predates MS 11) Switches will never move a RADIUS server's connectivity status to available if it was ever lost resulting in all authentications being placed into the critical auth VLAN (present since MS 14.32) Ms2xx/35x/4xx known issues Cross-stack LACP bundles experiencing a switch reboot will cause the remaining online port to experience an outage of up to 30 seconds. The same is seen again when the switch comes back online (present since MS 10) IPv6 multicast packets tagged for a VLAN may not be filtered correctly resulting in packets egressing into other VLANs (present since MS 14) IPv6 solicited-node packets bypass port isolation (present since MS 14) Rebooting a stack member may result in internal stacking packets being sent out into the LAN (present since MS 15) SVI default route can be incorrectly removed from the routing table after L3 changes are made on dashboard. Removing and re-adding the route is required to resync the stack (present since MS 15) Stack routing tables can get out of sync when L3 changes are made. Making an additional change to L3 can resolve the sync issue (present since MS 15) Switch stacks will learn MAC addresses from ports in the STP blocking state which can trigger a constant flood of MAC flaps in the event log Ms355 known issues In rare instances, stack ports fail to initialize after an upgrade (always present) Ms35x known issues Enabling Combined Power results in events being logged once per minute (present since MS 11) UPoE does not negotiate over LLDP correctly (always present) mGig switches will have an amber light for all physical ports that do not negotiate to the highest supported speed. Dashboard will continue showing a light green status for all ports above 100Mbps. For example, MS355 switch ports will incorrectly show an amber light for 1G, 2.5G, and 5G, but will show a green light for 10G. Ms425 known issues Large number of SNMP walks to switches in H.A. may destabilize the VRRP connection resulting in flapping (present since MS 15) Stacks in rare instances will start dropping DHCP traffic on trusted ports while DAI is enabled until rebooted (present since MS 12) Ms4xx known issues When an SFP module is inserted/removed, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)

Mloraditch · ‎Oct 27 2023

I don't know how far back it goes, but they did update at least some older versions and included this note: This list of issues has been provided as part of a one-time update. The list is current as of October 23, 2023 and is no longer being updated with new information. Please see the latest available patch release for new, active updates.

Mloraditch · ‎Oct 19 2023

Can anyone from Meraki comment on this?

Mloraditch · ‎Oct 17 2023

They always seem to release these things with GUI not quite ready yet. I wish they'd be more consistent with noting GUI comes later (which they've occasionally done), syncing the release with the GUI release, or just not even mentioning until the GUI is available.

Mloraditch · ‎Oct 16 2023

Just for the benefit of someone in the future looking at this thread, no matter how you shake it, this is a license change. This is when I suggest talking to your reseller and engaging with your Meraki rep. They have the ability to help ease the pricing pain of the upgrade. No guarantees, but always worth asking. As an individual home user not sure you have much leverage, but a regular business looking at this should definitely ask.

Mloraditch · ‎Oct 13 2023

YES. My primary coworker and I both noticed this earlier this week. I opened a case and per the support rep their documentation says it's supposed to take the idle timer of the shortest org you have access to. He said that's the way it's always been. It was implied that perhaps a backend change had enabled what was always supposed to be the behavior. He did comb through all of my orgs and found a couple that I was able to change, but I have one I'm not in charge of that is my main limiter. If anyone from Meraki is watching here's my case number: 10942842.

Mloraditch · ‎Oct 11 2023

Would be nice if they updated the note to be clear about that. I and others suspected as much for quite a while, maybe even document what changes make it happen

Mloraditch · ‎Oct 5 2023

Very few people know these plans ahead of time and no one official is going to give you anything on a public forum. Talk to your Meraki Rep they may be able to get you information under NDA. There are also significant discounts on APs right now through at least the end of January that can probably make the Wifi 6Es a no brainer.

Mloraditch · ‎Sep 30 2023

If you are using a non meraki bridge, I would think this would work. Most vendors I've dealt with operate as a layer 2 connection so the switches would consider it like any other set of two cables not in in a LAG.

Mloraditch · ‎Sep 30 2023

The Roaming/Teleworker bug is not listed in the fixes, but is no longer a known issue? Curious if it's actually fixed given how long it's been around. Important note While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the "Help" > "Firewall Info" page is allowed through any firewalls or security devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) Legacy product notice When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 Bug fixes General stability and performance improvements Known issues In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled

Mloraditch · ‎Sep 26 2023

Unofficially, based on my review of the pricing and specs, the MS130 will replace the MS120. MS130 gig only all appear to be cheaper than the same capacity MS120s at List and essentially the same switching specs with slightly better power consumption. Of course your price is determined by your Cisco Account Team and Partner. The MS125s are harder to evaluate as 10Gb uplinks are only in the X models. I would suspect the 125s will live on longer. However, officially, I haven't seen any answers to this. I would expect a blog post or some other announcement later today with perhaps a few more surprises. It's still somewhat early at Meraki HQ.

Mloraditch · ‎Sep 5 2023

Yes, that's it. It was defaulted to 5Ghz on this non greenfield setup.

Mloraditch · ‎Sep 5 2023

CW916X FAQs The above link has the following: "the third radio of the CW9166 also has the advantage of being able to be configured either as a 6 GHz or 5 GHz radio" Is that automatic when 6ghz isn't enabled, not supported in Meraki mode, or do I need to do something? I can't find further mention of it.

Mloraditch · ‎Aug 31 2023

Alerts This version's IOS image is based on 17.9.3 CCO. Upgrades to this version will result in a full system reload New features 802.1X Control Direction Adaptive Policy ACL hit counter live tool MAC Allow list on access ports Named VLAN Bug fixes CDP fails to populate all port module data (always present) In rare instances, large configurations would fail to apply LLDP information for the IPv4 management VLAN is incorrect (present since CS 16) MAB authentication may intermittently fail on stacks Storm control configurations can fail to be updated on LACP groups after changes are made (present since CS 16) Traffic analytics is missing categorizing some applications (always present) General known issues DHCP options longer than 180 characters may fail to be configured on the device resulting in the configuration being reverted (always present) DHCP server information is incorrectly reported, such as the subnet mask and "Last Seen" fields (always present) Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present) Large changes made via the API for a single device may take 10+ minutes to apply

Mloraditch · ‎Aug 9 2023

It's not appearing available to install yet, but I discovered the release notes paging through firmware versions. Important note While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the "Help" > "Firewall Info" page is allowed through any firewalls or security devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) Legacy product notice When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 Bug fixes General stability and performance improvements Various improvements in DFS behavior for outdoor APs APs may stop forwarding RTP traffic (Wi-Fi 6 APs) Security fixes Qualcomm wireless chipset vulnerabilities CVE-2022-33277, CVE-2022-40512, CVE-2022-33243 - https://docs.qualcomm.com/product/publicresources/securitybulletin/february-2023-bulletin.html (Wi-Fi 6 and Wi-Fi 6E APs) FTM RTT measurement turned on by default (Wi-Fi 6 and Wi-Fi 6E APs) Known issues Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled

Mloraditch · ‎Jul 30 2023

Here's to hoping they copy you here as well!

Mloraditch · ‎Jul 26 2023

Bug fixes Resolved an MX 17.10.4 regression that could result in the WAN 2 port being set as disabled when making changes via the device local status page. Corrected an issue that could result in an unexpected device reboot when FIPS mode was enabled. Fixed an issue that resulted in MX95 and MX105 appliances incorrectly forwarding CDP traffic. Resolved an issue that resulted in MX appliances generating syslog flow messages for internal traffic processing steps. Corrected a rare issue that could result in IBGP instability when two AutoVPN peers established their IBGP session using IPv6. Fixed an issue that could result in AutoVPN IPv6 routes not being preferred over non-Meraki VPN peer IPv6 routes. Resolved a rare issue that could result in device reboots for MX67(C,W) and MX68(W,CW) appliances. Corrected an issue that could result in configuration changes to the Layer 3 firewall rules not taking effect when the MX was configured in passthrough mode and only AnyConnect client VPN was configured. Fixed an issue that resulted in clients not receiving DHCP IP addresses if 1) clients were connected to Z4 appliances, 2) the Z4 was originally configured in NAT mode, 3) the client received an IP address from the Z4 while it was in NAT mode, and 4) the Z4 was reconfigured to operate in passthrough mode. Resolved an issue that resulted in the LED activity lights for LAN ports not functioning correctly on Z3(C) appliances. Corrected an issue that could result in IPv6 traffic received over VPN not being correctly routed to destinations reachable through other types of VPN. For example, AnyConnect client VPN to non-Meraki site-to-site VPN peers. Fixed an issue that could result in the default AnyConnect group policy not being applied consistently, depending on the username’s case/capitalization. Resolved an issue that resulted in routes learned via IBGP being reported as “external” routes on the Route table page in Dashboard. Resolved an issue that could result in traffic being incorrectly dropped when being routed across an IPv6 route learned via EBGP. Legacy products notice When configured for this version, Z1 and MX80 devices will run MX 14.56. When configured for this version, MX400 and MX600 devices will run MX 16.16.9. Known issues After making some configuration changes on MX84 appliances, a brief period of packet loss may occur. This will affect all MX84 appliances on all MX firmware versions Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page MX appliances will now properly validate that DBD packets conform to the appropriate MTU size. If the MX's OSPF peer has an improper MTU configured, it may cause the OSPF adjacency to fail to properly form. The updated behavior properly conforms to RFC. Please ensure these settings are properly configured on any MX's OSPF peers to avoid disruption after upgrading to MX 18.1.X. Other Updated APN mappings for the Orange and EE carriers. Content filtering URL lookups to the Talos backend will no longer follow routes configured for client traffic. These lookups should now always egress a WAN interface. Improved support for reporting when 2.5Gbps and 5Gbps link speeds were in use. Added support for automatic detection of AIF Telecom cellular connections using the “datapro” APN.

Mloraditch · ‎Jul 25 2023

Apparently this is not possible, you have to manually claim by serial? Is there a timeline on fixing this? Support just said it's being worked on.

Mloraditch · ‎Jul 7 2023

There is a dashboard issue https://status.meraki.net/ while the alert says only logins, I'm seeing similar issues as you plus config changes seem to take, but can't claim orders/licenses or add new devices to networks, etc.

Mloraditch · ‎Jun 26 2023

Got it. Thanks!

Mloraditch · ‎Jun 23 2023

Definitely didn't know this so thanks! One question, how do the clients know to update? I created a vpn profile and downloaded it and it doesn't feature any parameters that would tell the client. Is the installer provided somehow customized to check in with the securex cloud for update settings?

Mloraditch · ‎Jun 12 2023

Interesting new detail on the backend IOS version Alerts This version's IOS image is based on 17.9.3 CCO. Upgrades to this version will result in a full system reload. New features 802.1X Control Direction Adaptive Policy ACL hit counter live tool MAC Allow list on access ports Named VLAN Bug fixes A stack may fully reboot if a stack member crashes (present since CS 15) Cloning a stack member results in configurations for LACP to be missing, requiring the bundles to be reconfigured or the system to be rebooted (present since MS 15.14) IPv6 information is incorrectly presented in CDP/LLDP packets (always present) Modifying storm control can result in the configuration lines not being removed (present since MS 15) Portchannel is going down upon attaching adaptive policy configs and not coming back up after removing adaptive policy configs as well. Ports that are in LACP suspended show as offline instead of errored in dashboard (present since MS 14) RADIUS message NAS IP address is incorrectly 1.1.3.1 (present since CS 15) General known issues "Port Up/Down" events will generate an event log for each stack member DHCP options longer than 180 characters may fail to be configured on the device resulting in the configuration being reverted (always present) DHCP server information is incorrectly reported, such as the subnet mask and "Last Seen" fields (always present) Non-MS390 switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 unless the bundles are configured on the MS390 first. All Non-MS390 ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present) Rebooting a switch in a stack via the UI will result in the entire stack rebooting (always present) Receiving incorrectly flooded CDP packets may incorrectly report VLAN mismatches and SFP port information (present since MS 12)

Mloraditch · ‎Jun 7 2023

Quick Start Guide Getting Started FAQ tl;dr - Migration is built into latest versions of IOS-XE vs the process that previously existed and there is a dedicated team to help plan/validate that your system will work Still no public ETAs on other C9X00 models.

Mloraditch · ‎Jun 6 2023

This was just announced at Cisco Live. The details aren't fully online yet but it should be in public beta for SD-WAN Plus customers very soon. Announcement Blog I've pulled together some of the Cisco Live Presentations: The Journey to Hosting Containers on Meraki with ThousandEyes - BRKAPP-2727 - Really Cool Info on internals Making Meraki SD-WAN "ThousandEyes" Aware - PSOAPP-1618 Learn How Meraki and ThousandEyes Together Are Solving Your Application Performance Issues With Simplicity - BRKMER-2007 (The actual preso is not posted yet but URL should work by Thursday morning) I've seen some demos and it's pretty cool.

About Mloraditch

Mloraditch

Matthew Loraditch

Community Record

Badges