Difference between revisions of "Scheduled ECE network outage (February 16, 2018)"

From ECE Information Technology Services
Jump to navigationJump to search
(Outage over.)
 
Line 21: Line 21:
  
 
The operation was successful.  All networks and services should be operating normally now; please [[How To Report A Problem|report any problems you may encounter]].
 
The operation was successful.  All networks and services should be operating normally now; please [[How To Report A Problem|report any problems you may encounter]].
 +
 +
 +
==Update 2018-02-19 16:30==
 +
 +
Users on several subnets (RCL, COSE, POEM, and others) have reported problems with their network connection, specifically with acquiring an IP address via DHCP.  We have found a likely cause, and are now working to implement a fix.

Latest revision as of 16:37, 19 February 2018

UBC IT will be performing a network configuration change on Friday February 16, 2018, from 20:00 to 22:00. This work is needed to remove some network equipment that has become obsolete.

During this time, the following services are expected to be unavailable:

  • Wired, wireless, and VPN networks in ECE
  • Most ECE servers (including DNS and LDAP)
  • Most ECE websites (including www.ece.ubc.ca)
  • ECE home directories (through NFS or CIFS)

ECE mail service (sending mail through SMTP, receiving mail through IMAP, and webmail) will also be unavailable. Incoming mail will be queued, and delivery will resume afterwards.

Because NFS home directories will be unavailable, we recommend that users log out from accounts that directly use ECE home directories (including Linux workstations and ssh.ece.ubc.ca).

Thank you for your understanding and cooperation.

Derek Poon
UBC IT Services @ ECE


Update 2018-02-16 20:50

The operation was successful. All networks and services should be operating normally now; please report any problems you may encounter.


Update 2018-02-19 16:30

Users on several subnets (RCL, COSE, POEM, and others) have reported problems with their network connection, specifically with acquiring an IP address via DHCP. We have found a likely cause, and are now working to implement a fix.