Yes.  Latest stable on wifi, the button and MV22.  Switches are just one behind. ... View more

Thank you sir, will give those a try   ... View more

@CharlieCrackle is accurate.  Even says it in the announcement...   The list price for MT12 and the accessories have been adjusted appropriately so that there is no additional cost. ... View more

Thanks for the info.  I have it set up now and it's working great with the MV22.   ... View more

Yeah, I had the same problem.  I can get it to save after about 10-20 tries.   ... View more

That would make sense then.  One of the devices I was looking at was an old idrac that had been connected for months but meraki said 0 clients.  Could be that it hadn't reached out to the net at all.  Thanks ... View more

Thanks for the update. We also realize how hard it is to get equipment in customer hands lately. Please let us know! ... View more

@Aaron_Wilson thanks, I saw 4.15 alerting for the last month or so, so have been looking for a 4.16 ever since.  I didn't realise that the stable code was also warning! ... View more

>Does Cisco SecureX require additional licenses?   Not for authentication.  You can just sign up and start using it. ... View more

@Dartanian14 What browser extension?  I currently have to go through the O365 portal to login.  Meraki should enable SAML on their own login page like most other SAML integrated apps I've set up. ... View more

Just found some more info regarding other brands and stacking two switches with one cable.  It sounds like it works fine just isn't recommended for redundancy reasons.   https://networkengineering.stackexchange.com/questions/62651/how-many-stack-cables-would-be-needed-if-we-want-to-stack-two-3850-switches   https://community.extremenetworks.com/extremeswitching-other-233226/how-many-stack-cables-for-two-switches-stack-6755077   https://community.cisco.com/t5/routing/number-of-stack-cables-for-two-3650/td-p/3179794   I'll probably end up using two cables to be on the safe side. ... View more

The one point to remember with ACLs on the MS switches is that they’re applied to all traffic entering the switch, not going between VLANs - hence why there is no default deny all, as that would render the switch inoperative out of the box (it would just deny everything). And they’re stateless too - so just because they allow traffic in one direction, doesn’t mean they’ll let it come back the other way.   As you’ve discovered this actually provides some great flexibility as it means you can actually stop clients from communicating within a VLAN.   It also means that to stop communication between VLANs you could use deny rules that specify the source IP as any, the destination IP as the other VLANs subnet, and apply it to the source VLAN, simple as that. Then you don’t actually need the rules on the firewall to block inter-VLAN traffic as it is blocked as it enters the network.  There are a couple of gotchas to watch out for. The MS390 switches still have limitations on support for switch ACLs, and the MS120/125 switch model also have restrictions. ... View more

I feel like this should be on the known issues.  I read it on the ACL Documentation page "Note: The VLAN qualifier is not supported on the MS390. For the MS390, ACL rules with non-empty VLAN fields will be ignored." ... View more

It would depend on the criticality of what is going on the switches. Currently they are not stable enough for use in situations with servers or large traffic loads for us. They are relegated to being access layer switches for the time being. Frajnly we have been trying to figur eout what th eplan is here with regards to Cisco and these switches. It is pretty clear to me that the switch is running Catalyst IOS XE natively and the Meraki software is running in an IOS XE VM to provide the "Meraki" interface. Basically with the Meraki software VM acting as a "thunking" layer. I have verified this with Meraki support folks who had access to the catalyst stuff going on underneath for debugging purposes for some of our open tickets. Issues we had included problems with Stacking, stack members randomly reordering themselves, stacks requiring reboots for layer 3 SVI changes to take effect, issues with QoS, the 1000 vlan limitation issue, and issues with STP compatibility between catalyst IOS switches and the meraki switches. When doing forklift network upgrades for campuses, we have been having to build entire parallel networks back to the firewall to isolate the STP from the old catalyst STP or you get all kinds of weird stacking problems.   I come from a CCNP background and I have scoffed at our management's attitude that somehow this stuff is the future of networking. We deal with a lot of clients who have high turnover low skill set engineers due to low wages and living in rural areas. (Think government workers.) So they bought the Kool-Aid on this we can avoid fixing our HR problems and paying real salaries by getting this "Anybody off the street can build a GUI network" kit. The actual old Meraki hardware has been relatively trouble free. But having to debug a buggy beta product foisted on the masses with no actual debugging tools becasue they are hidden has been a HUGE time suck. Our early projects were regularly over budget and late due to trying to debug these things. Once you know the tricks like:   1. Isolate the STP instances from any Catalyst STP 2. Upon brining up an MS390, set all ports to access and VLAN 1 to avoid the 1000 vlan problem when connecting to switches that pass all vlans rather than a subset on trunks.  3. After making MS390 L3 changes reboot the stack to make sure things take effect. 4. Bring a magazine and some coffee to pass time while the switches are booting up. Bring a book if you are doing things that require multiple reboots like firmware updates.   My speculation having worked for government and large outfits is a very large company was working with cisco on a very large business deal. This deal probably stipulated port requirements, power requirements, feature requirements, or redundancy requirements that existing Merki hardware could not provide. So to not lose the contract, Cisco got a couple of engineers to hack together this kludge so they could be a merki solution but meet the hardware requirements. And once it was done they started selling this to the general public. But yeah the view here is this thing is still Beta. ... View more

I am currently working on the same phones, Poly CCX, and Microsoft Teams.  The Poly CCX firmware released recently, version 1.0.1.0054, will make the Poly CCX (400, 500, and 600) honor the port configurations you set in the Teams Admin Center under Meetings, Meeting Settings, in the Network section.  The suggested setting is TCP/UDP ports 50000 - 50019 for Audio, 50020 - 50039 for Video, and 50040 - 50059 for Screen Sharing.   Using the packet capture feature, we saw voice traffic from the CCX using the configured ports for Audio but not automatically adding DSCP value.  If you can use source ports in your Quality of Service settings on the switch, you can then set a rule to mark TCP and a rule for UDP for the selected ports with the appropriate value.   Microsoft's document for setting up QoS in Teams was updated recently, 8/6/2020.  It explains configuring the ports and recommendations to insert DSCP markers. https://docs.microsoft.com/en-US/microsoftteams/qos-in-teams?WT.mc_id=TeamsAdminCenterCSH   Good luck ... View more

Its just a management/ alerting  setting. You can set it at the switch settings ... View more

>Am I correct that SSD latency might be something like 30 microseconds?   Drives like Intel's 900P have a latency of 10us. https://ark.intel.com/content/www/us/en/ark/products/123623/intel-optane-ssd-900p-series-280gb-2-5in-pcie-x4-20nm-3d-xpoint.html    Next year, who knows. ... View more

While not required many times, we frequently run into situations where it is nice to be able to plug a device (or even a switch with multiple devices) into the LAN port. This is something we do with the Orbi's, so it would be great to see this on Meraki Go so we can use it in more situations. ... View more

It seems like 26.5 may have resolved the issue. ... View more

It 100% should be PEAP.  Check the log in the Meraki dashboard as well to see if it says anything interesting. ... View more

@PhilipDAthwrote: Check out some of these "before and after" pictures.  It should be possible to run the cables so you can remove kit without it being a major issue.   https://community.meraki.com/t5/Off-the-Stack/Before-and-After-Pictures/m-p/4650/highlight/true#M87 They don't help too much because we have an enclosed rack with PDU's running up one side and a wire duct running up the other.  Those are the two things that make it too narrow to pull the switch straight out.  If it wasn't as deep, I could probably tilt it or if the brackets were removable like all our other equipment, I could just remove one or two which would then allow it to slide out the rest of the way. ... View more