360 likes | 372 Views
This briefing provides updates on the reorganization of the Academic and Administrative Information Technology (AAIT) division, including the introduction of new team names and major changes within the Client Technology Services (CTS) unit. The announcement also includes a status report on wireless infrastructure and the upcoming implementation of Emory's next-generation core.
E N D
IT Briefing Agenda 11/17/05 • Foundation Issues & Governance • Quick Updates • AAIT CTS Organization • ACM Demonstration • VPN Announcement • Wireless & Core update • Rich Mendola • Karen Jenkins • John Ellis • John Ellis • Jay Flanagan • Paul Petersen
General Updates Karen Jenkins
Quick Updates • TechTalks - Announcement • New IT Forums to solicit input on current and future services/technology • Schedule meetings based on demand and interest • Send email to CTS-CI@listserv.cc.emory.edu to request a topic • Meetings and topics will be posted on it.emory.edu, meeting maker, and sent to local-l • MS Campus Agreement - Update
New AAIT Customer Facing Organization John Ellis
AAIT Re-Organization AAIT = Academic and Administrative Information Technology (Formerly known as ITD)
Objective • Reorganize the AAIT division to: • Improve service by increasing transparency to our customers and partners. • Become more agile in response to University strategic direction. • Respond more openly to synergy with potential partners.
New Team Names • Academic Technology Services (ATS) • Administrative & Data Services (ADS) • Client Technology Services (CTS) • Operational & Infrastructure Services (OIS) • Finance & Administration Services (OFA)
Major Changes? • New Unit: Client Technology Services (CTS) • Purpose: Focus on the Client and end-user experience • Customer relationship management • Customer facing technologies • Responsible for systems: • Email • Identity management and security • Desktop support • Websites & communications
Major Changes? (cont.) • New teams within Client Technology Services (CTS) for: • Identity Management • Email • Web & Communications • Consolidate all desktop support within CTS • Consolidate all systems support within Operations (OIS)
Major Changes? (cont.) • HelpDesk moves to Operations (OIS) • Split application administration functions from systems administration and support • Consolidate all enterprise data support within Applications; DBA’s move to ADS • Academic (ATS) teams aligned with management and lead positions
New Positions to be posted • New lead position in ADS for Enterprise Data Technical Lead • New lead position in OIS for Systems Support Technical Lead • Lead Storage Engineer • System Administrator positions
VPN Announcement Jay Flanagan
A Status Report for Wireless and the New CoreNovember 17, 2005
Agenda • Wireless at Emory • Status at Start of School • The ResNet Project • Current Usage • EmoryUnpulgged Released • Wireless Futures • Emory’s Next Generation Core • Current State • Design • Virtual Routing • Mesh versus Cube • 1 gig versus 10 gig • Implementation Timeline
Wireless: Start of School • September 2005 • 271 Access Points (all Aruba) • Full or Partial Coverage in over 20 Buildings • 3 Outdoor Areas Covered • Although coverage around campus was significant, the only Residence Hall with wireless was Woodruff…
Wireless: The ResNet Project • In September AAIT, Housing, and NetCom, led by Rich put together a project to install wireless in all of the Residence Halls. • Lowered costs: • $1,175 per Install (was $1,250) • $54 per month (was $72) • ResNet Project Specifics: • More than 50 Buildings • Projected almost 500 APs • Roughly $700,000 • Deadline: January - Start of Spring Semester
Wireless: ResNet Project Status • Completed Buildings: • Alabama, Dobbs, Gilbert, Hopkins, Longstreet, McTyeire, Means, Oxford, Smith, Thomas, Thomson, & Trimble • 395 Access Points (up from 271) • Remaining Buildings: • Clairmont (A,B,C,D,E,F,G,H & Tower), Clifton Tower, Fraternity Row, Harris, Turman Complex, & Turner Village • An additional 200+ APs to go
Wireless: Current Usage -Associations Blue Represents Total Associations
Wireless: Current Usage - Clients Total Number of Authenticated Wireless Users
Wireless: EmoryUnplugged – Released • Wireless Guest Access: • Unauthenticated and unencrypted wireless access for guests • Limited to Web, Secure Web, and VPN • WPA – Wi-Fi Protected Access: • User-friendly way to connect • Stronger Encryption
Wireless: EmoryUnplugged – Released • Spreading the Word… • Wheel Article, Emory Report Article • Website Improvements • http://it.emory.edu/wireless • EmoryUnplugged Events • 3 at Cox Hall Media Center • First Event Tomorrow for Local Support • 2 to 4 PM – Bring your laptop • 1 at Clairmont Campus (Week of 1/20)
Wireless Futures • Expanding Wireless Coverage • Emory, Crawford Long, & Wesley Woods Hospitals • Will support EeMR & Patient/Guest Access • Emory College (> 25 Buildings) • Others… • Wireless VoIP • The Remote AP • The Mobile Office
NexGen Core - Design • Virtual Routers • In the current model there are separate physical routers for each core with in the same switching center • Virtual Routers allow for each core to be contained within the same physical router • Advantages • Less Routers (less power and space) • Greater scalability
NexGen Core - Design • Mesh versus Cube • Mesh Advantages • Each router is only one hop away from any other router • Ultimate in redundancy • Mesh Disadvantage • Too many fiber paths and fiber ports
NexGen Core - Design • Cube Design • Each router is connected to a subset of the other core routers in such a way that an outage with any fiber path or switch center would not cause an outage. • Conserves on fiber paths and ports
NexGen Core - Design • 1 Gig vs. 10 Gig • Even with a cube design it would use an excessive amount of ports and fiber to duplicate the cube for each core. • With 10 Gig links we can setup the cube and virtually partition one gig links for each core. • Each core will be at each switching center • We will be able to burst into the unused bandwidth
NexGen Core – Implementation • The Routers are being installed now • The new router cube should be built before next semester • A transition plan for migrating links to the new core is being developed. • Deadline – end of the fiscal year