fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify current unifi protect chime state
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-26 20:10:45 +00:00
parent a282fe43bd
commit 77da65e64a
16 changed files with 193 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
home/doris-dashboard/docs/network-redesign-implementation-runbook.md
View File

@@ -2,6 +2,11 @@
> For Doris: use this during the live UniFi change window. Goal is a controlled cutover with explicit validation and rollback at each boundary.
Historical status note:
- this runbook came from the 2026-05-22 cutover-planning wave
- preserve it as the detailed plan, but do not treat every "tomorrow" step as still pending without checking later result docs
- current remaining-work truth lives in `network-migration-remaining-checklist-2026-05-22.md` and `unifi-protect-doorbell-chime-current-state-2026-05-26.md`
Goal: deploy the target VLAN/SSID/firewall design with minimum drama, keep legacy CIA Via as a quarantine lane for devices that cannot yet be migrated, and finish the window with an understandable, supportable network.
Architecture summary:
@@ -258,7 +263,7 @@ Exit criteria:
### Phase C: Management cleanup first
1. Ensure UDM, switches, and AP management surfaces are on VLAN 10 intent.
2. Remove obvious non-infrastructure devices from Management.
3. Move Protect chimes out of Management as top cleanup item if Security lane is ready.
3. Treat Protect chimes as a documented temporary Management exception unless you are explicitly re-validating their Protect health on a non-Management lane.
4. Re-validate UniFi visibility of gateway, switches, APs.
Rollback if:
@@ -272,14 +277,14 @@ Exit criteria:
### Phase D: Build/activate Cameras lane
1. Activate/validate `NET-CAMERAS`.
2. Activate `Security` SSID if used.
3. Move doorbell and Protect chimes to Cameras/Security.
3. Move doorbell and Protect chimes to Cameras/Security only if Protect health is explicitly validated during the move.
4. Validate app/admin behavior.
Rollback if:
- security devices fall offline and cannot be recovered quickly
Exit criteria:
- doorbell/chimes are no longer polluting Management
- either doorbell/chimes are healthy on Cameras/Security, or the documented Management exception is preserved intentionally
- Camera lane exists for future growth
### Phase E: Move core servers to Servers VLAN 30
@@ -353,8 +358,8 @@ Exit criteria:
## 9. Explicit Device Triage
Move tomorrow if practical:
- Protect chimes
- doorbell
- Protect chimes only during an explicit Protect-validation test
- doorbell only if healthy-state validation is immediate and reversible
- PD
- Serenity
- Nomad
@@ -403,6 +408,7 @@ Minimum successful tomorrow outcome:
- IoT lane exists and at least easy-value devices are moved
- Legacy CIA is converted into explicit quarantine/sunset lane
- no broad insecure exceptions were added out of fatigue
- any documented temporary Protect chime exception is written down instead of being rediscovered later
Nice-to-have, not mandatory tomorrow:
- U6 LR restored and tuned