I'm running a script on the management box that polls all the APs every 10 minutes, and an AP has no clients associated with it, and <meta charset="utf-8">if it hasn't done so yet, it reboots the AP.<div><br></div>
<div>This is to get around the recently-discovered mode-resetting problem: the config doesn't get saved, or fully used. I've previously explicitly saved the configs on each AP, and chelliot has updated the autoprovisioning code to work around this failure, but the APs that are out there and running could lose their IP address at any time due to the weird DHCP behavior.</div>
<div><br></div><div>The code is on the management box in ~fenner/src/pupu/reload-idle-aps/ . The list of APs being looked at is in aps.txt; the list of APs that have been reloaded is in aps-reloaded.txt; the script's output is in loop.log. You can find out what APs have not yet been rebooted by the script with</div>
<div><br></div><div><div>[fenner@management ~/src/pupu/reload-idle-aps]$ comm -23 aps.txt apnames-reloaded.txt</div></div><div><br></div><div><br></div><div>The current list:</div><div><br></div><div><div>Still to be reloaded at Sun Jul 24 15:53:28 GMT 2011:</div>
<div>ap101 ap102 ap103 ap104 ap105 ap110 ap111 ap112 ap119 ap120 ap121</div><div>ap123 ap124 ap125 ap127 ap130 ap131 ap134 ap138 ap139 ap141 ap142</div><div>ap144 ap145 ap147 ap151 ap153 ap157 ap159</div></div><div><br></div>
<div>(note that this list may have un-deployed APs in it; when it gets down to only un-deployed APs I'll stop running the script.)</div><div><br></div><div> Bill</div><div><br></div>