incident - 2022.07.23: power outage in tent 5
This commit is contained in:
parent
51449a9801
commit
5728762dbe
|
@ -134,3 +134,16 @@ Afterwards I've reloaded `dnsmasq` on `gw-core01`.
|
||||||
**impact**: none
|
**impact**: none
|
||||||
|
|
||||||
Currently `dnsmasq` has handed out 104 leases, so we presumably never ran out of ips in the old pool.
|
Currently `dnsmasq` has handed out 104 leases, so we presumably never ran out of ips in the old pool.
|
||||||
|
|
||||||
|
|
||||||
|
2022.07.23 07:40 - 12:50 | power outage in tent 5
|
||||||
|
-------------------------------------------------
|
||||||
|
|
||||||
|
There was a power outage in tent 5 taking down `sw-access02` and therefore also `ap-1a38` (tent 5) and `ap-2bbf` (tent 4).
|
||||||
|
|
||||||
|
**impact**: no accesspoints and therefore no wifi in tent 4 and 5. Maybe some clients roamed to a different tent.
|
||||||
|
|
||||||
|
**problems accessing the equipment**:
|
||||||
|
Currently every visit from Freifunkas need to be coordinated with the object management of the facility.
|
||||||
|
This is fine for sheduled maintenances but not doeable for incident response and often leads to discussions and unaccessible equipment (which is totally understandable).
|
||||||
|
Maybe we can "whitelist" certain people at the facility so they can always access the equipment without further authorization.
|
||||||
|
|
Reference in New Issue