{"id":5020,"date":"2025-01-26T21:52:24","date_gmt":"2025-01-27T05:52:24","guid":{"rendered":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/?p=5020"},"modified":"2025-01-26T21:55:02","modified_gmt":"2025-01-27T05:55:02","slug":"campus-network-outage-summary-friday-january-24","status":"publish","type":"post","link":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/2025\/01\/26\/campus-network-outage-summary-friday-january-24\/","title":{"rendered":"Campus Network Outage Summary – Friday, January 24"},"content":{"rendered":"
\n
\n
\n
\n\n\n<\/colgroup>\n\n\n\n\n\n
\n

\"This<\/span><\/span><\/a><\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n

Dear members of the Puget Sound community,<\/span><\/p>\n

<\/p>\n

Technology Services (TS) has resolved the following incident. Details on the issue are available below:<\/span><\/p>\n

<\/p>\n

Puget Sound Network: Campus Network Outage<\/span><\/p>\n

Friday, January 24 | 3:13 p.m. – 10:30 p.m.<\/span><\/p>\n

<\/p>\n

Outage Summary:<\/span>
<\/span>On Friday, January 24th, at 3:13 p.m., Technology Services observed a campus-wide network outage. Due to the scale of the outage and the campus community's inability to communicate via Zoom or email, our Emergency Response Group elected to issue an Everbridge alert to notify the campus. The team undertook several remedial actions to restore network connectivity, and a follow-up Everbridge alert was issued at approximately 5:15 p.m., indicating the outage had been resolved. Unfortunately, at around 5:50 p.m., the team observed a recurrence of the same network behavior seen during the initial outage. At this point, the campus network became unavailable again.<\/span><\/p>\n

Following a thorough review of event logs and identifying a viable remediation method, our network engineers, with the support of Juniper, implemented a configuration change to the core and distribution layers of the network. This action stabilized and restored connectivity at approximately 9:30 p.m. We apologize for the disruption caused by this outage and appreciate your understanding as we worked to restore services.<\/span><\/p>\n

Technical Details:<\/span>
<\/span>During the initial onset of the outage, our engineers reviewed network traffic patterns and identified what appeared to be a network loop causing the outage. A network loop, in its simplest form, occurs when data travels in a continuous circle without any mechanism to stop it. This can happen if a data port is connected to another port within the same network, creating an infinite data loop, or if a configuration change inadvertently causes traffic to route in a circular path. While protocols like Spanning Tree Protocol (STP) exist to prevent loops from disrupting an entire network, loops can sometimes originate in areas where STP is not applicable.<\/span><\/p>\n

The team conducted a comprehensive review of all changes made in the two weeks prior to the incident to determine if any recent network modifications had caused the outage. We are confident that no changes performed by our team were responsible. Additionally, we found no evidence of a cyber event contributing to the outage.<\/span><\/u><\/b><\/p>\n

Unfortunately, a series of factors led the team to a false positive regarding the root cause of the outage. During the event, our logging system was overwhelmed with excessive and unnecessary details, which obscured the underlying issue and made it difficult to diagnose the cause. The campus network's routing fabric uses Border Gateway Protocol (BGP) to determine the best paths for data to travel. BGP relies on a supplementary protocol, Bidirectional Forwarding Detection (BFD), to detect routing failures. Upon further analysis of the logs, we discovered an unknown issue causing BFD to continuously reset routing across the campus network, rendering it virtually impossible for devices to communicate.<\/span><\/p>\n

After consulting with Juniper support, our team confirmed it was safe to disable BFD temporarily to restore network connectivity. Once this configuration change was made, network traffic stabilized immediately, and services were restored. Additionally, packet captures of the network have been obtained to further analyze the outage and identify the root cause of the BFD resets. Once a fix has been identified, we will implement the necessary adjustments and re-enable BFD during the next available routine change window.<\/span><\/p>\n

Our teams continued to work through the weekend to address residual disruptions caused by the outage and ensure the stability of our data center operations.<\/span><\/p>\n

For more information on Technology Services' Incident Communication Plan or to view a list of our Critical Systems and definitions, please visit our <\/span>Service Announcements<\/span><\/a> page on the Puget Sound website.<\/span><\/p>\n

<\/p>\n

If you have any questions or concerns, please don't hesitate to contact the TS Service Desk.\u00a0<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

TS Service Desk<\/span><\/p>\n

Walk-In Support: Tech Center in Collins Library<\/span><\/p>\n

Phone Support: (253) 879-8585<\/span><\/p>\n

Online Help:<\/span> <\/span>support.pugetsound.edu<\/span><\/a>\u00a0<\/span><\/p>\n

Email Support: <\/span>servicedesk@pugetsound.edu<\/a><\/span><\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div><\/div>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

Dear members of the Puget Sound community, Technology Services (TS) has resolved the following incident. Details on the issue are available below: Puget Sound Network: Campus Network Outage Friday, January 24 | 3:13 p.m. – 10:30 p.m. Outage Summary:On Friday, … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":653,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-5020","post","type-post","status-publish","format-standard","hentry","category-announcements"],"_links":{"self":[{"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/posts\/5020","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/users\/653"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/comments?post=5020"}],"version-history":[{"count":0,"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/posts\/5020\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/media?parent=5020"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/categories?post=5020"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/tsmaintenance\/wp-json\/wp\/v2\/tags?post=5020"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}