White Sand Villas & Spa — Network Fix-It List
Field work order for the on-site technical team · compressed from the full diagnostic report · 2026-07-11
How to use this: Work top to bottom. The "Today" section fixes the things affecting the most guests right now — do those first and in order, since #2 and #3 partly depend on #1 being done. Everything has an exact device name, IP, and port so you don't need the full report to act. Each card has a Verify line — that's how you confirm the fix actually worked, not just that you did the step. Full technical justification for every item lives in the main report if you want the "why."
Do today — affects the whole network or the most guests
1Find and disconnect the network storm loop
Switch TVs ServerRoom (192.168.1.233) — port 5 (device 192.168.0.6, "tdch") and port 8 (device 192.168.1.7), both GbE
- Go straight to Switch TVs ServerRoom — both storm devices are confirmed on this one switch, ports 5 and 8.
- Look for a single cable run connecting port 5 back to port 8 (directly, or via one unmanaged switch/hub sitting between them) — that's the loop.
- Unplug that cable at one end and check if the storm stops (see Verify below).
- Once confirmed, leave that cable disconnected, or re-terminate it correctly if it was meant to go somewhere else.
Verify — In the UniFi controller, go to a switch's port stats and watch the broadcast/multicast packet rate on any Management LAN port: it should drop from a constant flood to near-zero within a few seconds of disconnecting the right cable.
Tools: laptop with controller access, cable tracer/toner if the loop isn't obvious by inspection
2Fix Switch Pro V8 (aggregates ~30 downstream switches — most guest villas)
192.168.1.220 · model USLP8P · rack/cabinet where Pro V8 lives
- Do step 1 first and wait ~10 minutes — most of Pro V8's jitter is very likely caused by the network-wide storm, not the switch itself.
- Physically check port 3 — the only port on this switch actually expected to power an AP. If that AP looks unpowered, check the cable/connector at both ends.
- Power-cycle Pro V8 in an off-peak window regardless (it's been running 94 days straight) — unplug, wait 10 seconds, plug back in. This will drop ~30 downstream devices for a minute, so warn guests/staff first.
- Only escalate to "replace this switch" if jitter is still bad after both step 1 and step 3 are done.
Verify — Ping 192.168.1.220 continuously for a minute after the power-cycle; sub-2ms consistent response with no timeouts means it's fixed. Also spot-check Switch V10 Livingroom (192.168.1.155) — it often clears at the same time as Pro V8.
3Fix Switch Middlestaff WallBOX (currently flapping every ~7 minutes)
192.168.1.110 · model USL8LPB
- Swap the power adapter for a known-good spare first — this is the most likely cause of a switch that keeps dropping and reconnecting.
- If it still flaps after 15-20 minutes on the new adapter, try a different wall outlet (bad outlet/circuit is the next most likely cause).
- If neither fixes it, the switch itself needs replacing.
- While you're there: reseat or replace the uplink cable at Switch POWER House (192.168.1.17), port 3 — that's the link feeding WallBOX.
Verify — Watch the controller's device connectivity log for 192.168.1.110 for 30+ minutes after the fix; zero reconnect events (down from ~1 every 7 minutes) confirms it. Note: Switch Middlestaff-Rooms and New carpentry uplink through WallBOX, so check those come back stable too.
4Inspect the core uplink (gateway ↔ switch fabric) — getting worse
Gateway port eth9 (on the UDM Pro Max, 192.168.1.1) ↔ its far-end SFP on the switch fabric
- Re-seat the SFP module on both ends (gateway side and switch side) — a loose/dirty SFP is the most common cause of intermittent 10G/1G renegotiation.
- Inspect the fiber patch cable for visible damage or a dirty connector; clean or replace if in doubt.
- If a spare SFP module is available, swap it in as a quick elimination test.
Verify — Check the controller's uplink history for this port over the next few days; incidents were accelerating (7 days → 4 days → 2 days apart), so the bar is "no renegotiation event for at least a week."
Do this week — real faults, but lower guest impact
Re-terminate cabling — degraded access-point uplinks (24 APs — wired at 100 Mbps or PoE not negotiating; this reads as "bad Wi-Fi" to guests but the radio is fine)
For each: replace or re-terminate the cable run between the AP and its switch port listed below. Use Cat6 cable (Cat5e is the absolute minimum if that's all that's on hand) — solid-core for permanent in-wall/ceiling runs, stranded patch cord only for the short jumper at each end. Terminate both ends to the T568B pinout to match the rest of this network. Keep any single run under 100m. If a run is exposed to sun/weather (roofline, outdoor umbrella, etc.), use outdoor/UV-rated jacketed cable, not indoor-rated. No switch model in this fleet caps speed below gigabit in hardware, so every one of these is a physical fix, not an equipment upgrade. Verify: the AP's uplink port shows 1000F and PoE "Good" in the controller after the fix.
| Access Point | AP IP | Switch → Port |
| V4 - Living Room | 192.168.1.69 | Switch V2 · port 2 |
| V7 - Bottom Bedroom | 192.168.1.83 | Switch V7 · port 8 |
| V10 - Living Room * | 192.168.1.79 | Switch V10 Livingroom · port 2 |
| Staff - Omar Office * | 192.168.1.94 | Switch Reception · port 3 |
| Senior - Downstairs | 192.168.0.164 | Senior staff · port 5 |
| V5 - Living Room | 192.168.1.89 | Switch V5 · port 3 |
| v2 living room new | 192.168.1.96 | Switch V4 · port 4 |
| Beach V4 - Mesh Pro | 192.168.1.189 | Switch V4 · port 6 |
| V11 - room 5 | 192.168.1.97 | Switch V11 technical · port 2 |
| Staff - Maintenance (new) | 192.168.1.217 | Maintenance USW Lite 8 PoE · port 6 |
| restaurant bar | 192.168.1.72 | Switch Bar PoE · port 5 |
| Restaurant - Terasse | 192.168.1.143 | Switch Kitchen · port 7 |
| Staff - Kasia Store 2 | 192.168.1.244 | Switch KasiaStore · port 3 |
| V9 - Living Room | 192.168.1.80 | Switch V9 new · port 8 |
| V5 Bedroom | 192.168.1.102 | Switch V5 · port 2 |
| V7_AP Livingroom U6-Lite | 192.168.1.76 | Switch V7 · port 2 |
| V14 Technical | 192.168.1.175 | Switch V14 new · port 2 |
| V10 - Upper Bedroom | 192.168.1.87 | Switch V10 · port 2 |
| New Kiteschoold inside U6 Lite | 192.168.0.227 | Switch Kiteschool · port 7 |
| V9 AP Bedroom Upstairs | 192.168.1.200 | Switch V9 new · port 6 |
| Nowy AP senior U7 Lite | 192.168.1.167 | Senior staff · port 3 |
| Beach_umbrella V2 | 192.168.1.158 | Switch V2 · port 7 |
| U7 Pro Max | 192.168.0.153 | Senior staff · port 4 |
| (unnamed AP) | 192.168.0.206 | switch cinnamon · port 6 |
Down switches — physically check power/cabling (5)
| Switch | IP | Note |
| Switch MainGate security | 192.168.1.34 | Unreachable 4/4 sweeps |
| Switch V3 | 192.168.1.52 | Unreachable 4/4 sweeps — also a designated IGMP querier |
| Switch Shop USW Flex | 192.168.1.207 | Unreachable 4/4 sweeps |
| Switch Beach Resta | 192.168.1.213 | Unreachable 4/4 sweeps |
| Switch BeachResta Cameras | 192.168.1.232 | Unreachable 4/4 sweeps — also a designated IGMP querier |
Check power LED and uplink cable at each. Verify: device shows "Connected" in the controller and passes a sustained ping.
Down access points — physically check (5)
| AP | IP | Note |
| V13 Technical Room | 192.168.1.169 | Highest confidence real fault — unreachable AND broken radio config (undefined channel). Start here. |
| Guest - Boutique Mesh Pro | 192.168.1.88 | Unreachable 2/2 sweeps |
| senior staff new (R4) | 192.168.1.234 | Unreachable 2/2 sweeps |
| Cinnamon Room 3 - Terrasse | 192.168.1.70 | Unreachable 2/2 sweeps |
| Boutique Inside / Tennis court | 192.168.1.107 | Two controller records share this one IP — physically confirm which AP (if either) is actually live, then delete the stale record in the controller |
Verify: device pings clean and shows "Connected" with a valid channel in the controller.
·Replace the cable at Switch office Store, port 4
192.168.1.174, port 4 — currently linked at 10 Mbps (should be gigabit)
- Trace and replace the cable run to this port — the switch hardware supports gigabit here, so a 10 Mbps link means a bad cable, connector, or wall jack.
Verify — Port shows 1000F (gigabit full-duplex) in the controller's port table after reconnecting.
Lower priority / verify later — not urgent, or not an on-site fix
Escalate two WAN outages with the ISPnot on-site
Liquid Intelligent Technologies — 11.6h and 22.1h outages this past week
Phone call / ticket, not a physical job. Ask for root cause and an SLA commitment. WAN quality when the link is up is fine (no bufferbloat) — this is purely about the two long outages.
Housekeeping — naming and duplicate records
- Name the two unidentified APs in the controller:
192.168.0.192 and 192.168.0.206.
- Confirm "Zanzibar White Sand Luxury 03" is a known AP, not a rogue clone of the guest SSID.
- After confirming which of Boutique Inside / Tennis court (192.168.1.107) is the real device, delete the stale duplicate record.
Trace the IGMP querier at 10.0.0.1
General IGMP queries on the TV VLAN are coming from 10.0.0.1, which isn't part of any configured subnet here. Worth tracing once the higher-priority items are done — this is a "should investigate," not a known active problem. Also worth re-confirming multicast/IPTV still fails over correctly now that 3 of the fleet's designated querier switches (V3, BeachResta Cameras, Pro V8) have been flagged elsewhere in this list.
Wired-vs-wireless speedtest in a complaining villa
Have a staffer run a phone speedtest over Wi-Fi, then plug a laptop into the same villa's wall port and repeat — this rules Wi-Fi/RF in or out as a contributing cause once the wired-side fixes above have landed.