UniFi: servers plugged into switches; server page in sections; My work; settings search and undo
UniFi: the controller's client list is matched to servers by IP address, so a server is connected through a switch or access point (and port). That is a dependency made by itself, shown on the server page, the Network devices page and the Connections map. IP Addresses can sync the devices' addresses. A server's page is split into Overview, Health, Network, History, Tasks and Settings, by ?view=; alerts link to the section they are about. My work lists what has your name on it: alerts you have, maintenance you started (extend, end with undo) and update runs you started, with a badge. Settings has a search box (and the command palette lists every setting). Removing a dependency, admin link, runbook, hand-made IP address, port opening or restore test is undone from the message instead of asked about first. Two backup tests used a fixed date and failed as days passed; they follow the real clock now. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
396e074108
commit
5e26e77340
45 files changed
+6224
-194
No files matched your search
+17
@@ -57,6 +57,8 @@ erDiagram
|
||||
integration_credentials ||--o{ integrations : "credential (set null)"
|
||||
integrations ||--o{ network_devices : "cascade"
|
||||
integrations ||--o{ network_segments : "cascade"
|
||||
integrations ||--o{ network_server_links : "cascade"
|
||||
servers ||--o{ network_server_links : "cascade"
|
||||
integration_credentials ||--o{ dns_providers : "credential (set null)"
|
||||
dns_providers ||--o{ dns_zones_cache : "cascade"
|
||||
dns_providers ||--o{ dns_records_cache : "cascade"
|
||||
@@ -678,6 +680,21 @@ Switches, access points and gateways read from a UniFi controller (see INTEGRATI
|
||||
|
||||
A device the controller no longer lists is deleted on the next read. Dependencies written by hand that mention a removed device are ignored.
|
||||
|
||||
#### `network_server_links`
|
||||
|
||||
Which server is plugged into which network device, worked out on every UniFi read: a client the controller lists whose IP address is exactly one server's own. Replaced as a whole on a read that lists any clients; kept as it was when it lists none.
|
||||
|
||||
| Column | Type | Notes |
|
||||
|---|---|---|
|
||||
| `id` | integer PK | |
|
||||
| `integration_id` | integer NOT NULL → `integrations.id`, **cascade** | Unique together with `server_id` and `client_mac`. |
|
||||
| `server_id` | integer NOT NULL → `servers.id`, **cascade** | |
|
||||
| `device_external_id` | text NOT NULL | The MAC of the switch or access point (`network_devices.external_id`). |
|
||||
| `client_mac` | text NOT NULL | The server's own MAC as the controller sees it. |
|
||||
| `port` | integer | The switch port, where the controller says. |
|
||||
| `wired` | bool NOT NULL | False for a client on Wi-Fi. |
|
||||
| `updated_at` | text NOT NULL | ISO. |
|
||||
|
||||
#### `network_segments`
|
||||
|
||||
The networks (VLANs) and Wi-Fi names of a UniFi controller, replaced as a whole on every read. Passphrases are never stored.
|
||||
|
||||
Reference in new issue
Block a user