D R A F T

Local System Administrator Guidelines

July 3, 1996

The purpose of these guidelines is to generally describe the administration and management required by local (departmental) computing systems. The stability and reliability of the UAB Campus Network depends on knowledgeable and consistent local system administration. A department or group of departments that share local computing resources and utilize the UAB Campus Network must have local support to administer these resources. This can be provided through a local system administrator who reports to a department or group of departments, a consultant or a university service center. Local system administrators are the first level of support for a business unit. Central resources are available to support the overall campus network and assist the local system administrator with network connectivity issues and problem resolution.

Local system administrators should have formal training in the operating system and network protocols of the system they support. It is preferred that they be certified. If they are not certified, departments must allocate the funds and the time required to acquire the training necessary for certification. Training is available through UAB Special Studies and local companies. Local system administrators should participate in continuing education as it is available and when network operating systems are upgraded to the next version or level. Local system administrators must cross-train someone within the department to do backup and recovery operations when the administrator is unavailable. The backup person must be able to handle minimum day-to-day operation of the applications that run on the workstations.

UAB local system administrators are classified as Information Specialists I, II, and III. The minimum qualifications for each are outlined below.

Information Specialist I: Position requires a two-year associate’s degree or high school diploma plus two years of occupational specific training. A minimum of one year experience in computer technology. Some knowledge of local and wide-area networks. Effective verbal and written communication skills a must. Directly related experience may be considered in lieu of a degree requirement. Network certification is not required; however the individual must pursue certification through continuing education, technical seminars and training courses during his employment.

Information Specialist II. Position requires a Bachelor’s degree in Business Administration, Computer Science, or field directly related to the department’s area of expertise. Minimum of three years’ experience is required. Prior experience should include database management, project coordination and general administration. At least one year exposure to programming environment is preferred. On-the-job experience should be supplemented with continuing education gained through technical seminars and/or training courses. Directly related experience may be considered in lieu of a degree requirement. Network certification is required.

Information Specialist III. Position requires a BS degree in Computer Science, Engineering, Math or closely related field. Minimum of 5 years experience in an information systems environment. Should have full knowledge of all application skills and programming. Effective verbal and written communication skills a must. Some supervisory experience is helpful. Directly related experience may be considered in lieu of a degree requirement. Network certification is required.

Novell Netware is the network operating system that has proved successful in meeting the needs of many administrative and research/academic areas. The University Computer Center/University Communications Services Data Communications/ Networking Services group (DC/NS) and Health Information Systems (HIS) have staff members who can support local system administrators in system management and problem solving for these systems. Other networking operating systems may better suit the needs of some areas. Windows/NT and Appleshare are approved LAN operating systems although the DC/NS staff cannot provide assistance with implementation and management at this time. UNIX systems that use TCP/IP natively are appropriate for some areas. Departments must be certain they have permanent support staff with the necessary expertise before considering these systems.

TIMGroup is an informal association of local system administrators who meet monthly to discuss networking problems, directions and related campus activities. Please contact Lister Hill Library for details.

UAB Computer and Electronic Repair provides equipment maintenance and Novell and Windows NT, LAN administration services. Contact the department for a fee schedule.

There are several on-line discussion groups and local newsgroups for network administrators. Participation in theses groups provides opportunity to discuss problems with other local administrators and are a means to notify administrators of network problems and changes that may impact them.

1. Day-to Day System Administration

Add, delete, and change local system users.

Troubleshoot hardware, software, application and network problems for local users.

Serve as contact between the local group and DC/NS or HIS for network problem reporting and resolution.

Assist DC/NS in network problem resolution.

2. System Documentation

Record the description (serial and model numbers), acquisition, movement and disposal of LAN equipment in accordance with Equipment Accounting Policy. Provide this information to the department Accountable Equipment Officer who interfaces with Equipment Accounting. Use this information to maintain hardware, software, and configuration documentation on servers, desktop workstations, printers and modems. This documentation may be maintained electronically; software that can be used for this purpose is available from TIMGroup, located on the Lister Hill FTP server. Copies of this documentation (paper or digital) should be stored offsite through the TUCC or HIS Computer Operations Manager. Attachments 1 and 2 are examples of the information required. They include:

login names

user locations

hardware, model numbers, characteristics and property tag numbers at each location

software installed at each location, dates purchased and installed, manufacturer, version and level

server location

network address information (such as IP numbers) assigned to all devices

2. Software Copying Policies

Supply system users with UAB Policies and Procedures for network usage and software copying. Council users to remove any unauthorized software or hardware on the server or their PC.

3. Disaster Recovery

Develop a formal disaster recovery plan and testing schedule.

Ensure that each server has back-up capability.

Perform daily and weekly server backups. At least once a week, deliver a backup of the server and the compression software, to the TUCC or HIS Computer Operations Manager for offsite storage. Label it with the department name, hardware type, server IP address, date and time of backup.

4. Security (refer to the UAB Medical Center Network Architecture Standards and Guidelines, Network Security)

Users must have assigned signon codes and unique passwords.

Require all system users to use passwords and change them frequently. Encrypt all passwords if the network has this capability. UAB auditors recommend a minimum password length of 6 and minimum change frequency of 90 days. Please refer to the TUCC On-line Manual for password selection guidelines.

Setup at least one additional system administrator ID with supervisor privileges for emergency system administration backup. It is recommended that this ID/Password be sealed in a labeled envelope, and delivered to the TUCC or HIS Operations Manager to be stored in the locked facilities.

Refer to the Standards and Guidelines, Network Security section for data encryption standards and firewall recommendations. Having good security on the network is the best protection.

All servers and workstations should run virus protection software. DC/NS recommends F-PROT virus protection software. The software should be updated every three months to ensure that protection from new viruses is included. All diskettes should be scanned before introducing them to the system.

Additional security should be provided for workstations in unsecured areas.

5. Dial-in Access

Use central dial-in access through the UAB Campus Network. This provides user authentication and does not tie up campus telephone system resources. Do not attach modems to the local system without careful planning for security needs and consulting with DC/NS.

.

SERVER NAME: ______________________________________________________

User Name: __________________________________________________________

Location: ________________________________ Phone: _____________________

Login Name: _____________________________ Password: ___________________

Vendor: _________________________________ Model: ______________________

S/N: ____________________________________ UAB Property No: _____________

Memory: _______________ HD Size: _________ Processor: ___________________

Vendor: _________________________________ Model: ______________________

S/N: ____________________________________ UAB Property No: _____________

Networked? ___________ Queue name: __________________ Number: _______

Pserver Name: ________________________________________________________

Vendor: _________________________________ Model: ______________________

Communications Software: _______________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

Date: _______________________________________________________________

Server Name: ________________________________________________________

Location: ____________________________________________________________

Number of Users on Server: _____________________________________________

System Administrator Name: _____________________________________________

S/A Location/Phone Number: _____________________________________________

Hard Drive Capacity: ____________________________________________________

I/P Address: ___________________________ Type of NIC: __________________

1. _______________________________ Number of Licenses: ___________

1. _______________________________ Number of Licenses: ___________

1. _______________________________ Number of Licenses: ___________

2. _______________________________ Number of Licenses: ___________

3. _______________________________ Number of Licenses: ___________

4. _______________________________ Number of Licenses: ___________

5. _______________________________ Number of Licenses: ___________

6. _______________________________ Number of Licenses: ___________

7. _______________________________ Number of Licenses: ___________

8. _______________________________ Number of Licenses: ___________

9. _______________________________ Number of Licenses: ___________

10. _______________________________ Number of Licenses: ___________