Ideally from the Cases section in Dashboard (? at the top right > Cases) ; alternatively from meraki.com/support, however you'll need to provide some details about which organisation, so I'd recommend the first method!   Giac ... View more

thanks all for the replies   looks like we are going to move forwards   thank you ... View more

We came across the same issue and found bug https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvq00652/?rfs=iqvred which was affecting our test results. ... View more

Hey guys, fix it. Downgrade version 25.x  all done. But study the case for upgrade 26.x (the bug list is interesting)   regards   Entao, se algum amigo de profissão chegou até aqui. Conselho faça um downgrade.  Mas estude o caso para fazer o upgrade para 26.x (o bug list é extenso, até uma vergonha a Cisco liberar um equipamento com tanto ajustes ) enfim. all Done.     ... View more

Yes it is. 3 days if i'm not mistaking. Latest update I got (again) was that not everything is yet in place but i've been put on the list where people are chosen from. ... View more

Isn´t it easier to use the scheduling of the switch port. Halve an hour a day scheduling as off, and after the time is run then the accesspoint reboots. It an easy way without any scripts. You find it on "switch" - "port schedules".   ... View more

thank you for the answer   it makes sense that they are saying with the pair-wise but would this effect all devices at the same time? the wifi connected but no traffic is good as well as it would make sense when the wireless looked 100% but there is a potential traffic is not passing   when it comes to devices I have 3 different devices (make and model) that were all effected with this event so the chipset part seems weird  or do you mean the chipset in the Meraki AP? in this case the AP was an MR42 - but I guess all chipsets are pretty much the same across the Meraki product range?         ... View more

thank you,   makes sense when you say create the user - I was just doing a policy to says anything matching the Meraki_test without creating it on the ISE box first   I will give this a go   for the moment we now had TAC looking at out ISE box because we have a bug with out logging causing the primary to crash so we are down to the secondary ISE box only   should of just stuck with windows radius would of been a world of ease - but security teams have their crazy ideas of buying boxes for $$$$ and then dumping them off just so they can say they have the product (rant moment) ... View more

Hi Nolan   thank you for the reply   I am heading to the warehouse next week to survey again and again to validate how the power/performance have changed   I use Netscout survey Pro and we have Zebra devices which has some SSIDer type app giving RSSI details I had spent weeks on the deployment previously getting the roaming to a reasonable level I I worked out my 10-15%  with multiple surveys for single APs showing the SSID and in most cases tape/chalk on the floors mapping out dbm and roaming variables for the devices   the warehouse has moving stock and liquids/foil in most places including a 3 level warehouse floor so I had to get my bleed levels as accurate as possible   if I receive a call regarding wireless they can tell me the floor/isle and I know what AP they should be on/joining/leaving as I know the boundaries I have in place to keep signal and roaming conditions   what I was seeing after the upgrade were devices far passed the boundaries configured for roaming still attached to the same AP also at the time of roam they were now hopping between multiple APs within 30-50secs of joining I had our remote technical guy take a walk to different areas with a Zebra device and the signal was -3 to -5  better than before which in most cases would be a good things but the size of this warehouse and floors separated by metal grate - this adds lots of interference with the power increase this is bringing the possibility of overlapping channels closer today in places of high density so this is potentially now the issue     the constant roaming was effecting the performance of the devices to make them unusable - after the downgrade it has been perfect again   at first I though I had forgot to disable client balancing but it was already disabled   I think I am going to be spending a long time troubleshooting this again - I don't mind it as its fun work mapping It all out I just was not expecting the impact   when it comes to auto power and auto channel this went badly for us practicing back on install in this warehouse - it was like a wave of change every 20-30mins with the amount of reflection/scattering and the thin floors the APs really were not handling it well   we have other warehouses/offices running on auto no problems so I am have nothing against letting the software do its job - but everywhere always ends up with a problem site   Cheers ... View more

Hello, I have sites with MR26 with exact same problem   try asking meraki to revert your firmware to 23.11 and see if t becomes stable   if it does please reply and let me know as we are in discussions about this problem now   ~Cheers ... View more