Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
This week I finally got a maintenance window to be able to upgrade one of our pairs of C9500-12X pairs to a version supported by the Meraki dashboard.The ISSU upgrade (from the CLI) worked perfectly from 17.9.5 to 17.15.4 and took about 35 minutes.St...
Switches - MS software versions MS 18.1.6 changelog New feature highlightsGroup Policy ACL on MS130 & MS150Maximum MAC support in MAC Allowlists802.1x limited access mode with pre-auth GPACLLocal Status Page connectivity diagnostics enhancementsLayer...
I know it is probably a marketing/salesy thing, but is there any real reason why an unmonitored/unmanaged Catalyst switch shows up with a diamond on the topology with the comment 'Not enough information to draw the root of this network."?Looking at t...
Security appliances software versions MX 26.1.2 changelog Executive summaryThis is a new beta release for MX 26.1. It contains new feature functionality that expands connectivity options and security capabilities.For customers already running MX 26.1...
Perfect, both of us who had 9500s running in device configured mode had them appearing in the wrong part of the topology. 9300s appear correctly in either mode so happy to see that 9500s at least work in cloud configured mode
You might want to even go down to 20MHz, but I would try 40MHz first, as that might be good enough. The theoretical maximum speed for a client will drop to ~600Mb/s for 40MHz instead of ~1.2Gb/s for 80MHz but in reality you may get more throughput, ...
I would start by reducing the channel width to 40MHz as if any of the 4 bonded 20MHz channels overlap with a neighbour, you get interference with your current setting.