Infrastructure Development and Services Group
Computing Users Support Group
Joint Annual Report
1999-2000
Hua-Pei Chen
CRM, EECS Dept.
July 7th, 2000 

•	IDSG Accomplishments in 1999-2000
•	Network

i.	Cory Hall upgraded from ATM to Gigabit backbone/switched Ethernet.
ii.	Deployed gigabit link between Cory and Soda Halls.
iii.	Deployed gigabit backbone for both Cory and Soda Halls.
iv.	Deployed 4 new switched subnets in Cory and Soda Halls.
v.	Deployed test subnets for Instructional and research groups.
vi.	Finished Tier 2 connection to UCB CNS with dual 100Mb load-balancing links.
vii.	Working with CNS to phase out obsolete CNS routers in Soda Hall.

•	Institutional Infrastructure

i.	Assumed overall networking, wiring, and DNS management for all EECS.
ii.	Deployed DHCP services throughout EECS by adding 6 additional DHCP servers, enhanced monitoring and tracking of unauthorized uses.
iii.	Simplified user account management process, accounts are created within 24 hours.
iv.	Merged EECS users into one uniform user domain for both UNIX and NT.
v.	Consolidated many Cory NT domains and NT services, while making them redundant.
vi.	Deployed an LDAP based user information database by merging information from other traditional sources such as roster database, UID, NIS, etc.  This information is configurable by users thru secure web accesses.
vii.	Deployed cross-platform 1.5TB capacity, highly available and redundant RAID storage server Network Appliances with native NFS and NTFS support, snapshot for quick file restorations, and on-the-fly configuration management.  This has been deployed as a central home directory server, as well as project space server.  Current capacity at 450GB.  Reduced the dependency on SAMBA.
viii.	Upgraded all existing infrastructure servers (DNS, EECS/CS mail gateways and relays, NIS master and slave servers, etc.)

•	Applications and Services

i.	Deployed SSL based secure IMAP service, this allows users to access email anywhere, platform independently.  Currently this has a user base at 350 count.
ii.	Deployed EECS Calendaring server, including conference room scheduling and viewing over the WWW, as well as SSL-based secure personal WEB calendaring access.  Currently this has a user base of 150.
iii.	Deployed Solaris 7 (64-bit) Sparc and x86, and Linux SWWs.
iv.	Upgraded NTSWW to new clustering server, redesign and updated NTSWW web pages and info.
v.	Deployed IDSG web site.
vi.	Deployed forms for requesting or searching thru IDSG services, with appropriate notifications sent to PI/requestors/Gas for charging purposes, if applicable.
vii.	Deployed an EECS Certificate Authority server.
viii.	All IDSG monthly recharge reports are available and searchable on secure web site for authorized users in EECS.

•	Security

i.	Standardize and enforce the “no clear-text password” policy.  Instituted a secure password update server, work with other support groups and staff to implement SSH, Kerberos, or SecureCRT accesses only.
ii.	Restricted EECS Mail relay service to reduce SPAM.  Set up EECS external mail relay server with authentication control.
iii.	Instituted the policy to require pre-registered MAC address for all DNS accesses.  Actively monitoring un-authorized accesses, both for DHCP and fixed IP.
iv.	Set up SSL-based email and calendaring accesses, actively switching users away from clear-text based POP services.
v.	Set up EECS authenticated user only internal WEB resources.
vi.	Take an active role in monitoring the network and system security on the EECS network, coordinating with UCB security officers and internal support groups.  Publish monthly security incidents reports.  Make all patches available for users in EECS in a timely and organized manner.

•	Staffing

i.	Hired an IDSG group lead in September of 1999.
ii.	Instituted an EECS wide security officer for computing and networking security.
iii.	Hired a PAII and reclassed this staff to a PAIII level for EECS NT infrastructure.
iv.	Merged the networking staff into IDSG.

•	
IDSG Proposed 3-Year Infrastructure Plan
•	Institutional Infrastructure
i.	Upgrade and integrate two EECS web servers.  Deploy EECS internal secure web services for authenticated users, including proxy service.
ii.	Upgrade and migrate EECS NT4 infrastructure to NT2000 environment.
iii.	Deploy EECS wireless DHCP based LAN.
iv.	Upgrade obsolete core EECS routers.
v.	Deploy PKI based EECS certificate authority server
vi.	Upgrade existing file servers with cross-platform (UNIX and NT) support.
vii.	Increase the capacity of existing production application services (IMAP/Calendar, etc.).
viii.	Upgrade or replace existing NT/UNIX gateway service (SAMBA) with other state-of-art alternatives (Cascade).
ix.	Streamline and automate user account management.
x.	Deploy EECS user email virus-checking service.
xi.	Deploy EECS networking monitoring facility for networking and system security detection.
xii.	Deploy new data-warehouse to replace existing roster and other user information databases.
•	Application
i.	Deploy EECS user roaming service.
ii.	Deploy NT2000 NTSWW and NT2000 desktop install servers.
iii.	Deploy EECS Web Proxy service.
•	General Support
i.	Deploy EECS uniform user support helpdesk.
ii.	Deploy EECS computing and networking extended hour support.
•	Data Recovery and Archival Service
i.	Deploy brand new dual UltraSparc based 4-drive AIT2 120-tape jukebox with native backup capacity of up to 6TB.
ii.	Offer cloning and monthly off-site storage of EECS research data.
iii.	Offer bi-monthly data archival and offsite storage service for up to 5 years at no extra charge.
•	
CUSG Accomplishments in 1999-2000
CUSG’s work can be summarized in the following categories:
•	Contracted Support

i.	Focused on full service system administration and user support contract.
ii.	Published service level agreement and recommended guidelines for hardware and software support.
iii.	Deployed a brand-new job request and tracking front-end with user-friendly web submission and progress viewing, user and staff notifications, escalations, and monthly ad-hoc billing generations.  This has greatly simplified the need to keep detailed personal tracking, avoid confusion with customers, and gives the staff and the management the tools to track trends and staffing needs.
iv.	Deployed a back-end relational database to track all contract types, pricing, and information.  This has greatly facilitated the support staff in getting pertinent background info in order to provide the correct support to users.  The other benefit is that this database is designed to automatically generate billing journals correctly and efficiently, which is a great improvement over the error-prone manual generation of billing statements before.

•	Recharge Process

i.	Re-establish better communications with the grant administrators, this is done by providing information sessions to the GA, providing user-friendly and timely statements to GA for their approval before submitting to the journals, as well as getting them involved in processes that required verifications of charges.
ii.	A secure web site, accessible only by the authorized grant administrators, has been set up so that previews of the billing statements can be done.
iii.	Billing statements have been generated on a quarterly basis for reviews.  T&M recharges reports now include links to a certain job requests and can be viewed on line.
iv.	Work to further update our back-end contract database has begun.

•	Staffing

i.	Reallocated staffing distribution based the detailed analysis of the EECS research computing requirements.  This process has made the support organization more effective and efficient.
ii.	Properly trained existing staff in new technologies, such NT advanced desktop and server support, IMAP/Calendar applications, etc.
iii.	Reclassified J. Jed to a PAIII.
iv.	CUSG’s administrative assistant, G. Spears, resigned in March.  TAP staff has been brought in to help out in the interim.
v.	Hired students for more back-end support tasks.
vi.	Instituted an EECS HELP phone (2-7777).
vii.	Revamped the job request process so that it is a tool for job tracking, job escalations, and trend analysis, as well as providing real-time detailed report over the web, both for billing purpose as well as progress status.

•	CUSG Goals for 2000-2001
•	Continue improving back-end processes and the quality of the data

i.	An ERL server is housing the existing Access-based database, with very limited CUSG staff access.  We intend to migrate the database over to another relational database housed in a local server, and allow CUSG staff more access.  We also need to improve the quality of the data entered, allowing more flexibility in querying and report generation.
ii.	CUSG needs to continue updating the information we currently have.  Especially in the areas of our pass-thru hardware service contract with external vendor.
iii.	CUSG need to provide more data linking between various CUSG databases, as well as other EECS databases, such as existing LDAP and roster databases.

•	Billing process

i.	CUSG intends to provide monthly billing statements and have them accessible thru the secure web site by the beginning of next month.  This will give the reviewers more time to go over the statements, allow more time for adjustments, if any, so that the charges are accurate.
ii.	CUSG will cut down and phase out remaining cost centers, such as client backups, hidden staff recharges, etc.
iii.	CUSG will do the best to keep grant administrators, faculty and users abreast of its services and charges.

•	Financial

i.	CUSG will streamline its administrative support needs.
ii.	CUSG will streamline and simplify its services and recharges.
iii.	CUSG will focus on providing efficient and cost-effective support while maintain a break-even financial status for 2000-2001.
iv.	CUSG will review its past deficits, including 1999-2000, and finalize plans to recover past debts.

•	Staffing

i.	CUSG will need hire another PAII to supplement the EECS Uniform User Helpdesk.
ii.	CUSG will need to hire an additional work-study student for some back-end tasks.
iii.	CUSG will continue to improve the quality of its staff’s support and expertise.  This will include relevant trainings and adequate tools.
iv.	CUSG will need to obtain some administrative support both in purchasing, BFS, and daily administrative support.