In attendance: William Dougherty - NI&S, chair and scribe; Mary Dunker-SETI; Mike Moyer-NI&S; Wanda Baber-NI&S-SMT; Jeff Kidd-CNS; Bill deWindt-Learning Technologies; Karen Herrington-IMS; Kimberley Homer-NI&S; Richard Quintin-ES DBA; Brian Jones-NI&S; Kevin Davis-UCS.
CNS: The expected network maintenance postponed from Thanksgiving will be attempted December 27 and 28, the week of the university closing. Part of that maintenance will require a chassis replacement of a core network device located in the ISB switchroom. During this chassis swap there will be interruptions in Internet connectivity. It is likely that traffic from campus to the datacenter should still flow during this time. whichever day this major chassis upgrade is not done, there will be rolling IOS (OS on Cisco gear) upgrades across core devices located in each of the NI&S switching centers across campus. Each core device contains redundant Supervisor modules that can be upgraded separately while the other maintains switching and routing functions so these rolling upgrades "should" be transparent to most university users. The time period will probably be short, an hour or less. Exact time and which day will be used for each task will be forwarded to the team.
Continuing UC upgrades and network equipment updates will be announced through VT-DNET.
Learning Technologies: LT has the following activities scheduled for the holiday break that is on the horizon--On Monday January 14 from 5:00am until 6:00am we will be moving cabling on LT's internal networks from a legacy Ethernet switch to a new 10Gb/s switch we have installed. This change will mainly impact (and upgrade) our internal management networks and should not affect any production systems. On Tuesday January 15 from 5:00am until 6:00am we will be migrating numerous production links from the same legacy Ethernet switch to the new 10Gb/s switch. Again, this change should not impact any production systems and be completely transparent to end users. On both dates all LT Systems staff will be working in concert on the changes and monitoring systems in the event any one step negatively impacts performance in any way. Should such a situation arise, we will halt the changes and revert to our current configuration so that we can ascertain the source of the problem(s). These changes have already been tested in a dev environment so our confidence is high that they will go smoothly, but we are putting the caveat of "should" on both day's activities since everyone knows that sometimes the best laid plans are the ones that can blow up in your face. If anyone has questions or concerns please let Bill deWindt or Dave Adams know and we will adjust accordingly. Outside of these internal networking changes, LT has nothing else scheduled for December or January.
Facilities: February we are due for another data center generator manual load transfer and I am proposing Sunday, February 10th, starting at 8am, and would be complete in an hour. No one in the room expressed a concern.
SETI: WIndows A.D maintenance will take place. All services, with the exception of the domain controllers--so authentication will work so Exchange will still function. This will be on Saturday, December 22 at 6am til 8am. Hokie SelfService and AD Admin will be down. See IT Critical Dates calendar for further details.
IMS: Provisioning for BEIS (Banner Enterprise Identity Services) is tentatively scheduled for January 10th. No real notice as this will be transparent to most users. Will cue off of employee affiliation.
UCS: Will be closed during Holiday break; Call Center will still be creating tickets, but no call backs. Dec 21 until January 2nd.
Google info: Dates to officially shutdown mail servers associated with legacy service needs to be established and announced. Chair will check with E-mail support team. An e-mail was sent to some group who no longer have proper affiliations, so this should not come as a complete surprise.
SAMSWise calendaring info: Attempt to make subscribing simple and effective. Posting has also been simplified. Posting by host or application, in which case host or hosts will be chosen automatically. This will be somewhat complicated due to the level of complexity of the service offerings we maintain, but this committee is the one charged to ensure accuracy of information. Google calendaring will be used, but API testing is still needed.