@TravisFleming1 is there a reason that the MS-MX link is running at 100Mbps?  The ports on both devices are capable of 1Gbps. ... View more

@HMP we are on 28.2 now and that seems fine.  I will aim to do some more testing tomorrow to confirm. ... View more

@MrBear the sector antenna does about an 80 degree spread so would be ideal for you, I think it will make a big difference.  If you want to keep the existing antennas I'd position the AP where the tree is as it goes all round! ... View more

@MrBear with those antennas I would not expect a long range as they are not focused in any particular direction.  Do you have all round coverage requirements, or do you want it all in front of the AP etc.?  If in one direction then a pair of sector antennas might be better for you as they extend the signal distance by up to 2.5 times - 5 GHz Sector Antenna (13 dBi Gain) | Cisco Meraki ... View more

Just cable tested a non PoE device running at 100Mbps on an MS210 with 14.24, pair 3 shows open (which technically is correct): Tested a 100Mbps connection on an MS225 with 14.22, pair 3 still shows short there:   ... View more

@pesos that sounds like a perfect solution.  You can definitely have more than one org, I have one for work and one for home and both are accessible using my work Cisco identity. ... View more

@pesos if you add it to a network it will give you 30 days to test it, if the org is in co term licensing mode then you will get a warning about buying a license and you must remove it (or buy the license) before the deadline as otherwise all your devices will be impacted.  If in the mode where each device has its own expiry then you will get 30 days to play. ... View more

@TravisFleming1 put the MXs on your site inside the LAN in single armed concentrator mode.  Connect the MPLS circuit to your LAN and at the other end to WAN 2 on their site, presumably that was spare?  Make sure that their MX WAN2 can reach the internet via your LAN by setting the correct routes. Enable SD-WAN on the network that contains the MXs at your site and the MXs on your site should connect to their MXs and use both routes. ... View more

@IT_Tropolis Cisco's focus is on AnyConnect and that is now available on MX. ... View more

Hi @TASIS_IT,   We are running 28.1 on most of our 100+ APs and at least 30 of those are MR42/52 models.   It has been stable so far, I'll let you know if we see any problems. ... View more

@DarrenOC that naming convention looks awfully similar to the one I've been using for the last 25 years 😈. It works worldwide though I add one extra letter:   Country code | site code | technology | device type | number   i.e. UKBNES1 - United Kingdom, Brighton, Ethernet, Switch, 1   For a fibre switch replace E with F, for Token-Ring we used a T, however ES is replaced entirely with FW for corporate firewalls and PI for public internet ones as we aren't entirely consistent and we've never had a firewall that isn't Ethernet!   Ultimately if everyone can find the device from the name then who cares what format you use! 🙂     ... View more

@Twitch it is a big job if you have a lot of devices, but the APIs can be used to make a lot of it less bad... ... View more

@Twitch why not combine the two organisations? ... View more

@KarstenI I'll second that, we've got a couple of APs that keep dropping down to 100Mb/s a few days after a reboot, despite being on shielded CAT6/A structured cabling and patch leads.  I think there are some contacts that need cleaning in the chains, but as our wireless traffic isn't high speed, just lots of users, fixing it isn't a top priority yet...  ... View more

A quick comparison on what might have been..     ... View more

@BHDJon MS390 is a Cisco 9300 with a software layer on top, hence it behaves like other Cisco iOS switch stacks ... View more

@DarrenOC you can stop being quiet now 😉 ... View more