Wireless Networking

The AirBears Network will experience an outage at the locations listed below to facilitate the connection of the existing captive portal devices to the AirBears router that will serve the east half of campus. This will match the configuration in service for other areas of campus.

The outage should only last about 15 minutes at each location listed in the IST announcement.

Resolved as of 2010-10-18 08:00:00

Wireless AP controller at Soda, Cory and Sutardja Dai will be upgraded with the latest code on Aug 12 (Thursday) at 7:30AM-9:00AM. I will reboot 3 Cisco AP controllers. You may experience that the wireless network at Soda, Cory and Sutardja Dai will be up and down for about or less 20 mins. If everything goes ok, the total hours will take less than 1 hour. This upgrade will affect wireless users only. During this time, the wired network will still work.

If you have questions, please contact with networks@eecs

Resolved as of 2010-08-12 08:30:00

Wireless AP controller at BWRC will be upgraded with the latest code on July 28 (Wed) at 7:30AM-8:30AM. I will reboot BWRC Cisco AP controller. You may experience that the wireless network at BWRC will be up and down for about or less 20 mins. If everything goes ok, the total hours will take less than 1 hour. This upgrade will affect wireless users in BWRC only. During this time, the wired network will still work.

If you have questions, please contact with networks@eecs

Resolved as of 2010-07-28 08:00:00

The IST managed captive portal device for the EECS supported AirBears will be replaced at 6:00pm on July, 21, 2010. This is to resolve issues related to the hardware, including the problem that caused an outage earlier today.

Users will not have access to the AirBears network in Cory, Soda, Sutardja Dai, and the parts of Hearst Mining that are supported by EECS wireless devices.

Resolved as of 2010-07-21 18:30:00

The Captive Portal device for the EECS AirBears feed stopped responding at 10:11 a.m. It was restarted and returned to service at about 10:40 a.m. Users may have to re-authenticate to use AirBears again.

Please direct any questions to IST 510-642-8500, Monday – Friday 8:00am – 5:00pm http://ist.berkeley.edu/support/service-desk

Resolved as of 2010-07-21 10:40:00

Wireless AP controllers will be upgraded with the production code on July 20 (Tuesday) at 7:00AM-8:30PM. I will reboot all Cisco AP controllers. I will schedule the wireless network downtime. You may experience that the wireless network will be down for about or less 20 mins for each building during 7:00AM-8:30AM. If everything goes ok, the total hours will take less than 1.5 hours. This upgrade will affect wireless users in Soda, Cory,Citris and BWRC. During this time, the wired network will still work.

If you have questions, please contact with networks@eecs

Resolved as of 2010-07-20 08:01:00

Cory Wireless AP controller will be upgraded with the newer version of firmware on May 27(Thursday) at 8:00AM.

I will reboot Cory AP controller. I will schedule the wireless network downtime for about 20 mins. You may experience that the wireless network will be down for about or less 20 mins during 8:00AM-8:20AM. This upgrade will not affect wireless users in Soda, Citris or BWRC. During this time, the wired network will still work.

If you have questions, please contact with networks@eecs

Resolved as of 2010-05-27 08:20:00

There will be a brief interruption to
wireless network service at BWRC
Wednesday May 26, 2010 at 8:15 am
when we change the dhcp server associated
with the WLANs
[Read more…] about Brief wireless interruption at BWRC

A wireless AP controller in Sutardja-Dai Hall will be upgraded with the newer version of firmware on May 26(Wed) at 8:00AM.

I will reboot Sutardja-Dai Hall AP controller. I will schedule the wireless network downtime for about 20 mins. You may experience that the wireless network will be down for about 20 mins during 8:00AM-8:20AM. This upgrade will not affect wireless users in Cory,Soda or BWRC. During this time, the wired network will still work.

If you have questions, please contact with networks@eecs

Resolved as of 2010-05-26 08:12:00