We have upgrade to the newest fimware and are using software scheduling, but are still have certain clients with extremely high re-reg counts. We have had numbers in the 5000 range in just over 3 days uptime. Not all customers on this ap are having the issue. Also, the connection quality of the clients seem to be OK.
RSSI (Avg/Last): 1639/1636 Jitter (Avg/Last): 3/3 Power Level (Avg/Last): -64/-64
This is an example that is not working well.
Just a ?.. How come you didn’t switch back to Hardware Schedualing after you upgraded to 7.2?
We actually had not ever been on hardware, should we be? Also, to test that would we need to change all clients and AP at this location?
you would need to change all APs and SMs at a location that are on the same frequency.
Getting back to the origional question, a close exam of the local RF conditions for the offending subscribers could shed some light.
(scheduling some downtime and) testing with the APs off would make interference easier to see.
We are also still seeing high reg counts on our 900 equipment. We did a spectrum analysis and it looks fine on both ends. We saw this dramatically increase when we recently added customers to the tower. We now have 38 on that AP. Not sure if number of SMs on an AP matters, but the reg and re-reg counts are now very high for multiple SMs.
We are noticing that the SM has a hard time registering. Once it registers, it will usually stay connected. Below is a sample from the session page. From what we are experiencing, this firmware still needs some work…
LUID: 021 : MAC: 0a-00-3e-90-31-1d State: IN SESSION (Encrypt Active)
Site Name : xxxxx
Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 070605 (DES Sched) P9
Session Timeout: 0, AirDelay 90 (approximately 2.51 miles (13230 feet))
Session Count: 51, Reg Count 18, Re-Reg Count 197
RSSI (Avg/Last): 1807/1813 Jitter (Avg/Last): 4/3 Power Level (Avg/Last): -63/-63
DnRate(B): 1024 DnLimit(B): 20000 UpRate(B): 512 UpLimit(B): 5000 (kbit)
LoUpCIR(D): 0 LoDnCIR(D): 0 (kbps)
Rate : VC 37 Rate 2X/1X
LUID: 022 : MAC: 0a-00-3e-90-80-79 State: IN SESSION (Encrypt Active)
Site Name : xxxxx
Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 070605 (DES Sched) P9
Session Timeout: 0, AirDelay 49 (approximately 1.36 miles (7203 feet))
Session Count: 3, Reg Count 1, Re-Reg Count 7
RSSI (Avg/Last): 1921/1958 Jitter (Avg/Last): 3/4 Power Level (Avg/Last): -61/-60
DnRate(B): 1024 DnLimit(B): 20000 UpRate(B): 512 UpLimit(B): 5000 (kbit)
LoUpCIR(D): 0 LoDnCIR(D): 0 (kbps)
Rate : VC 38 Rate 2X/1X
LUID: 023 : MAC: 0a-00-3e-90-61-3c State: IN SESSION (Encrypt Active)
Site Name : xxxxx
Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 070605 (DES Sched) P9
Session Timeout: 0, AirDelay 11 (approximately 0.31 miles (1617 feet))
Session Count: 404, Reg Count 197, Re-Reg Count 1604
RSSI (Avg/Last): 1767/1775 Jitter (Avg/Last): 4/4 Power Level (Avg/Last): -63/-63
DnRate(B): 1024 DnLimit(B): 20000 UpRate(B): 512 UpLimit(B): 5000 (kbit)
LoUpCIR(D): 0 LoDnCIR(D): 0 (kbps)
Rate : VC 39 Rate 2X/1X
LUID: 024 : MAC: 0a-00-3e-90-77-d7 State: IN SESSION (Encrypt Active)
Site Name : xxxxx
Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 070605 (DES Sched) P9
Session Timeout: 0, AirDelay 44 (approximately 1.22 miles (6468 feet))
Session Count: 7, Reg Count 1, Re-Reg Count 21
RSSI (Avg/Last): 1887/1890 Jitter (Avg/Last): 3/3 Power Level (Avg/Last): -61/-61
DnRate(B): 1024 DnLimit(B): 20000 UpRate(B): 512 UpLimit(B): 5000 (kbit)
LoUpCIR(D): 0 LoDnCIR(D): 0 (kbps)
Rate : VC 40 Rate 2X/1X
luid 21 and 23 dont happen to be using cordless 900 phones do they?
They have 2.4Ghz cordless phones, but no 900mhz phones.
I have noticed that in general, 900 SMs take much longer to register - sometimes when they are rebooted (or the AP is rebooted) they may go through 10 sessions and 50 re-regs before they get a session that sticks.