31
CMPE 151: Network Administration Spring 2004

CMPE 151: Network Administration

Embed Size (px)

DESCRIPTION

CMPE 151: Network Administration. Spring 2004. Class Description. Focus: system and network administration. Sequence of exercises. E.g., installing/configuring client machines (including kernel), servers (FTP, Web, file server, mail, DNS, etc.), network gateways (firewalls, NAT), etc. - PowerPoint PPT Presentation

Citation preview

Page 1: CMPE 151: Network Administration

CMPE 151: Network Administration

Spring 2004

Page 2: CMPE 151: Network Administration

Class Description Focus: system and network

administration. Sequence of exercises.

E.g., installing/configuring client machines (including kernel), servers (FTP, Web, file server, mail, DNS, etc.), network gateways (firewalls, NAT), etc.

Final project.

Page 3: CMPE 151: Network Administration

Class Format Lectures.

Meet in BE 168. Typically, 2 lectures on each topic:

A more “theoretical” lecture on background material.

A more “practical” lecture to get projects started.

Lab time. Students expected to spend ~10

hr/week in the lab.

Page 4: CMPE 151: Network Administration

More class information Grading:

Weekly projects: 75%. Final project: 25%.

Academic Integrity Policies: Will be strictly enforced. Come talk to us if questions.

Page 5: CMPE 151: Network Administration

Class Web Page www.cse.ucsc.edu/classes/cmpe151/Spring04. One of the main course resources. It will be constantly updated. Students are responsible for

keeping track of updates (e.g., syllabus, project due dates, links to project descriptions, etc.).

Page 6: CMPE 151: Network Administration

Projects Current list and due dates on Web

page. Project description.

Should have all information required for each project,

Including how to submit project. They will be added as we go.

Page 7: CMPE 151: Network Administration

Readings and Documentation List of recommended books on the

Web page. Links to on-line documentation.

Documentation provided on the Web page as starting point.

Seeking further documentation to complete an assignment is considered part of the assignment.

Page 8: CMPE 151: Network Administration

Lab Usage Policies Very important! This is our lab and we must keep it

in working condition!

Page 9: CMPE 151: Network Administration

Lab Usage Policies (cont’d) Access:

Only to registered students! No food or drinks!

Equipment: All equipment must remain in the lab at all times. Students are responsible ($$$) for faulty, stolen,

vandalized equipment. Students must report immediately any problems.

Lab Fee: Used for printing and some “non-

permanent”equipment.

Page 10: CMPE 151: Network Administration

Lab Setup LAN of workstations. Connected to outside world through netlab.cse.ucsc.edu.

All students will get an account on netlab.cse.ucsc.edu.

Students will have root access on all other machines. After finished using a machine for the day,

students must restore them to their original state.

Page 11: CMPE 151: Network Administration

UNIX Basics

Page 12: CMPE 151: Network Administration

Brief history Originally developed at AT&T Labs in

the late 60’s. In the mid 70’s, UNIX was made

available to universities and research centers free of charge.

In 1977, Berkeley’s UNIX distribution became available: BSD (Berkeley Software Distribution). Final release: 4.4BSD-Lite. FreeBSD originates from this release.

Page 13: CMPE 151: Network Administration

UNIX structure

Hardware

UNIX Kernel

Shell

Utilities: editors, compilers, etc.

Page 14: CMPE 151: Network Administration

Shell Command interpreter. Interface between user and OS. Several shells: bourne shell, C

shell, bash, etc.

Page 15: CMPE 151: Network Administration

File structure Unix file systems are organized as

hierarchies of files and directories.

Page 16: CMPE 151: Network Administration

File structure: example

Client/root

vmunix usr

staffstudents

Server 1/root

export

users

joe bob

Server 2/root

nfs

users

ann eve

Page 17: CMPE 151: Network Administration

Files and directories Files are leaf nodes in the file

structure tree and directories are intermediate nodes.

File names: up to 255 characters. Upper and lower case letters. Numbers. Some special characters. File name extensions (preceded by

“.”). Describes file content.

Page 18: CMPE 151: Network Administration

Pathname Concatenation of directory names

from root to file name using “/” as delimiters. Example: /export/users/bob /cse/faculty/katia

Absolute versus relative pathnames.

Page 19: CMPE 151: Network Administration

Special directories Working directory (or “current”

directory): “.” Home directory (“~”). Parent directory: “..”

Page 20: CMPE 151: Network Administration

Navigating… pwd. cd. ls.

Page 21: CMPE 151: Network Administration

Creating and removing directories mkdir. rmdir.

Page 22: CMPE 151: Network Administration

Moving and copying mv. cp. Example:

$ pwd/home/katia$ mv summary.txt documents/.

Page 23: CMPE 151: Network Administration

Access permissions Types of permissions:

Read, write, execute. Who can do it?

Owner, member of owner’s group, anyone else.

ls –l (long) displays access permissions, file owner and group, size, last modified data and time, file name.

Page 24: CMPE 151: Network Administration

Changing access permissions chmod Example:

chmod a+rw summary.txt

Page 25: CMPE 151: Network Administration

Listing file contents More, cat, less.

Page 26: CMPE 151: Network Administration

Shell Command interpreter. Command line. Shell script.

Page 27: CMPE 151: Network Administration

Command line Syntax

<command> arg1 arg2 … argn [cr] Execution:

If shell finds file with same name as command, a new process is started to execute that file.

Shell is sleeping while command executes.

Shell returns to active and issues prompt.

Page 28: CMPE 151: Network Administration

Standard input and output Default places where input info is

read and output info is sent. By default, stdio and stdout is the

terminal.

Page 29: CMPE 151: Network Administration

Redirection Redirect stdin and stdout. <command> [arguments] > filename <command> [arguments] < filename Example:

$ cat summary.txt $ cat summary.txt > summary2.txt $ cat > sample.txt

Page 30: CMPE 151: Network Administration

Pipes stdout of one command “piped” to

stdin of anther command. Example:

cat summary.txt | more who | grep “katia”

Page 31: CMPE 151: Network Administration

Running program on background OS runs program while you can do

other things. “&”.