Ok kids, I just found a weird one.
Went out and applied some config changes to some SMs in our network. After the config change, of course, a reboot is necessary. Finally got to one customer, made the changes, rebooted him, and suddenly everyone drops off. I get back into the AP, and discover that it rebooted as well.
Must be an abberation. Moved on and reconfigged several other SMs, all reboot without problem, AP stays online.
I go back to this one customer, config changes I applied are there, saved, etc., etc., just fine. Just for grins, I reboot the SM again. Guess what, the AP reboots too.
Everything is running 6.1 code, software scheduling, all non-advantage units.
Weird.
You state all your units are running v6.1; check Boot and FPGA also.
I had the same problem with a single SM when upgrading APs and SMs to v4.2.3 from a mix of Nahum, v3.x, and v4.0.x. I presumed the problem was related to the mismatch between software, FPGA, or Boot versions, but I haven’t tried to duplicate the problem.
I’ll pay close attention when I upgrade to v6.1. I’d like to test it immediately, but the SM in question services my one customer who needs their Internet connection 7x24.
I can confirm this. We had everything on 4.2.3 (AP’s & SM’s). On some sectors, when the SM was forced to reboot, the AP was rebooted too which means that other clients connected to this AP was disconnected also. Asked the tech. supp but no avail. 
This is very sad.
Teknix wrote: You state all your units are running v6.1; check Boot and FPGA also.
Heh, should have clarified. All are FPGA 111504 and Boot 3.0. I did know at least that much. :)
It's interesting, I have 50 SMs between two APs, and this is the only SM with which I have this problem.
Same problem, but out of 121 SM’s I have several, I’ll say around 20 SM’s that do that
ccie4526 wrote: I go back to this one customer, config changes I applied are there, saved, etc., etc., just fine. Just for grins, I reboot the SM again. Guess what, the AP reboots too.
I have seen this problem as well when you connect to a subscriber using the logical unit id (LUID). I have tried tracking down the problem and once thought it was the browser I used on windows, firefox. However, I tried using different browers on FreeBSD and found that the same thing occurs with all of them including IE on windows.
Since the problem is variable, I (typicallly) no longer reboot the SM when connected through the AP. Instead, I remote into the SM directly and reboot that way.
Unfortunately, there are some cases where I must reboot a unit through the LUID. During that time, I do one of two things...A) I pray that it doesn't reboot the AP. B) I wait until after typical business hours to reboot the unit.
I have also seen this issue as well, made a change in an sm and rebooted the sm and the AP reboots as well as the sm too.