As of about 9:45 PM, production services were externally available, and internal building networking came online during the next few hours. As of 1:30 AM we have restored service to all locations except a small handful, which currently include BWRC and Blum Hall. We will be making use of tomorrow’s scheduled contingency maintenance period to fully restore all services in all locations.
At this time we have begun to restore production services, but there are still a number of connections to be made. We’re continuing to work and hope to have service restored as soon as possible.
Due to unforeseen complexities, we are extending our maintenance window. We currently expect production services to be externally reachable by 10PM, with internal network service possibly taking longer. Updates will be posted as they are available.
We apologize for the trouble, and hope that it doesn’t stop you from enjoying what’s left of the holiday season.
There is a full maintenance outage of the EECS network scheduled for today from 10AM – 8PM. During this window, the entire EECS network will be offline as we transition to our new routing core.
Expected service impacts:
- Internet connectivity will be unavailable on all EECS networks
- All EECS Wired* networking will be offline or unreliable
- All EECS Wireless** networks will be unavailable (the networks will continue to be visible in some locations, however the underlying transit networks will be offline)
- The BWRC will be isolated from EECS and unable to access the Internet or non-BWRC-hosted resources
- EECS hosted services (such as NFS project space and home directories) will be unavailable
We apologize for any inconvenience that this maintenance will cause, but are excited for the improved service opportunities that the new network will bring us.
*EECS Wired locations include Soda, Cory, and Sutardja Dai Halls, and the BWRC
**EECS Wireless locations include Soda, Cory, Sutardja Dai, Calvin, and Blum Halls, as well as the Sibley Auditorium, certain areas of the Hearst Memorial Mining Building, and the BWRC
This is a reminder about the pair of scheduled outages we will be experiencing this weekend.
On Saturday, January 3rd, we will be performing a system-wide network upgrade which will render all EECS locations and services offline for most of the day. This is to install and cut over to our new core routing infrastructure. More information, including full details, can be found in this IRIS News post. Updates during the outage will be posted to this blog, and IRIS News will be configured to redirect here.
On Sunday, January 4th, there will be a full-building power outage for Soda Hall, in order to perform preparatory electrical work for the Jacobs Hall construction project. Backup power will be supplied to the computer machine rooms in 288, 290, and 420A Soda Hall, in order to provide continuity for core EECS departmental and research resources. Soda Hall will be closed and otherwise dark for most of the day. More information, including full details, can be found in this IRIS News post. Updates during the outage will be posted to this blog, and IRIS News will be configured to redirect here.
Welcome to the externally hosted EECS/IRIS Systems Status blog, which is intended to complement our internal IRIS News app found at https://iris.eecs.berkeley.edu. While the majority of service updates will be posted to IRIS News (which also has the capability to send out notices to various e-mail distribution lists), large-scale maintenance and outage updates will be posted here. This blog is hosted on IST’s Pantheon platform, which gives us the ability to post updates even when EECS’ internal infrastructure is down or severely affected by a scheduled or unscheduled outage.
Before any scheduled outage which will affect IRIS News, we will be sure to post and send out a link to this site to help the community stay informed about the current status of EECS services. In the event of unscheduled outages, we may not have the opportunity to update IRIS News, so it would be a good idea to bookmark this site as well.
Derek, on behalf of IDSG