0% found this document useful (0 votes)
7 views

Chapter-1-NSA

The document is a course outline for Network and System Administration at Bule Hora University, detailing key concepts such as systems, networks, and operating systems. It covers the architecture, modules, components, interfaces, and data related to systems, as well as the roles and responsibilities of system administrators. Additionally, it discusses Linux distributions, file system hierarchy, user and access management, and essential shell commands.

Uploaded by

lidelidetuwatiro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views

Chapter-1-NSA

The document is a course outline for Network and System Administration at Bule Hora University, detailing key concepts such as systems, networks, and operating systems. It covers the architecture, modules, components, interfaces, and data related to systems, as well as the roles and responsibilities of system administrators. Additionally, it discusses Linux distributions, file system hierarchy, user and access management, and essential shell commands.

Uploaded by

lidelidetuwatiro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 60

Bule Hora University

College of Informatics
Dep’t of Computer Science
Course Title: Network and System Administration

Chapter 1 - Introduction to Network and System Administration (NSA)


Compiled by: Firaol B.

March-2025
Outlines:
• Introduction
• Objectives/Goals, Challenges and Common Practices
• Overview of the OSs
• Unix-like Systems Vs Windows Systems
• Linux Distributions and UIs
• Linux Operations Review
• Essential Shell Commands
• Advanced Shell Features
Introduction to NSA, What is a System?

What is a System?
• The dictionary definition of a system is “a set of things working
together as parts of a mechanism or an interconnecting network.”
• System is an organized collection of computers interacting with a
group of users.
• A system is comprised of five primary elements: architecture, modules,
components, interfaces, and data.

Network and System Administration (BHU/CS) 3


Introduction to NSA, What is a System?
Architecture:
• Architecture is the conceptual model that defines the system structure
and behavior.
• This is often represented graphically through the use of flowcharts that
illustrate how the processes work and how each component is related
to one another.
Modules:
• Modules are pieces (hardware or software) of a system that handle
specific tasks within it.
• Each module has a defined role that details exactly what its purpose is.
Network and System Administration (BHU/CS) 4
Introduction to NSA, What is a System?
Components
• Components are groups of modules that perform related functions.
• Components are like micro_x0002_systems within the system at large.
• Using components and modules in this way is called modular design,
and it’s what allows systems to reuse certain pieces or have them
removed and replaced without crippling the system.
• Each component can function on its own and can be interchanged or
placed into new systems.

Network and System Administration (BHU/CS) 5


Introduction to NSA, What is a System?
Interfaces
• Interfaces encompass two separate entities: user interfaces and system
interfaces.
• User interface (UI) design defines the way information is presented to
users and how they interact with the system.
• System interface design deals with how the components interact with
one another and with other systems.

Network and System Administration (BHU/CS) 6


Introduction to NSA, What is a System?
Data: Data is the information used and outputted by the system.
• System designers dictate what data is pertinent for each
component within the system and decide how it will be handled.
• Each component complements the system in its own way to keep
everything functioning properly.
• If one piece of the puzzle becomes askew, the entire system can
be impacted. B/c technology is constantly evolving, components
are modified, added, or removed on a constant basis. To make
sure these modifications have the desired effect, systems design is
used to orchestrate the whole affair.
Network and System Administration (BHU/CS) 7
Introduction to NSA, What is a System?
Introduction to NSA, What is a Network?
• A network is a set of devices / nodes connected by
communication links.
•A node can be a computer, printer, or any other device
capable of sending and/or receiving data generated by
other nodes on the network.
The Structure of Computer Systems
A computer system is a collection of components (both hardware
and software) that function as a part of a whole.
Accessing computer resources is divided into layers.
Each layer is isolated and only interacts directly with the layer
below or above it.
If we install a new hardware device
No need to change anything about the user/applications.
However, you do need to make changes to the operating
system.
You need to install the device drivers that the operating
system will use to control the new device.
The Structure of Computer Systems
If we install a new software application
No need to make any changes to your
hardware.
But we need to make sure the application is
supported by the operating system
user will need to learn how to use the new
application.
If we change the operating system
Need to make sure that both applications and
hardware will compatible with the new
operating system.
NSA overview

Network and System Administration (BHU/CS) Slide #12


NSA overview...

Network and System Administration (BHU/CS) Slide #13


NSA overview...

Network and System Administration (BHU/CS) Slide #14


NSA Goals

Network and System Administration (BHU/CS) Slide #15


NSA Challenges

Network and System Administration (BHU/CS) Slide #16


NSA Common Practices

Network and System Administration (BHU/CS) Slide #17


NSA Overview...

Network and System Administration (BHU/CS) Slide #18


NSA Overview...

Network and System Administration (BHU/CS) Slide #19


NSA Overview...

Network and System Administration (BHU/CS) Slide #20


NSA Overview...

Network and System Administration (BHU/CS) Slide #21


NSA Overview...

Network and System Administration (BHU/CS) Slide #22


NSA overview...

Network and System Administration (BHU/CS) Slide #23


NSA overview...

Network and System Administration (BHU/CS) Slide #24


NSA overview...

Network and System Administration (BHU/CS) Slide #25


NSA overview...

Network and System Administration (BHU/CS) Slide #26


NSA overview...

Network and System Administration (BHU/CS) Slide #27


NSA overview...

Network and System Administration (BHU/CS) Slide #28


NSA overview...

Network and System Administration (BHU/CS) Slide #29


NSA overview...

Network and System Administration (BHU/CS) Slide #30


NSA overview...

Network and System Administration (BHU/CS) Slide #31


NSA overview...

Network and System Administration (BHU/CS) Slide #32


NSA overview...

Network and System Administration (BHU/CS) Slide #33


What do sysadmins do?
Small org: sysadmin can be entire IT/Computing staff
– Phone support
– Order and install software and hardware
– Fix anything that breaks from phones to servers
– Develop software
Large org: sysadmin is one of many IT/Computing staff
– Specialists instead of “jack of all trades”
– Database admin, Network admin, Fileserver admin, Help desk
worker, Programmers, Logistics
Network and System Administration (BHU/CS) Slide #34
Common Activities
1. Add and remove users.
2. Add and remove hardware.
3. Perform backups.
4. Install new software systems.
5. Troubleshooting.
6. System monitoring.
7. Auditing security.
8. Help users.
9. Communicate.
Network and System Administration (BHU/CS) Slide #35
User Management
Creating user accounts
– Consistency requires automation
– Startup (dot) files
Namespace management
– Usernames and UIDs
– Multiple namespaces or SSI?
Removing user accounts
– Consistency requires automation
– Many accounts across different systems

Network and System Administration (BHU/CS) Slide #36


Hardware Management
Adding and removing hardware
– Configuration, cabling, etc.
Purchase
– Evaluate and purchase servers + other hardware
Capacity planning
– How many servers? How much bandwidth, storage?
Data Center management
– Power, racks, environment (cooling, fire alarm)
Virtualization
– When can virtual servers be used vs. physical?
Network and System Administration (BHU/CS) Slide #37
Backups
Backup strategy and policies
– Scheduling: when and how often?
– Capacity planning
– Location: on-site vs. off-site.
Monitoring backups
– Checking logs
– Verifying media
Performing restores when requested

Network and System Administration (BHU/CS) Slide #38


Software Installation
Automated consistent OS installs
– Desktop vs. server OS image needs.
Installation of software
– Purchase, find, or build custom software.
Managing software installations
– Distributing software to multiple hosts.
– Managing multiple versions of a software pkg.
Patching and updating software

Network and System Administration (BHU/CS) Slide #39


Troubleshooting
Problem identification
– By user notification
– By log files or monitoring programs
Tracking and visibility
– Ensure users know you’re working on problem
– Provide an ETA if possible
Finding the root cause of problems
– Provide temporary solution if necessary
– Solve the root problem to permanently eliminate

Network and System Administration (BHU/CS) Slide #40


System Monitoring
Automatically monitor systems for
– Problems (disk full, error logs, security)
– Performance (CPU, mem, disk, network)
Provides data for capacity planning
– Determine need for resources
– Establish case to bring to management

Network and System Administration (BHU/CS) Slide #41


Helping Users
Request tracking system
– Ensures that you don’t forget problems.
– Ensures users know you’re working on their problem; reduces
interruptions, status queries.
– Lets management know what you’ve done.
User documentation and training
– Policies and procedures
Schedule and communicate downtimes
Network and System Administration (BHU/CS) Slide #42
Communicate
Customers
– Keep customer appraised of process.
• When you’ve started working on a request with ETA.
• When you make progress, need feedback.
• When you’re finished.
– Communicate system status.
• Uptime, scheduled downtimes, failures.
– Meet regularly with customer managers.
Managers
– Meet regularly with your manager.
– Write weekly status reports.
Network and System Administration (BHU/CS) Slide #43
Overview of OS
• Computer System = Hardware + Software + User
• Software = Application Software + System Software(OS)
• An OS is a system Software that acts as an intermediary/interface
between a user of a computer and the computer hardware.
• Operating system goals:
 Execute user programs and make solving user problems easier
 Make the computer system convenient to use
 Use the computer hardware in an efficient manner

Network and System Administration (BHU/CS) Slide #44


Functions of Operating System
Linux Distributions
Linux is a free Unix-type operating system originally created by Linus
Torvalds with the assistance of developers around the world.
Some of the popular LINUX distributions are:
• Mandrake: http://www.mandrakesoft.com/
• RedHat: http://www.redhat.com/
• Fedora: http://fedora.redhat.com/
• SuSE/Novell: http://www.suse.com/
• Debian: http://www.debian.org/

Network and System Administration (BHU/CS) Slide #46


Linux File System Hierarchy
• The Linux File Hierarchy Structure or the Filesystem Hierarchy Standard
(FHS) defines the directory structure and directory contents in Unix-like
operating systems. It is maintained by the Linux Foundation.
• In the FHS, all files and directories appear under the root directory /, even if
they are stored on different physical or virtual devices.
• Some of these directories only exist on a particular system if certain
subsystems, such as the X Window System, are installed.
• Most of these directories exist in all UNIX operating systems and are
generally used in much the same way; however, the descriptions here are
those used specifically for the FHS and are not considered authoritative for
platforms other than Linux.
Network and System Administration (BHU/CS) Slide #47
...cont’d

Slide #48
Network and System Administration (BHU/CS)
...cont’d
The ancestor of all directories on the system; all other directories
are subdirectories of this directory, either directly or through other
subdirectories.
Essential tools and other programs (or binaries).
Files representing the system's various hardware devices. For
example, you use the file `/dev/cdrom' to access the CD−ROM drive.
Miscellaneous system configuration files, startup files, etc.
The home directories for all of the system's users.
Essential system library files used by tools in `/bin'.

Network and System Administration (BHU/CS) Slide #49


...cont’d
Files that give information about current system processes.
The superuser's home directory, whose username is root. (In the
past, the home directory for the superuser was simply `/'; later, `/root' was
adopted for this purpose to reduce clutter in `/'.)
Essential system administrator tools, or system binaries.
Temporary files.
Subdirectories with files related to user tools and applications.

Network and System Administration (BHU/CS) Slide #50


Directories, Files and Inodes
• Every directory and file is listed in its parent directory.
• In the case of the root directory, that parent is itself.
• A directory is a file that contains a table listing the files contained within
it, giving file names to the inode numbers in the list.
• The information about all the files and directories is maintained in INODE
TABLE
• An Inode (Index Nodes) is an entry in the table containing information
about a file (metadata) including file permissions, UID, GID, size, time
stamp, pointers to files data blocks on the disk etc.

Network and System Administration (BHU/CS) Slide #51


Users, Groups and Access Permissions
• In UNIX/LINUX, there is a concept of user and an associated group
• The system determines whether or not a user or group can access a
file or program based on the permissions assigned to them.
• Apart from all the users, there is a special user called Super User or
the root which has permission to access any file and directory

Network and System Administration (BHU/CS) Slide #52


Access Permissions
Permission:-
• It is useful tool to enhance file.
• It controls which user can access what and how.
• It is the way in which we allow or deny some person or user to
access something.
• Concerned with preventing unauthorized access to the systems
data.
• There are three permissions for any file, directory or application
program.

Network and System Administration (BHU/CS) Slide #53


Access Permissions
• The following lists the symbols used to denote each, along with a brief
description:
• r — Indicates that a given category of user can read a file.
• w — Indicates that a given category of user can write to a file.
• x — Indicates that a given category of user can execute the file.
• Each of the three permissions are assigned to three defined categories of users.
• The categories are:
• owner — The owner of the file or application.
• group — The group that owns the file or application.
• others — All users with access to the system. Slide #54
Network and System Administration (BHU/CS)
...cont’d
• So totally nine(9) permission is given in total for a single file
There are two ways to set permission for a file. They are:
1. Symbolic mode and
2. Absolute mode

Slide #55
Network and System Administration (BHU/CS)
...cont’d
1. Symbolic mode
We use symbol for giving permission to the users and its format is chmod
command is followed by string and then the name of file.
Format: chmod + string + file name.
The string has three parts
a) User: (u – user, g – group, o – others)
b) To access or to deny: (+ to access and – to deny)
c) Permission: (r – read, w – write, x - execute)
Example: chmod u + rwx A.txt
: chmod uo – rw A.txt
Slide #56
Network and System Administration (BHU/CS)
...cont’d
2. Absolute mode
We use number
Format: chmod + number + file name
The number has three parts
a) 4 – read
b) 2 – write
c) 1 – execute
d) 0 – none
Example: chmod 764 A.txt
:chmod 777 A.txt Slide #57
Network and System Administration (BHU/CS)
NETWORK & SYSTEMS ADMINISTRATORS DO THE FOLLOWING:
• Determine an organization’s network and computer system needs
before setting up
• Install all network hardware and software and make needed
upgrades and repairs
• Maintain network and computer system security and ensure that all
systems are operating correctly
• Collect data in order to evaluate and optimize network or system
performance

Network and System Administration (BHU/CS) Slide #58


...cont’d
• Add users to a network, assign and update security
permissions on the network
• Train users in the proper use of hardware and software
• Interpret and solve problems when a user or an automated
monitoring system alerts them that one exists

Network and System Administration (BHU/CS) Slide #59


Reading Assignment
• Essential Shell Commands
• Basic File Manipulation Commands and Directory Navigation Commands
• Advanced File Manipulation Commands (Init, Processes, and Threads)
• Advanced Shell Features

Network and System Administration (BHU/CS) Slide #60

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy