Before the upgrade had no issues, now on a tower with a cluster of 6 ap’s
Random people drop off if the tower is rebooted and do not come back.
The AP they were connected to does not show up in ap eval but sometimes if I reboot the ap again they show up.
Anyone else seeing this?
These are 2.4 Advantage AP’s
I have not noticed that with 900MHz, fortunately. I can’t speak for 2.4GHz =(.
I did, however, have a problem upgrading all my 900 gear. There were a few times where CNUT got stuck at “programming” and froze for over 10 minutes. The SM’s would reboot like a normal software upgrade, but when they came back up they would still be 8.1.5.1
I would simply retry it a few times and eventually it would go through.
8.2.2 seems to be purring good for us so far…knock on wood.
I just upgraded several of my 5.7 sm and have had one to not register back to the ap. A reboot of the sm got it going again. Luckily I had a back door in to reboot it…I am going to let these few run a couple of days before I do more.
Any one else getting this once upgraded to 8.2.2 — This is a P9 running NAT and DHCP.
SM still seems to work fine after this upgrade.
00:12:45 UT : 01/12/01 : File src/root.c : Line 425 System Startup
00:12:45 UT : 01/12/01 : File src/root.c : Line 430 Software Version : CANOPY 8.2.2 SM-DES
00:12:45 UT : 01/12/01 : File src/root.c : Line 434 Software Boot Version : CANOPYBOOT 3.0
00:12:45 UT : 01/12/01 : File src/root.c : Line 444 FPGA Version : 100207
00:12:45 UT : 01/12/01 : File src/root.c : Line 448 FPGA Features : DES, Sched
00:13:30 UT : 01/12/01 : File src/syslog.c : Line 1283 Time set
00:13:37 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
00:13:37 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
00:13:37 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
01:13:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
01:13:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
01:13:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
02:58:47 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
02:58:47 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
02:58:47 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
03:58:53 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
03:58:53 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
03:58:53 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
05:43:58 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
05:43:58 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
05:43:58 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
07:29:02 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
07:29:02 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
07:29:02 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
09:29:12 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
09:29:12 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
09:29:12 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
10:29:17 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
10:29:17 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
10:29:17 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
12:14:22 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
12:14:22 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
12:14:22 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
13:59:27 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
13:59:27 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
13:59:27 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
15:44:32 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
15:44:32 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
15:44:32 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
17:29:37 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
19:14:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
19:14:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
19:14:42 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
20:59:47 UT : 01/12/01 : File src/arp.c : Line 1639 netIF is NULL for SrcIF=0
I believe that I read about this log entry in the Readme notes for 8.2.2 and it is a harmless line that can be ignored.
However, read the README (!) file to confirm.
Yes… you’re right! (page 29)
Since this is the case… We haven’t had any problems with 8.2.2
cbotts wrote: Before the upgrade had no issues, now on a tower with a cluster of 6 ap's
Random people drop off if the tower is rebooted and do not come back.
The AP they were connected to does not show up in ap eval but sometimes if I reboot the ap again they show up.
Anyone else seeing this?
These are 2.4 Advantage AP's
Yes, I got the same problem too, but still with 821v2
What we do is, change to another new SM, and try to scan again. Usually it worked.
Look like everyone is on "wait and see" situation before upgrading to 8.2.2
damn you motorola....everything worked flawlesly at 7.36 but now, it just rubbish.
We are trying to use XR ubiquity card with mikrotik, and see the result for ptp.
We just finished upgrading to 8.2.2 across hundres of SM’s and no problems.
Support calls on NAT customers went away and VoIP is great.
Go ahead and upgrade IMO, there are THOUSANDS of SM’s running this now with no problems.