university of pisa computer science department system administration stefano bistarelli university...

University of PisaComputer Science Department

System Administration

Stefano Bistarelli

University of PisaComputer Science [email protected]://www.di.unipi.it/~bista/

Annalina Fabrizio

dr. Stefano Bistarelli: System AdministrationUniversity of PisaComputer Science Department

Outline

lun mar mer gio ven sab dom

1 2 3 4 5 6 7

8 9 10 11 lab 12 lab 13 14

15 lab 16 17 18 lab 19 lab 20 21

22 lab 23selfstudy 24 25lab 26 lab 27 28

29 lab 30 selfstudy 31

2001

Gennaio


Outline

lun mar mer gio ven sab dom

1 2 lab 3 4

5 lab 6 7 Ripasso in

aula / Selfstudy 8 lab 9l ab 10 11

12 Exam 13 Exam 14 15 16 17 18

19 20 21 22 23 24 25

26 27 28

2001

Febbraio


Prima Settimana

9IntroduzioneInstallazione win2KInstallazione Linux

Riferimenti:-Lucidi-Cap 1,2,15 libro-RH inst.guide

10W2KActive DirectoryUtenti e gruppi

LinuxUtentiBackup

11 lab

-Linux utente1

12 lab

-Linux utente2


Seconda settimana

15 lab

-Creare disco boot ms-dos con dentro FDISK, FORMAT, etc.-Fare fdisk, fdisk/mbr-installazione win2K-Gestione licenze-Disco di ripristino-Backup, restore-Scheduling di backup nonno-padre-figlio-Uso di comandi NET-Install. XwinRiferimenti-cap. 1,2,3,15 libro

16 17 18 lab

Inst Linux,Creare multi bootBackup linux,Inserimento utenti linux

Inserimento utenti W2k

19 lab

W2kFile system

LinuxFS


Classification of Systems

Small sites: have 1 - 10 machines, all running the same OS. only about 20 users. There is only one administrator.

Medium sites: have up to 100 machines, and may be running up to 3 different

OSs. usually has about 100 users. more than one administrator, either specializing in different OSs

or sharing general system administrator duties. Large sites:

have over 100 computers, multiple operating systems over 100 users. a hierarchy of administration, with the lead or senior System

Administrator responsible for all of the systems and assigning duties to one or more assistant administrators.


System Administration Skills: Novice System Administrator (1/2)

Required skills: Strong inter-personal and communication skills: is capable

of explaining simple procedures in writing or verbally; has good phone skills.

Familiar with Unix and its commands/utilities at the user level. Can edit files using more than one editor. Know shell commands.

Can perform standard file processing tasks; find, move, remove, redirection.

Required background: Two years of college or equivalent post-high school

education or experience.


System Administration Skills: Novice System Administrator (2/2)

Desirable: A degree or certificat in computer science or related field. Previous experience in customer support, computer

operations, system administration, or another related area. Motivated to advance in the profession.

Appropriate Responsibilities: Perform routine tasks under the direct supervision of a

more experienced administrator. Be the front-line interface for users; accepting problem

reports and passing them to the appropriate system administrators.


System Administration Skills: Junior System Administrator (1/2)

Required skills: Strong inter-personal and communication skills: capable of

training users in applications and Unix fundamentals. Able to write basic system and user documentation.

High skill level with most Unix commands and utilities. Familiar with most basic system administration tools and tasks

(can cleanly boot and shutdown the system, add and remove user accounts, use backup programs, perform fsck and maintain system database files (groups, hosts, aliases, etc.)).

Fundamental understanding of the functioning of the Unix operating system: for example understands job control, hard and soft linking.

Required background: One to three years of system administration experience.


System Administration Skills: Junior System Administrator (2/2)

Desirable: Degree in CS or a related field. Familiarity with networked/ distributed computing environments

(can use the route command, add a workstation to a network, or mount a remote filesystem.).

Ability to write functional scripts in an administrative language (shell, Perl, Tk).

Some programming experience in an applicable language like C. Appropriate Responsibilities:

Administer a small site alone, or assist in the administration of a larger site.

Work under the general supervision of a more senior system administrator or computer systems manager.


System Administration Skills: Intermediate/Advanced SysAdm (1/2)

Required skills: Has strong inter-personal and communication skills: capable of

training users in complex topics, making presentations to internal groups. Able to write intricate system and user documentation. Capable of writing and explaining purchase justifications.

Independent problem solving; self-directed, self-starting. Very comfortable with most aspects of the Unix operating system:

paging/swapping, inter-process communication, devices and device driver fundamentals, file system concepts like inode and superblock.

Familiar with fundamental networking/distributed computing environments and concepts. Can configure NFS and NIS, use nslookup or research to check information in the DNS.

Ability to write detailed scripts in at least one, preferably two administrative lnaguages, (shell scripts, Perl, Tk).

Ability to perform at least minimal debugging and modification of C programs.


System Administration Skills: Intermediate/Advanced SysAdm (2/2)

Required background: Three to five years of system administration experience.

Desirable: At least a BS in Computer Science or a related field. Significant programming background in any applicable language.

Appropriate Responsibilities: Receive general instructions for new duties from supervisor. Administers a mid-size site alone, or assists in administration of a

larger site. Initiates some new responsibilities and helps plan for the future of

the site and network. Manages novice system administrators or operators. Evaluates and/or recommends purchases; has strong influence on

the purchasing process.


System Administration Skills: Senior System Administrator (1/2)

Required skills: Strong inter-personal and communication skills; capable of writing

proposals and papers, acting as a vendor liaison, making presentations to customer/client audiences or making professional presentations, work closely with upper management.

Ability to solve problems quickly and completely. Ability to identify tasks which should be automated and then write

tools to automate them. Solid understanding of the Unix based operations system:

understands paging and swapping, interprocess communication, devices and device drivers, can perform system analysis and tuning.

Ability to program in at least one, preferably two administrative languages, (shell, Perl, Tk) and port C programs from one platform to another, write small C programs.

Solid understanding of networking/distributed computing environments, understanding the principals of routing, client/server programming, and the design of consistent network-wide filesystems.


System Administration Skills: Senior System Administrator (2/2)

Required background: More than 5 years of previous system administration experience.

Desirable: A degree in CS or a related field. Advanced degree preferred. Extensive programming experience in an applicable language. Publications within the field of system administration.

Appropriate Responsibilities: Design/implement complex local and wide-area networks of

machines. Manages a large site or network. Works under general direction of senior management. Establishes/recommends policies and procedures for system use and

services. Provides the technical lead and/or supervision for system

administrators, system programmers, or others. Has purchasing authority and responsibility for purchase

justification.


Finally, some important thoughts for system Administrators:

1. Never do something you can't undo. 2. Always check the backups, never assume they are working.

Make sure you can restore from them, too. 3. Write down what you did, even if you know you will never

forget it, you will. 4. If you do it more than once, write a script. 5. Get to know your users before there is a problem, then when

there is, they will know who you are and maybe have a little understanding.

6. Remember you are performing a service for your users, you don't own the system, you just get to play with it.

7. Check your backups. 8. Never stop learning, there is always something you should

know to make your job easier and your system more stable and secure.

9. Check your backups, again.


history


Unix history (1/4)

1969 Ken Thompson (at Bell Labs): first version of unix on a DEC PDP-7.

1970 Thompson and Dennis Ritchie ported it to a DEC PDP-11/20. the first C compiler ( a language in which one could write a portable

OS.

1973 Ritchie and Thompson rewrote the UNIX kernel in C. 1974-1977 UNIX source code was free to Universities.

1978 UNIX, 7th edition, released. Portable to various hardware architechures. ATT announces that they would be charging license fees for UNIX source (version 7 forms the basis for all the Unix versions currently available).


Unix history (2/4)

1979 ATT's announcement of its intention to commercialize UNIX. University of California at Berkeley create its own variant: BSD UNIX.

The most influencial BSD versions are 4.2 (1983) and 4.3 (1987). The DARPA sponsored development of the Internet was on BSD UNIX. Most of the early commercial vendors of UNIX (Sun (SunOS), DEC

(Ultrix), etc.) were largely based on BSD UNIX.

1983 ATT released the commercial UNIX System V. BSD version 4.2

released. 1987 ATT UNIX System V release 3. This is the release that various

major hardware vendors (HP (HP-UX) and IBM (AIX). BSD v 4.3 was released.

ATT and Sun jointly agreed to cooperate on UNIX development to merge/unify System V and BSD.


Unix history (3/4)

1990 ATT issues System V release 4 as a new standard unifying UNIX variants. This was the result of Sun and ATT's cooperation.

However, other vendors (especially DEC, HP, IBM) united to creat the Open Software Foundation, OSF. The quip that OSF really stands for Oppose Sun Forever has some truth.

1991 OSF-1 released. This was also the year that freely distributable Unix clones such as Linux and FreeBSD started.

1992 Sun develops its Solaris OS: a System V release 4.

1993 X Window, the client/server-based graphical user developed at MIT,was ported in a freely distributable form to Intel hardware

(XFree86).


Unix history (4/4)

1995 Linux, a unix clone written by Linus Torvalds, is being actively developed by a growing Internet-based community of hackers.

The source code is freely available. Ports for Intel, Alpha, Sparc and MIPS hardware. Due to its development and use, documentation for Linux, even when

for the user just running Linux on their own machine, has much that is of interest to the Unix system administrator.


Win2000 history

1985 MS-Net per DOS3.10 (file server and print server)

1988 LAN Manager per OS/2

1993 MS Win NT 3.1 stesso numero di versione di window e LAN Manager

1994 Win NT 3.5

1995 Win NT 3.51 + IIS 1.0

1996 Win NT 4.0 (TCP/IP, DNS, IIS 2.0)

???? Win NT 5 ????

2000 Window 2K Server


Progettazione installazione server


Progettazione installazione server: che scelta HW?

Disco SCSI 1GByte per sistema NTFS Applicativi Dati utente

NIC (eth 10/100 Mbps) Stessa scheda su tutti i

PC 256 Mbyte RAM Backup Ups Raid


Tools a portata di mano (win2k)

Cd win2k Dischetto avvio dos (con driver per ntfs) Dischetto per ripristino Nastro per backup


Istallazione (2 ore)

Boot con floppy dos, fdisk, fdisk /mbr Boot con cd (10 min) Partizioni: (10 min)

¼ del disco = partizione ntfs Reboot e inst. Grafica (15 min) Regional setting

Modifica tastiera e euro/italia Personalize your sw

Nome istallatore Licensing Computer name and adm password Data e ora Copia dei file (1 ora)


Installazione cont.

Gestione licenze Settagio ruolo server Aggiunta nomi per altri server

1 DC Gli altri tutti server applicativi

Creazione disco di ripristino Backup (e restore)


tipi di backup di win2k

per ogni file "bit di archiviazione" 1=file modificato 0= non modificato (posto a 0 dal backup)

backup normale: copia tutti i file (i bit tutti a 0)

backup mediante copia: copia tutti i file (ma non cambia bit)

backup incrementale: copia solo file modificati da ultimo backup (copia i file con

bit a 1 e azzera i bit dei file copiati) backup differenziale

(copia i file con bit a 1 ma non li azzera) backup quotidiano

(copia file mutati in un determinato giorno, bit immutato)


Schema Nonno-padre-figlio

a fine mese backup normale (per 12 mesi) ogni venerdi backup normale settimanale

(per 5 settimane=1mese) lun,mart,merc,giov backup incrementale

totale di 12+5+4=21 nastri


Installazione Linux!


Installazione Linux (1 ora?)

Creazione disco boot RAWRITE IMG

Installazione Language setting: english Keyboard configuration Mouse configuration Install type=custom Manual partitioning : fdisk Lilo:

creare boot disk Lilo su /dev/hda2


Installazione Linux (1 ora?)

Installazione Timezone (not use UTC) Creazione 10 account (per 2 lab successivi) Package (tutto) Xconfiguration


Dati HW (com msd) e da window.

Prendere nota per ogni periferica IRQ, I/O, memoria scheda audio Dischi: numero, ide/scsi, cilindri, settori, facce? Ram istallata? cd-rom (ide/scsi)? Scsi adapter? Nic? Mouse (ps2/serial, 2/3 bottoni)? schede video (modello, quantità RAM)? Monitor (vertical, orizontal refresh rate)? Controlla HCL


Proprietà del sistema (1/2)


Proprietà del sistema (2/2)


Linux!


Selezione della Lingua


Configurazione tastiera


Configurazione mouse


Tipo di istallazione


Partizionamento


Configurazione della rete


Regional settings


Inserimento account


packages


X Configuration (1/2)


X Configuration (2/2)


The end!


Installing ….


Laboratorio win2k: 3 ore

installare tutte le macchine, (occorrono 10 cd e 20 floppy) Prima verificare interrupt schede di rete e segnarle su

foglietto. Partizioni: cancellare tutto l’esistente, riservare ¼ per

win2k (almeno 1.5 Gbyte) Setup: selezionare boot da cdrom Aggiungere: Tastiera italiana, codifica italia + euro,

Lasciare standard americani Settare fascia oraria gmt+1 Nome utente: nome istallatore, nome società vuoti Nome macchina= gia’ assegnati a lezione Password= nomemachinapsw Indirizzi di rete come a lezione (dovrebbe fare in

automatico)


Laboratorio: 3 ore

Modificare licenza per 10 utenti Settare accesso al dominio corsopescia

(utente unico per ora: studente, password studentepsw)

Creare dischi di ripristino (occorrono 10 dischetti)

Backup e restore (vari esempi) Creazione backup schedulato

Tramite utilità bachup-scheduling Comando backup a linea di comando Comando at


Laboratorio(extended): 2 ore

Comandi NET Installazione xwin su tutte le macchine


Win: inst (cap 1,2,15) backup–Linux:inst (RH ig) Win: regsitro, AD, utenti (cap 4,5,7) Booting/shutdown (fotocopie libro salomon, fotocopie

libro, RH rg) Linux: utenti, superuser, backup (fotocopie libro, RH

rg) FS, device, disk (cap 8,9 - fotocopie libro, RH rg) Processi, printing (fotocopie salomon,cap 10-

fotocopie libro, RH rg) Processi periodici (??, Linux:quota - fotocopie libro, RH

rg) Monitoring (cap 17,20 - - fotocopie libro, RH rg)


Linux 1 : Rute Linux 2: Win: inst (cap 1,2,15) backup–Linux:inst (RH ig) Win: regsitro, AD, utenti (cap 4,5,7) Booting/shutdown (fotocopie libro salomon, fotocopie

libro, RH rg) Linux: utenti, superuser, backup (fotocopie libro, RH rg) FS, device, disk (cap 8,9 - fotocopie libro, RH rg) Processi, printing (fotocopie salomon,cap 10- fotocopie

libro, RH rg) Processi periodici (??, Linux:quota - fotocopie libro, RH

rg) Monitoring (cap 17,20 - - fotocopie libro, RH rg)

university of pisa computer science department system administration stefano bistarelli university...

Documents

junior system administrator

novice system administrator

hierarchy of administration

system database files

required skills

computer operations

communication skills

computer systems manager