Header Search Widget

IRIS

Instructional & Research Information Systems

Disable SMBv1 on Windows systems

by

Due to critical vulnerabilities in Windows SMB (file sharing) services, the
campus Information Security & Policy (ISP) group advises
disabling of SMBv1 on all campus Windows systems, and that you prepare to update
all Windows systems quickly on Patch Tuesday (Feb 14) to patch more
recent versions of SMB (SMBv2 and SMBv3).

Please see our FAQ page for some details on disabling SMBv1.

Wireless Controller Upgrade, Jan. 26 2017

by

We will be performing an emergency upgrade of our wireless controllers tonight beginning at 9:30PM to address a bug which has been causing periodic controller crashes that bring down the wireless network. The last outage generated by this bug was on Jan. 18, but we also experience more frequent crashes that do not affect production due to redundancy.

The controllers have the capability for a hitless upgrade (upgrade without affecting service), however we have had mixed experience with this feature in the past. We expect there may be an outage of 10-15 minutes while the controllers reload after the upgrade.

This maintenance will affect wireless networks in Soda, Cory, Sutardja Dai, Blum, and Jacobs Halls, as well as the Calvin Lab, BWRC, and BiD Lab in HMMB.

Please direct any questions about the upgrade to help@eecs.berkeley.edu.
[Read more…] about Wireless Controller Upgrade, Jan. 26 2017

LDAP issue affected IRIS website and other services

by

A network problem with one of our LDAP load balancers caused some intermittent problems with some Departmental services. This probably started overnight when a server was patched and restarted. This morning we had reports of intermittent problems with Repo, and the IRIS roster and network applications on iris.eecs. The problem has been identified and resolved for now. Around 12:10pm we had to restart the server that hosts the iris.eecs website and the Department jabber server, but all services are operational again at this time.

Resolved as of 2017-01-20 12:10:00

Brief Wireless Network outage

by

All wireless networks were unavailable for approximately 12-15 minutes due to a simultaneous crash of our primary and backup wireless controllers.

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

Changes to EECS-Secure, Thurs Jan. 12th

by

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.