azcomputerguru/claudetools
1
0
Fork 0
Code Issues 59 Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from HOWARD-HOME at 2026-06-17 09:35:47

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-17 09:35:47
This commit is contained in:
Howard Enos
2026-06-17 09:35:56 -07:00
parent 8f0e576c49
commit 8f72178d8a
2 changed files with 52 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
clients/cascades-tucson/reports/2026-06-16-unifi-full-audit.md
View File

@@ -74,3 +74,37 @@ quirk, not a real fault. No action needed unless WAN2 misbehaves.
**Conclusion:** gateway/DHCP/DNS/WAN are not bottlenecking the wireless. The 2.4 GHz remediation
(power-down + coverage-redundancy disables) remains the correct and sole fix for the client-experience tail.
## Daytime re-check (2026-06-17, ~09:33, loaded network)
Post-remediation loaded-network measurement (overnight 6/17: 24 of 76 2.4 radios disabled, 42 set to Low
~6 dBm; Floors 5/6 + mesh untouched). Fleet healthy: 77 adopted / 2 disconnected (same known 108 + 1) --
**no AP went offline.**
**Active-radio-only snapshot (09:33, excludes the 24 disabled):** cu_total 67%, cu_interf 48%, clients 105
(vs pre-change active cu_total 77% / cu_interf 64%).
**Time-of-day-controlled hourly (this AM vs same hours yesterday @ full power):**
| 2.4 site-wide AM | Yesterday (full) | Today (post) |
|---|---|---|
| cu_total | 79% | 44% |
| cu_interf | 66% | 32% |
| retry% | 17.0% | 23.4% |
| satisfaction | 39 | 30 |
| sta/radio | 2.32 | 2.21 |
**Mixed result -- read honestly:**
- WIN: 2.4 interference/airtime is clearly down (fewer contending transmitters + smaller cells). On the
active radios, cu_interf ~64% -> ~48% (snapshot) / 66% -> 32% (morning hourly avg, fewer radios).
- CONCERN: **retry rose (17.0 -> 23.4%) and satisfaction fell (39 -> 30)** time-of-day-controlled. Likely
OVER-THINNING: Low = ~6 dBm is a 17 dB cut from auto (~23), and with 24 radios also disabled some edge
2.4 clients now reach a farther/weaker AP -> more retransmits, lower satisfaction. (Partly composition:
fewer 2.4 clients today, so the remaining tail may be the stubborn legacy/far devices.)
**RECOMMENDATION (needs Howard's go -- this re-check is read-only):**
1. Bump the KEPT 2.4 radios from Low -> **Medium** (~12-15 dBm): restores client signal while keeping cells
smaller than full power. `apply-radio cascades ng power medium --zone ...` per floor, then re-measure.
2. Do NOT expand disables further; consider re-enabling a specific radio if a dead zone/complaint appears.
3. Re-measure retry/satisfaction after the Low->Medium bump (same time-of-day) to confirm recovery.
The interference goal is met; the lever now is finding the power floor that keeps cells tight WITHOUT
starving edge clients. Medium is the likely sweet spot vs the aggressive Low.