The controllers recovered and APs automatically rejoined; all APs should be back online now.
We are investigating the cause of the crash and any possible steps we can take to prevent this from occurring again.
Resolved as of 2017-01-18 16:31:00
Instructional & Research Information Systems
Resolved as of 2017-01-18 16:31:00
Overnight between Wed. 1/11 and Thurs. 1/12 we will be transitioning EECS-Secure to a new authentication backend. The old servers, etips1.eecs.berkeley.edu and nps-0.eecs.berkeley.edu will be retired and replaced with a new cluster which will identify itself as clearpass.eecs.berkeley.edu. There will be no interruption to wireless connectivity during the transition.
EECS-Secure will continue to function as it has, but your computer may notice the change in server certificates and prompt you about it. We are listing some steps below that may be helpful if you have trouble connecting on Thursday morning, and remember that you will be able to use other networks (e.g. AirBears2, CalVisitor) to visit this page and the EECS-Secure FAQ.
Windows 10:
* “Continue connecting? If you expect to find EECS-Secure in this location, go ahead and connect.”
* You can click “Connect”, but first we recommend clicking “Show certificate details” and verifying the thumbprint against the Server Certificate at the EECS-Secure FAQ link below.
Mac OS:
* “Before authenticating to the server ‘clearpass.eecs.berkeley.edu’, you should examine the server’s certificate to ensure that it is appropriate for this network.”
* Verify that the server name is “clearpass.eecs.berkeley.edu” and click “Show Certificate” to confirm that the certificate is valid; then click “Continue” to connect.
Linux:
* We have seen many different behaviors depending on distro and version. If you have trouble, we recommend deleting the saved network and reconnecting, making sure to check the authentication details in the EECS-Secure FAQ, which is linked below.
If the above aren’t helpful to you, you might try following the Linux advice by deleting your saved EECS-Secure and reconnecting from scratch. In any case, if you have trouble, please visit the helpdesk in 395 Cory Hall.
More information about EECS-Secure authentication, including configuration details, certificates, and certificate fingerprints can be found on the EECS-Secure FAQ:
https://iris.eecs.berkeley.edu/15-faq/21-network/eecs-secure.html
This change ONLY applies to EECS-Secure and will not affect any other networks, such as EECS-PSK, AirBears2, etc.
If you have been using EECS-RADtest to help us test the new servers, that network is no longer available and we strongly recommend you remove the saved network from your machine.
As a reminder, mobile devices are not fully supported on EECS-Secure. Depending on device and OS version, you may be able to connect, but we can provide only limited support. If you can’t connect to EECS-Secure, we recommend using CalVisitor, or EECS-PSK if you require EECS network access.
If you have any questions or problems, you may visit the helpdesk at 395 Cory Hall or help@eecs.berkeley.edu.
We will have a full system shutdown on Thursday, December 22nd at 7:30 AM to perform necessary fire and emergency power testing in our server rooms. The entire EECS network and all hosted resources will be offline during this maintenance.
This will affect networking in the following locations:
Wired and wireless networks offline:
* Soda Hall
* Cory Hall
* Sutardja Dai Hall
* Jacobs Hall
* BWRC
Wireless networks offline, wired remains online:
* Blum Hall
* Calvin Lab
Hosted resources such as the EECS website, file servers, etc. will be offline and globally inaccessible.
The facilities maintenance window is scheduled from 7:30 AM to 1 PM, but we anticipate the network and critical services should be back by 11AM if all goes well.
The intent is to perform these tests annually going forward; however we will learn from this year’s procedure and aim to keep more critical services online in the future.
If you have any questions about this maintenance, please contact help@eecs.berkeley.edu.
[Read more…] about EECS Full Network and Service Outage, Thurs. 12/22/16 7:30AM
We have just experienced an outage of a main switch which serves wired and wireless on the 2nd, 3rd, and 4th floors of SDH. Network staff are investigating and will repair ASAP.
[Read more…] about Network Outage, SDH 2-4th floors, 10/27/16
The wired network in the 165 Cory server room will be offline from 8-10AM while switches are physically relocated.
All department services have redundant copies elsewhere and will not be affected. Private systems within 165 Cory will not have network connectivity.
Please contact help@eecs.berkeley.edu if you have any questions or concerns about this maintenance.
[Read more…] about 165 Cory Network Outage, 10/21/16
The wireless network on half of the fifth floor of Soda Hall has been offline since yesterday morning. Trouble reports were received this morning and we are currently working to resolve the issue.
[Read more…] about Soda 5th Floor Wireless Outage, 10/17-18
Resolved as of 2016-09-22 09:48:00
We will be reconfiguring one of the transit links out of Cory Hall tonight at 5PM. There will be no general network or service outages, but some services will have a brief interruption in connectivity:
* Private networks which transit between Cory and Soda Halls (TIER, CEC, Viper)
* Machines in Cory Hall on the 169.229.59.0/26 and 128.32.38.0/23 networks (not including EECS-PSK wireless clients)
* The primary departmental WINS (Windows Name Service) server, but the secondary will remain online
[Read more…] about Cory Hall Network Maintenance, 9/15/16
We will be performing an emergency reboot of the switch which provides service to the third/fourth floors of the Sutardja Dai Nanolab at 12:15 PM today, in order to clear some bad state left over from this weekend’s upgrades. The third and fourth floors of the Nanolab will be without network connectivity for approximately five minutes.
[Read more…] about Emergency Reboot, Nanolab 3/4 Switch 8/22/16
At the suggestion of our vendor, we will be upgrading various access switches to the latest supported software version. This will affect wired and wireless clients in Soda, Cory, and Sutardja Dai Halls, and wireless users in Blum Hall.
The first set of these upgrades will take place Saturday night at 10PM and will occur in waves. We are upgrading sixteen switches in four waves and expect to be done by 11:30.
The second will take place on Sunday night at 10PM, will affect a smaller group of switches, and should be done by 10:30.
Brief network interruptions (on the order of five minutes) are expected for users in these locations while switches reboot. Most locations will experience a single interruption, but some will require two. Where possible, we will stagger reboots in an attempt to maintain Wi-Fi coverage.
[Read more…] about Access Switch Upgrades, Sat-Sun 8/20-21