9
edits
Changes
Incident Report: 20230109 (view source)
Revision as of 16:43, 10 January 2023
, 16:43, 10 January 2023some more stuff
== Lessons Learned ==
== Lessons Learned ==
* We need to be more happy to assume, if we haven't touched the network and something's happened, it could be an ITS issue. Look at things like traceroutes earlier.
* ITS don't really know about us - like they'd have just assumed uryfw0 is just 144.32.109.64 and not a gateway for all of 144.32.64.160/27, so be happy to remind them of this.
* Phone ITS earlier if it's a big problem.
* Don't get distracted by things that are merely the result of the problem - i.e. our DNS is often external to URY (i.e. wogan or ITS nameservers), so it can't resolve DNS. But it doesn't mean the key problem is DNS - the key problem is that no traffic reached us. What didn't help was the confusion about guest PC being able to access the internet - this is because it has a web proxy (because IRN).
[[Category:Incident Reports]]
[[Category:Incident Reports]]