Anyone else experiencing AP’s running NV2 that completely stop talking to the Client Radios ?
When this happens none of the Clients are reachable - ping, Mac Ping - fail. Power cycling the client does not resolve the problem. Disable/Enable the AP interface and everything starts working again
Anyone ??
we would need more detailed info on your Nv2 network so we could try to reproduce it.
How often does it happen?
what usually triggers the lockup - upload/download or some bandwidth testing?
I have NV2 running on 8 AP’s now and 10 PtP links. NV2 Distance and Slots vary depending on the AP.
The problem appears to be completely random. It first happened on a PtP link only 13 hours after I installed 5.21 on those two RB’s. It has since happened to THAT PtP again, and another one as well.
All of the “AP’s” that have had the problem so far are running as a router, no bridging.
The most recent one (that I sent you the suppout.rif from) has 42 connected clients. Radius Auth. for Wireless. Radius DHCP. Nv2 Period=4, Cell Radius =10. No NV2 security. Card is an Atheros 5413. RB is a 433AH. Uptime since upgrade to 5.21 is ~4 days 7 hours. ALL on this AP clients are also 5.21.
You can email me at the address from ticket [Ticket#2012102366000597] if you need further info.
please try to lower the tdma-period-size to 2 on the AP and check again.
The AP and the Clients uses the legacy AR5413 chipet cards?
What wireless mode you use for the wireless clients: station, station-wds or station-bridge?
The same problem with my AP which you have remote access. [Ticket#2012062266000221]
The problem occurs randomly (even just once a week). No BW test running.
I’m having same problems on grooves and metals. Random reboots, disconnects and other crap like that. To make things even more fun, after /system package downgrade metal went bye-bye. Feels like 2.9 all over again
This isn’t a reboot problem. The AP side just stops talking to the CPE’s. CPE’s are mostly R52H on RB411. I have probably 30 Grooves as CPE’s running 5.20 or 5.21 and no issues with them. No Groove AP’s though. Other than this issue 5.21 has been very stable - and latency and jitter are way better than previous versions of NV2.
Well, I replaced a groove after upgrading it to 5.21 with Metal. Now co-worker gets on the mast to replace metal with another metal. Either two devices were broken, or 5.21 is broken. I’m not planning on uploading 5.21 again. Metal is now confirmed dead after attempt to downgrade 5.21->5.20 - ethernet doesn’t even come up…
Yes, that’s correct. Not sure about any subtle hardware differences, but it’s mipsbe. Oh well, sent some supouts with wireless lockups, maybe it will get fixed along that
BTW: Yesterday overnight I tried setting the TDMA slots to 2, but could only authenticate ~24 CPE’s. The status Tab showed “Connected 42, Authenticated 24”. I cache radius responses for 2 minutes. Radius resends were low but the other ~18 CPE’s could not authenticate (?) In the end I could only lower the slots to 3 and still have all subs authenticate.