fix incorrect ips for switches in IPAM

documentation/INCIDENTS.md

@@ -120,3 +120,17 @@ I ran ansible with `--fork=1` to update on ap at a time (every ap takes about 5
 **impact**:
 Either clients "roamed" (no fast roaming - short interuptions) to a different ap or waited till the original ap came back online.
 For every client not more than 10-15 seconds service interruption.
+
+
+2022.07.17 01:50 | (maintenance) increase dhcp pool size for clients
+--------------------------------------------------------------------
+
+The dnsmasq instance for the client network (`10.84.4.0/22`) only used the dhcp pool `10.84.4.100 - .250`.
+
+To be able to actually assign the full `/22` to clients I've changed the pool to `10.84.4.2 - 10.84.7.254`.
+
+Afterwards I've reloaded `dnsmasq` on `gw-core01`.
+
+**impact**: none
+
+Currently `dnsmasq` has handed out 104 leases, so we presumably never ran out of ips in the old pool.

documentation/OVERVIEW.md

@@ -12,8 +12,8 @@ IPAM / Device Overview:
 | Name           | Location  | MGMT IPv4    | MAC                 | Device               | Notes |
 | -------------- | --------- | ------------ | ------------------- | -------------------- | ----- |
 | `gw-core01`    | Büro      | `10.84.1.1`  | `78:8a:20:bd:b6:ae` | Ubiquiti EdgeRouterX |       |
-| `sw-access01`  | Büro      | `10.84.1.10` | `bc:cf:4f:e3:bb:8d` | Zyxel GS1800-8HP     |       |
-| `sw-access02`  | Zelt 5    | `10.84.1.11` | `bc:cf:4f:e3:ac:39` | Zyxel GS1800-8HP     |       |
+| `sw-access01`  | Büro      | `10.84.1.11` | `bc:cf:4f:e3:bb:8d` | Zyxel GS1800-8HP     |       |
+| `sw-access02`  | Zelt 5    | `10.84.1.12` | `bc:cf:4f:e3:ac:39` | Zyxel GS1800-8HP     |       |
 | `hyper01`      | Büro      | `10.84.1.21` | `00:23:24:54:f0:fe` | Lenovo ThinkCentre ? |       |
 | `monitoring01` | `hyper01` | `10.84.1.51` | `16:b9:13:c3:10:5e` | Proxmox VM           |       |
 | `ap-2bbf`      | Zelt 4    | `10.84.1.30` | `24:de:c6:cc:2b:bf` | Aruba AP-105         |       |