RESOLVED: Issue with primary F5 Load Balancer

Starting at 2:13 am on 12/9, the primary F5 load balancer experienced a memory exhaustion condition. This problem appeared to resolve itself at 6:07am. The problem restarted at 12:04 pm. ITS System staff failed over to the standby F5 unit at 1:55 pm and rebooted the primary. This problem would have impacted most load balanced services, including UTLogin, TED, and Doc Repo. At this time, we are running on the standby unit and service appears to be stable. We are continuing to monitor the situation. We will engage vendor support to determine the root cause of this issue.

Latest Update: 2019-01-12 04:02:21 - On New Year's day, we successfully installed a patch on the production F5 load balancers that should address the memory exhaustion issue. The systems have been running well since being patched. We believe this issue is now resolved.