‎ etwork administration involves a wide array

N
‎Network Administration ‎of operational tasks that help a network to
‎run smoothly and efficiently.

•‎ Design, installation, and evaluation of

‎network.
•‎ FTP: File transfer; sends passwords in plain
‎Network Administration: ‎• Perform regular data backups. ‎text.

•‎ Create accurate technical documentation ( •‎ HTTP: Web data transfer; all data in clear
‎network diagrams, cabling, etc.). ‎text.

•‎ Implement authentication for network •‎ S-HTTP: Secure HTTP with support for
‎resource access. ‎• Software should be separated from OS files. ‎encryption, signing, MAC authentication.

‎• Provide troubleshooting support. •‎ Follow Unix-style structure: use bin and lib •‎ HTTPS: Secure HTTP using SSL/TLS; all data
‎Structuring Software:
‎for consistency. ‎encrypted.

•‎ Responsible for system setup, •‎ Site-specific software should be stored •‎ SSH: Secure alternative to rsh; encrypts
‎Application Protocols:
‎configuration, and maintenance. ‎separately to define responsibility. ‎session and X11 forwarding.

•‎ Focused on multi-user systems (e.g., •‎ LDAP: Lightweight directory access protocol

‎System Administration: •‎ Small organizations: Central user
‎servers). ‎for user info lookup (passwords, phone
‎registration, simple setup. ‎numbers); connects with NDS, Exchange, NIS.
‎• Hardware configuration.
•‎ Large organizations: Requires balance ‎• NTP: Synchronizes time across the network.
‎Scope and Goals: ‎• Software setup. ‎User Registration: ‎between centralized control and
‎departmental autonomy.
•‎ IMAP: Protocol for reading and transferring
‎• Serve organizational needs. ‎emails; alternative: POP.
•‎ Ensure unique user IDs and flexible access
‎across the network.
•‎ SMTP: Protocol to send emails over the
‎• User account management. ‎network.
‎• Local account: Access limited to one host.
‎• Create file systems.
‎management ‎• Proxy: An agent acting on behalf of another.
•‎ Network account: Access to multiple hosts
‎• Install software. ‎Local vs Network Accounts:
‎in the network domain.
‎• Security
‎• Define backup and recovery policy.
•‎ Centralized password system is ideal for
‎• Uses: ‎• Caching
‎consistency.
‎• System maintenance. ‎Proxies and Agents:
‎Duties of a System Administrator: ‎troubleshooting ‎• Sometimes Load Balancing
‎• Arrange repairs quickly during failures. ‎• Must define clear rules for account use.
‎• Web proxies reduce traffic by caching data.
‎• Hardware/peripheral monitoring. •‎ Users can misuse accounts → need strict
‎control. ‎• Firewall proxies add a security layer.
‎monitoring ‎• Monitor performance.
‎• Policy should include:
•‎ Startup Method: Daemon starts at boot and
‎• Monitor network communication.
‎runs in background.
‎Account Policy: ‎• Allowed and disallowed actions.

‎• Full system access (unrestricted). •‎ On-demand Method: inetd listens and starts
•‎ Enforcement measures (e.g., cleanup of ‎Summoning Daemons:
‎daemon when needed.
‎temp files).
‎Root Account: ‎• Can delete critical system files.
•‎ Not all services are suited for on-demand
•‎ Immediate deactivation if weak passwords
‎• Recovery only possible through backups. ‎startup.
‎are found.

‎• Create users. •‎ Users need support as they lack admin

‎• Converts hostnames ↔ IP addresses.
‎privileges.
‎• Reset passwords. ‎• FQHN: Fully Qualified Host Name.
‎ utomation of Tasks (Perl/
A ‎User Support Services:
‎Python or shell scripts.): •‎ Admins must assist users when problems
‎• Lock/unlock accounts. ‎• Resolver: Client
‎arise.
‎DNS Setup (Domain Name System): ‎• DNS Components:
‎• Monitor server security and services. ‎• BIND: Server
‎1. Direct support.
‎• Choose between: ‎1. httpd.conf
•‎ Knowledge of how systems are used in ‎2. User self-sufficiency.
‎organizations. ‎2. access.conf
‎• Train users.
•‎ OS, applications, hardware/software ‎3. srm.conf
‎Additional Skills Required: ‎troubleshooting. ‎Support Policy: ‎• Best approach: combination of both. ‎• Provide help when needed. ‎• Configuration files:
‎4. mime.types
‎• Problem-solving under stress. ‎• Create FAQs and documentation.
‎5. Perl scripts (aliases, error handling)
‎• Quick and accurate system diagnostics. •‎ Balance support efforts as per available
‎time and automation level. ‎6. Private directories

‎ hapter 1: Introduction to
C
‎System and Network ‎ hapter 3: Host and User
C ‎ hapter 5: Application-level
C
‎Administration ‎Management ‎Services

‎Central Topic

‎Chapter 2: System Components ‎Chapter 4: Network-level Services ‎ hapter 6:Models, Methods and
c
‎Tools of Network Administratio
•‎ Refers to both the operating system and all ‎• Datagram is decapsulated.
‎cooperating computers in a network. ‎At Destination: ‎• Built-in service: CMIS
‎Definition of “System” in Administration: •‎ Packet is extracted and sent to the
•‎ More precisely: human–computer system = ‎transport layer. ‎• Comprehensive; covers all 7 OSI layers
‎collaboration between human and computer
‎to solve a problem or provide a service.
•‎ Transfers packets from source to ‎1. OSI Management Protocol (CMIP): ‎• Used in LAN/WAN management
‎destination without altering them.
‎• No strict definition. ‎• Object-oriented, layered design
•‎ Fragmentation: Splits large packets into
‎Operating System: ‎• Generally includes the kernel + user utilities. ‎smaller ones for delivery. ‎• SNMP often used in this context
‎Network Layer Features:
•‎ Considered all bundled programs essential •‎ Routing: Chooses optimal path for packet ‎• Developed by IETF
‎for system functionality. ‎delivery.
‎• Initially for Internet component management
•‎ Addressing: Adds source and destination
‎• Uses the system and infrastructure. ‎addresses to packets. •‎ Widely adopted for WANs and telecom
‎1. Human: ‎2. SNMP / Internet Model:
‎systems
‎• Often the source of most system issues.
‎1. Packetizing ‎• Easy to implement
‎• Devices that run software.
‎2. Host Computers: ‎Network Layer Services: ‎2. Routing ‎Network Management Standards:
‎• Most commonly deployed standard
‎• Can be fixed or mobile.
‎ hree Main Components of
T ‎3. Forwarding ‎• International standard by ITU-T
‎Human–Computer Systems: ‎• Specialized devices for traffic management.
‎• Designed for telecom network management
•‎ Encapsulates data from upper layers into a ‎ . TMN (Telecommunications Management
3
‎• Direct internet traffic.
‎network layer packet. ‎Network):
‎• Routers: ‎• Based on OSI framework
‎• Operate at IP level (Layer 3 of OSI).
•‎ Adds header (with source & destination
‎• At source: •‎ Covers both network and administrative
‎3. Network Hardware: ‎addresses, and other info).
‎• Manage local network traffic (LAN). ‎management
‎• Switches:
‎• Sends packet to data link layer.
‎• Operate at Ethernet level (Layer 2). ‎• Adopted globally via IEEE
‎• Receives packet from data link layer.
‎• Connect devices physically. ‎• Focuses on LAN/MAN management
‎• Cables: ‎4. IEEE LAN/MAN Model:
‎1. Packetizing: ‎• At destination: ‎• Decapsulates it.
‎• Examples: Fiber optic, twisted pair, etc. ‎• Strongly based on OSI
•‎ Delivers the payload to the appropriate
‎upper layer protocol. ‎• Concerned with OSI layers 1 & 2

•‎ Routers do not change source/destination ‎• Object (managed entity)

‎addresses.
‎1. Organization Model: ‎• Defines components and their roles: ‎• Agent (collects data)

‎• Manager (processes data and controls)

•‎ Specifies how management data is

‎structured and stored

‎2. Information Model: ‎• SMI (Structure of Management Information)

‎• MIB (Management Information Base)

•‎ Defines communication between network

‎management entities:
‎OSI Network Management Model:
•‎ Management application processes (
‎3. Communication Model: ‎application layer)

‎• Layer management (between layers)

‎• Layer operation (within layers)

‎• Five main functions:

‎1. Configuration

‎2. Fault management

‎4. Functional Model (FCAPS):
‎3. Performance monitoring

‎4. Security control

‎5. Accounting and resource usage

•‎ Concerned with structure and storage of

‎management data.

•‎ SMI (Structure of Management Information):

‎syntax and semantics of management data.
‎Information Model: ‎• Defines:
•‎ MIB (Management Information Base): virtual
‎DB used by agents and managers.

•‎ MIB: Virtual database with managed object

‎definitions.
‎MIB vs MDB:
•‎ MDB: Real database holding actual data for
‎management use.

•‎ Describes components and relationships in

‎network management.

‎• Network objects: hosts, hubs, routers.

‎• Managed
‎Organization Model: ‎• Objects can be:
‎• Unmanaged

‎Three-tier Model:
•‎ Manager ↔Agent/Manager ↔ Agent ↔
‎Managed Objects

‎Two-tier Model: ‎• Manager ↔ Agent ↔ Managed Objects