Professional Documents
Culture Documents
AIX 5L AU14 System Administration I Implementation Instructor PDF
AIX 5L AU14 System Administration I Implementation Instructor PDF
cover
AIX 5L
System Administration I:
Implementation
(Course Code AU14)
Instructor Guide
ERC 11.0
Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM® is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
AIX AIX 5L AS/400
CICS/6000 DB2 Domino
HACMP Hummingbird Infoprint
iSeries Language Environment Lotus
Magstar Micro Channel MVS
Network Station OS/2 POWER
POWER2 POWER GTO PowerPC
PS/2 pSeries Redbooks
Requisite RISC System/6000 RS/6000
SecureWay SP System/370
Tivoli
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.
The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without
any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer
responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While
each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will
result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
© Copyright International Business Machines Corporation 1997, 2005. All rights reserved.
This document may not be reproduced in whole or in part without the prior written permission of IBM.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
V3.1.0.1
Instructor Guide
TOC Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
TOC Unit 10. Working with the Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . 10-1
Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
10.1 Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
SMIT Volume Groups Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
List All Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
List Volume Group Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
List Volume Group Information (Physical Volumes) . . . . . . . . . . . . . . . . . . . . . . 10-16
List Volume Group Information (Logical Volumes) . . . . . . . . . . . . . . . . . . . . . . . 10-18
Add a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Add a Scalable Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Set Characteristics of a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Change a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Logical Track Group (LTG) Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Extending and Reducing Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
Remove a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
Activate/Deactivate a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Import/Export a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45
Advanced RAID Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47
Exercise: Working with LVM (Parts 1 and 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
10.2 Logical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53
Logical Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-56
Mirror Write Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
Striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Striped Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
Logical Volume Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
SMIT Logical Volumes Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
Show Logical Volume Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
Add a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-76
Remove a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-78
Set Characteristics of a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-80
List All Logical Volumes By Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-83
Show Logical Volume Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-85
Add Copies to a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-87
Reorganize a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-90
10.3 Physical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-93
Physical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
SMIT Physical Volumes Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-96
List Physical Volume Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
List Logical Volumes on a Physical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-100
List a Physical Volume Partition Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-102
Add or Move Contents of Physical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-104
Documenting the Disk Storage Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
qdaemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-22
The /etc/qconfig File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-25
Printer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-29
AIX Printer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-31
Configuring a Printer with a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-34
Selecting a Printer Type (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-36
Selecting a Printer Type (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-38
Printer Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-40
Add the Print Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-42
Remote Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-44
Client Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-46
Start lpd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-48
Add a Remote Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-50
Define the Print Server on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-52
Let's Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-54
Submitting Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-56
Listing Jobs in a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-59
Change Characteristics of a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-62
Removing a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-65
Managing Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-67
Understanding Queue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-69
Bringing Queues Up and Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-72
Managing Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-74
Cancelling Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-76
Job Priority Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-79
Holding a Job in a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-82
Moving a Job between Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-84
Printing-related Directories to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-86
Printing Problem Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-88
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-91
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-93
Exercise 19: Printers and Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-95
Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-97
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .X-1
TMK Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM® is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
AIX® AIX 5L™ AS/400®
CICS/6000® DB2® Domino®
HACMP™ Hummingbird® Infoprint®
iSeries™ Language Environment® Lotus®
Magstar® Micro Channel® MVS™
Network Station® OS/2® POWER™
POWER2™ POWER GTO™ PowerPC®
PS/2® pSeries® Redbooks™
Requisite® RISC System/6000® RS/6000®
SecureWay® SP™ System/370™
Tivoli®
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.
Duration: 5 days
Purpose
The purpose of this course is to enable students to install, customize,
and administer the AIX 5L V5.3 operating system in a multiuser
environment using pSeries systems.
Audience
Anyone responsible for the system administrative duties implementing
and managing AIX 5L V5.3 operating system on an IBM pSeries
system.
Prerequisites
The students attending this course should be able to:
• Log in to an AIX system and set a user password
• Execute basic AIX commands
• Manage files and directories
• Use the vi editor
• Use redirection, pipes, and tees
• Use the utilities find and grep
• Use the command and variable substitution
• Set and change Korn shell variables
• Write simple shell scripts
These skills can be acquired by taking the AIX 5L Basics course or
through equivalent AIX/UNIX knowledge.
Objectives
On completion of this course, students should be able to:
• Install the AIX 5L V5.3 operating system, software bundles, and
filesets
• Perform system startup and shutdown
Contents
• Introduction (Overview of pSeries)
• System Management Tools - SMIT and the Web-based System
Manager
• Software Installation and Management
• System Startup and Shutdown Devices
• Printers and Queues
• Managing Queues
• System Storage Overview
• Working with the Logical Volume Manager
• Working with File Systems
• Managing File Systems
• Paging Space
• Backup and Restore
• Security
• User Administration
• Scheduling
• Networking Overview
Curriculum relationship
This course should follow the AIX 5L Basics course. A basic
understanding of AIX environment and simple commands is
recommended before taking this course.
pref Agenda
Day 1
(00:30) Welcome
(00:25) Unit 1 - Introduction to pSeries/AIX System Administration
(00:10) Activity: su
(00:40) Unit 2 - AIX V5.3 Installation
(00:15) Activity: Configuration Assistant
(00:20) Unit 3 - System Management Interface Tool (SMIT)
(00:20) Exercise: Using SMIT
(00:30) Unit 4 - AIX Software Installation and Maintenance
(00:25) Exercise: AIX Software Installation
(00:10) Unit 5 - Configuring AIX Documentation
(00:10) Exercise - Information Center
(00:10) Unit 6 - WebSM
(00:20) Exercise: Configuring WebSM server
(00:30) Unit 7 - System Startup and Shutdown
(00:30) Exercise: System Startup and Shutdown
Day 2
(00:40) Unit 8 - Devices
(00:30) Exercise: Devices
(00:50) Unit 9 - System Storage Overview
(00:10) Let's Review: LVM Terminology
(00:30) Unit 9 (Cont)
(00:15) Activity: LVM Commands
(00:25) Unit 10 - Working With the Logical Volume Manager
(00:20) Activity: Volume Groups
(00:45) Unit 10 (Cont)
(00:40) Exercise: Logical Volume Manager
(00:35) Unit 11 - Working with File Systems
(00:20) Activity: Inodes and NBPI
Day 3
(00:35) Unit 11 (Cont)
(00:40) Exercise: Working with File Systems
(00:25) Unit 12 - Managing File Systems
(00:25) Exercise: Managing File Systems
(00:25) Unit 13 - Paging Space
(00:20) Exercise: Paging Space
(00:40) Unit 14 - Backup and Restore
Day 4
(00:20) Unit 14 (Cont)
(00:30) Exercise (optional) - Using tar and cpio
(02:45) Unit 15 - Security and User Administration
(00:35) 15.1 - Security Concepts
(00:25) Exercise: Security Files
(00:30) 15.2 - User Administration
(00:40) Exercise: User Administration
(00:25) 15.3 - Security Files
(00:10) Activity: Examine the Security Files
(00:25) Unit 16 - Scheduling
(00:30) Exercise: Scheduling
Day 5
(00:40) Unit 17 - Printers and Queues
(00:10) Let's Review
(00:25) Unit 17 (Cont)
(00:40) Exercise: Printers and Queues
(00:30) Unit 18 - Networking Overview
(00:40) Exercise: Networking
References
GA23-2674 Exploring IBM RS/6000 Computers
SG24-4690 A Technical Introduction to PCI-Based RS/6000
Servers
SG24-2581 Managing AIX on PCI-Based RISC System/6000
Workstations
SG24-5120 RS/6000 System Handbook
www.ibm.com/eserver/pseries
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Define terminology and concepts of IBM Sserver pSeries
systems
• List common configurations available for IBM Sserver
pSeries systems
• Describe the roles of the system administrator
• Obtain root access with the su command
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Optimized on
pSeries machines
Notes:
RISC history
The IBM Sserver pSeries systems use RISC processors and were formally called
RS/6000 systems, where the RS stood for RISC System.
Reduced Instruction Set Computing (RISC) architecture was originally developed by
IBM in the 1970s. Its basic objective was to provide a reduced instruction set that would
execute very fast with maximum efficiency in the hardware. More complex instructions
would be implemented in the software.
POWER architecture
The simple RISC-based instruction is typically executed in one system clock cycle (or
less using superscalar techniques). IBM has enhanced the standard RISC technology
by introducing the newer Performance Optimized With Enhanced Risc (POWER)
Uempty architecture. The original POWER architecture has also evolved into the PowerPC,
POWER4, and POWER5 architectures.
The POWER architectures are designed with the newest in circuitry engineering and
multiprocessor technologies and yield very fast performance.
The instructions are handled in a superscalar (parallel) fashion by the processor which
further increases the performance offered by a RISC system.
64-bit architecture
Support for 64-bit architecture has been provided since AIX V4.3. This support provides
improved performance for specialized applications with:
- Large address spaces (up to 16,384,000 terabytes)
- Access to large datasets for data warehousing, scientific and multimedia
applications
- Long integers in computations
A major enhancement to AIX since AIX 5L V5.1 was the introduction of the 64-bit
kernel. Server consolidation and workload scalability will continue to require higher
capacity hardware systems that support more memory and additional I/O devices. The
64-bit AIX 5L kernel is designed to support these requirements.
The 32-bit and the 64-bit kernel are available. Only 64-bit CHRP-compliant PowerPC
machines are supported for the 64-bit kernel on the POWER platform. The primary
advantage of a 64-bit kernel is the increased kernel address space allowing systems to
support increased workloads. This ability is important for a number of reasons:
- Data sharing and I/O device sharing are simplified if multiple applications can be run
on the same system
- More powerful systems will reduce the number of systems needed by an
organization, thereby reducing the cost and complexity of system administration
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the relationship between the internal hardware architecture and RISC
concepts.
Details — This page is meant as an introduction. Do not go into too much detail on
hardware. Other courses, such as Q1316/AU16 discuss hardware in more detail.
The first RISC system was developed in 1975 at the IBM T.J. Watson Research Center as
a spin-off of telephone switching research. In 1986, IBM introduced the first system to use
RISC technology - the PC RT. AIX was announced at this time as well as the operating
system for the PC RT. The PC RT is often thought of as the first generation of RISC
systems.
The RS/6000 systems, introduced in 1990, are often thought of as the second generation
of RISC systems. AIX V3 was introduced as this time. The latest update of this course
reflects AIX 5L V5.3.
Since October 2000, new servers with UNIX operating systems have been introduced by
the name of IBM Sserver pSeries systems.
Of course, IBM offers many systems, from smaller personal systems and workstations up
to the Scalable PowerParallel (SP) systems.
The added information on superscalar is for interest purposes only. Systems that are
designed to handle multiple instructions simultaneously are called superscalar.
The student notes also mention AIX V4.3 64-bit support. The greatest potential
performance benefit of 64-bit addressing is the ability to handle very large address spaces.
In order to use the 64-bit capability, the RS/6000 processor must be capable of supporting
this enhancement. The IBM S70 was announced in October of 1997 to provide 64-bit
support. Since AIX V4.3 the operating system allows users to write their own 64-bit enabled
applications. Note also, that since AIX 5L V5.1, the full 64-bit kernel was made available for
POWER systems.
Additional Information — It should be noted that the advantages of 64-bit addressing
capability come with a cost. Extra addressability must be accompanied by very large
amounts of system memory to work effectively and memory is not inexpensive.
Applications compiled in 64-bit mode also consume more disk space than their 32-bit
equivalents.
Also, AIX 5L V5.3 supports two hardware architectures:
• 32-bit POWER architecture
• 64-bit POWER architecture
The 64-bit kernel is available for 64-bit POWER. Older 32-bit architecture is supported by
the 32-bit kernel. The 64-bit POWER hardware gives you the choice of running a 32-bit or
64-bit kernels.
Transition Statement — The next page talks about the IBM Sserver pSeries system bus
types.
Uempty
pSeries System Bus Types
PCI
ISA
PCI Bus
Notes:
Introduction
The job of the bus is to provide the highway for information to flow between the IBM
Sserver pSeries system elements and the optional I/O feature cards (for example,
SCSI adapters, token-ring cards) that are plugged into the adapter slots.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Workstation Configuration
Notes:
Overview
One common configuration for the IBM Sserver pSeries systems is as a single-user
graphical workstation suitable for graphics applications, such as CAD/CAM.
In this configuration, the IBM Sserver pSeries system has a graphical display (referred
to as an LFT - Low Function Terminal) which is attached to a graphics adapter inside the
system unit. A keyboard, mouse, and optional graphics tablet are plugged into special
ports on the system board.
There are a number of graphics cards available for the different IBM Sserver pSeries
models which differ in speed, resolution, number of colors supported, 2D or 3D support,
and so forth. There are corresponding displays that can be used from personal
computer displays through to the 23-inch PowerDisplay.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Server Configurations
Multiuser System
pSeries ASCII Terminals
System Unit
Async Adapter
Networked System
Server Clients
Network File Transfer
Management
Disk storage PCs
Printers Mail
Programs Network
Login Sessions
Documentation
pSeries pSeries
Other systems
© Copyright IBM Corporation 2005
Notes:
Overview
Some multiuser systems consist only of ASCII terminals connected locally or over a
telephone line by modem. Two ASCII devices can be connected to the serial ports
provided on IBM Sserver pSeries systems. All further ASCII devices will require an
asynchronous adapter card.
More complex systems consist of many IBM Sserver pSeries systems and other
devices such as PCs connected over a local area network (LAN) like Ethernet or token
ring. In this case, the IBM Sserver pSeries system requires the appropriate
communications adapter card.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
PC Connectivity
pSeries
PC
Network
X Window X Window
Client Server
Programs Software
Notes:
Overview
Very commonly, IBM Sserver pSeries systems are accessed via a network using PCs.
One way to connect is using telnet. Another method, which is growing in popularity, is
to install software on the PC to give the PC the capability to function as an X-Window
Server. This allows the PC to function as a graphics display station for the IBM
Sserver pSeries system. There are many commercially available software packages
for several different operating systems that provide this functionality.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Uniprocessor (Uni)
SSA
Adapter
Cache Processor
Memory Cards
Notes:
Overview
The term uniprocessor refers to a machine with only one processor. The processor is
connected to the memory and other adapters via the bus. Today, the I/O buses are
based on the Peripheral Component Interconnect (PCI) architecture.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Interconnect
CPU
1
CPU
2 ... CPU
n
... ...
Multiple processors accessing Loosely-coupled processors
the same memory and all disk linked by high-speed interconnect
SMP Cluster 1600
Notes:
Introduction
The Symmetric MultiProcessor (SMP) architecture supports a single copy of the
operating system which is shared by all processors. Memory and disk are also shared.
IBM Sserver pSeries SMP models support both PCI and MCA buses and can support
up to 24 processors. Beginning with AIX 5L V5.2, MCA architectures are no longer
supported.
Uempty 1600 can incorporate the regular IBM Sserver pSeries models up to and including
p690 machines.
Each Cluster 1600 node has its own memory, operating system, expansion slots, and
disk. A high-speed network called the SP Switch (up to 480 MB/sec.) is available to
connect the nodes together. The Cluster 1600 uses the Parallel System Support
Programs (PSSP) to control its environment.
The Cluster 1600 system is ideal for any parallel computing, high CPU-usage (such as
modeling and numerical analysis) and I/O-intensive applications (such as Data Mining,
OLTP, DB2/PE and Oracle Parallel Query/Server).
Cluster 1600 is also commonly used in an HACMP (High Availability Cluster
Multi-Processing) situation where better physical isolation is desired than can be
provided with an LPAR solution.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the concepts of SMP and SP (cluster 1600).
Details — Don't spend a lot of time on this as SMP and SP are covered in other courses.
However, many of the students attending this class may be using one of these systems.
Note that SMP nodes are also available on the SP.
Examples of IBM RS/6000 systems supporting the SMP environment are the 43P-240 (1-2
way), M80 (2-8 way), F50 (1-4 way), H50 (1-4 way), the S70 (4, 8 or 12 way), and the S80
(6-24 way). Most servers support 64-bit applications (64-bit capability has been supported
since AIX V4.3).
Additional Information — The student notes mention the speed of the SP Switch. It has a
rated hardware speed of up to 480 MB/sec. However, when using TCP/IP for
communications, the limitations of this protocol will produce a top speed of about 75
MB/sec. To take advantage of the rated speed of the SP Switch, some customers forego
TCP/IP and instead use Message Passing Interface (MPI) programming.
Transition Statement — Let’s look at one more very common configuration: an LPAR
machine.
Uempty
Logical Partitioning (LPAR)
Interconnect
PPPPP PPPPPPP
PP PPP
PPPPP PPPPPPP
MM MM
MMM MMMMMMM
AAAA AAAA
AAAAAA AAAAAAAAAAAAA
A = Adapter
M = Memory
P = Processor
= Disk
© Copyright IBM Corporation 2005
Notes:
Introduction
This visual illustrates that LPARs can have resources allocated based on the needs of
the workload rather than the amount contained in a physical building block. In the
diagram above, there are four partitions, each with various amounts of resources.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
means the partitions must be reactivated (that is, rebooted) to change the resource
configuration.
When memory is moved from one partition to another with dynamic LPAR, memory is
written to all zeroes by the system firmware. Likewise, I/O adapters are fully reset when
moved.
Allocating disks
Disks are not allocated to partitions individually. Instead, the I/O slot containing the
adapter controlling one or more disks is allocated to a partition.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
There are a number of distinct tasks which the system administrator on a UNIX or AIX
system must perform. Often there will be more than one system administrator in a large
organization, and the tasks can be divided between the different administrators.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
$ su root
or
$ su - root
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the importance of the root ID and keeping it secure.
Details —
Additional Information — Students will have an opportunity to experiment with su in the
first activity.
Transition Statement — Time for a checkpoint.
Uempty
Checkpoint
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
1. What type of adapter are you likely to require for a single-
user graphics workstation?
a. Asynchronous
b. Communications
c. Graphics
Additional Information —
Transition Statement — Now, let’s do an exercise using the su command.
Uempty
Exercise 1: root Login Methods
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Do the su exercise.
Details —
Additional Information —
Transition Statement — Now, let’s summarize the unit.
Uempty
Unit Summary
• Common Configurations
– Single-user graphics workstation
– Multiuser ASCII
– Networked system
– X Window-enabled PC
– SMP
– SP
• System Administrator's Role:
– Pre-installation planning
– Install hardware, software, network
– Manage user accounts, system resources, licenses
– Backup/recovery
– Define subsystems
– Performance monitoring, capacity planning
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 1. Introduction to IBM Sserver pSeries Systems and AIX 1-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — Now, onto the next unit.
References
SC23-4374 AIX 5L Version 5.1 Installation Guide
SC23-4389 AIX 5L Version 5.2 Installation Guide
SC23-4887 AIX 5L Version 5.3 Installation Guide
GI10-0729 AIX 5L Version 5.1 Release Notes
GI10-0739 AIX 5L Version 5.2 Release Notes
GI10-0756 AIX 5L Version 5.3 Release Notes
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Installation Methods
CD-ROM
Tape (Not available for AIX 5L installation)
4 mm
8 mm
Preinstallation Option (for a new system order)
Network Installation Manager (NIM)
Token Ring
Ethernet
FDDI
Notes:
Required memory
In AIX 5L V5.2 and AIX 5L V5.3, 128 MB of RAM is required to install the Base
Operating System (BOS).
In AIX 5L V5.1, 64 MB of RAM is required to install the Base Operating System.
Platform type
Beginning with AIX 5L V5.2, the Common Hardware Reference Platform (CHRP) is the
only supported platform. Execute bootinfo -p to get your hardware platform and
bootinfo -y to check, if you have a 64-bit or a 32-bit machine. A 64-bit machine can
run the 64-bit kernel as well as the 32-bit kernel.
Preinstallation option
The preinstallation option is only valid if accompanied by a hardware order that includes
the preinstalled AIX.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the BOS install source devices.
Details — You do not have to explain all the following details to the students, however it is
useful for the instructor. Cover as much of the following as you feel necessary.
CD-ROM:
• Requires only 8 MB of RAM with AIX V4.1 and V4.2; 32 MB of RAM with AIX V4.3.
• Packaged in a file system format
• Mounted over a directory /SPOT
• AIX 5L V5.3 requires 128 MB of RAM
Tape:
• Requires 16 MB of RAM with AIX V4.1 and V4.2; 32 MB of RAM with AIX V4.3; 64 MB
of RAM with AIX 5L V5.1 and 128 MB of RAM with AIX 5L V5.2 or V5.3.
• Data blocks:
- File 1 - Boot image
- File 2 - BOS install programs
- File 3 - Table of contents (TOC)
- File 4 - backup-format file images for products
You could also mention at this point that with AIX V4 and later booting from diskettes is not
supported.
This unit will focus on installation of AIX on a standalone system, that is, a system that can
boot/start up by itself. For students interested in how to perform a NIM installation, refer
them to the Network Installation Management Guide and Reference.
For those students with preinstalled systems, instructions for completing the installation
can be found in the Startup Instructions for Preinstalled Systems, which is shipped with the
pSeries hardware.
Additional Information — The AIX 5L is only delivered on CD. Prior to AIX 5L V5.1 with
tape, each different software order is created separately. This process is referred to as
stacked tape because there are multiple installation images “stacked” one after another on
the tape.
The stacked tapes are bootable and provide all of the menus necessary to install the BOS
either from the distributed tape or from an installation server machine across a network.
Once the BOS is installed, the same tape can be used to install the various optional
software products.
A complete system image backup tape can be created which is in a similar format to a
stacked tape; that is, it is bootable and can be used to install the system.
In AIX 5L V5.1, the memory requirements have been increased to 64 MB of RAM for
installation from CD and in AIX 5L V5.2 or V5.3 up to 128 MB.
Transition Statement — Let's next look at the steps necessary to install AIX 5L V5.3.
Uempty
Installation Process (From CD)
Insert CD in CD-ROM drive
Power on system
Press <F5>
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
NEXT:
Select the language
for installation
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the console and the installation language.
Details — After a few minutes into the boot process, the console message will be
displayed on the screen attached to port S1 (serial port 1) and also to all native graphics
screens. Point out that the message will be subtly different depending on the type of
screens that you have connected (that is, ASCII or graphics). On a graphics terminal, you
will need to press <F1> and then <Enter> to make it the system console. If you wish to
have an ASCII terminal as the system console, press 2 and then <Enter>.
Explain that the console can be thought of as a bucket which the system uses and sends
messages to every time it has something to say. Also, if the system is in single-user mode,
this will be the only terminal (by default) that will be available.
The settings that have been highlighted must be set through the setup menus (for example,
on an ibm3151 to obtain the setup menus, you must press the <Ctrl><Setup> keys and
follow directions).
To set the installation language, select one of the eight choices. Note that this message
only appears on the console (which you have just defined). The language that you select
will be used only during the installation process.
There are separate options which have to be set to establish the language for the
environment after the installation process has completed.
Note: Only single-byte character set locales can be chosen as an installation language.
Additional Information —
Transition Statement — After the definition of the console and the language, the
Welcome to the Base Operating System Installation and Maintenance menu will be
displayed. Let's see what values can be set from this screen.
Uempty
Installation and Maintenance Menu
At the Installation and Maintenance menu check all the
installation settings:
Type the number of your choice and press Enter. Choice indicated by >>>
88 Help ?
99 Previous Menu
>>> Choice [1]: 2
Notes:
Overview
To confirm or change the installation and system settings that have been set for this
system, type a 2 and press <Enter>. Select 88 to display help on this or any
subsequent installation screen.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Consider the options from the Installation and Maintenance menu.
Details — The first option will start the installation using the default settings. If, however,
you wish to view and possibly alter the current settings, then you need to select the second
option, which will be discussed in this unit.
The third option allows for maintenance tasks such as going into a maintenance shell,
copying the system dump, carrying out an image backup, and so forth.
Additional Information —
Transition Statement — For an initial installation, it is recommended to chose option 2, to
verify that the settings are what you want. Let's choose this option.
Uempty
Installation and Settings
Installation and Settings
Either type 0 or press Enter to install with current settings, or type the
number of the setting you want to change and press Enter.
1 System Settings:
Method of installation ...................... New and Complete Overwrite
Disk where you want to Install ........ hdisk0
Notes:
Overview
The Installation Settings screen allows you to:
- Set the type of installation:
• Migration
• Preservation
• New and Complete Overwrite
- Determine the installation disk
- Set the primary language environment
- Set more options
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — View the installation settings menu.
Details — Use this visual as a spring-board to the following four visuals which show how
the system settings (option 1) and the primary language environment (option 2) can be
changed. The third option includes the desktop type, Trusted Computing Base, and other
optional software.
The Installation and Settings screen displays the default installation settings for your
system. The default settings are determined by the state of your system.
Additional Information —
Transition Statement — Let's first consider option 1, the different methods of installation.
Uempty
Method of Installation
Option 1 of the Installation and Settings menu:
2 Preservation Install
Preserves SOME of the existing data on the disk selected for installation.
Warning: This method overwrites the user (/usr), variable (/var), temporary
(/tmp), and root (/) file systems. Other product (application) files and
configuration data will be destroyed.
3 Migration Install
Upgrades the Base Operating System to current release. Other product
(application) files and configuration data are saved.
88 Help ?
99 Previous Menu
>>> Choice [2]: 1
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Preservation Install
Use the Preservation Install method when a previous version of BOS is installed on
your system and you want to preserve the user data in the root volume group. This
method removes only the contents of /usr, / (root), /var and /tmp. The Preservation
Install option preserves page and dump devices as well as /home and other
user-created file systems. System configuration has to be done after doing a
preservation installation.
Migration Install
Migration prior to AIX V4.2.1 is not supported. Use the Migration Install method to
upgrade an AIX V4.2.1 or later system to an AIX 5L version, while preserving the
existing root volume group. This method preserves all file systems except /tmp, as well
as the logical volumes and system configuration files. Obsolete or selective fix files are
removed. Migration is the default installation method for an AIX system running Version
4.x.
The installation process determines which optional software products will be installed.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Installation Disks
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
There are times when you may want to reuse a disk that previously contained some
sensitive material and you want to be sure that information is no longer accessible.
If this is an overwrite installation, you can specify to erase the disks chosen to be
installed before the installation occurs by typing 55 and pressing the <Enter> key for the
More Disk Options option shown on the previous visual.
Uempty This menu also prompts for the patterns to be used for each disk erasure. The patterns
are a choice of the hexadecimal values 00,a5,5a, or ff. For example, a pattern of 00 will
write all zeros to the drive. Erasing a drive is a time-consuming process and only drive
types that are supported by the diag command can take advantage of this option (for
example, erasure of IDE drives are not supported).
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the use of the new disk erasure option.
Details — The purpose of multiple overwrites and the use of different patterns is to further
obscure any residual magnetic pattern from which the original data might be reconstructed.
Additional Information —
Transition Statement — After completing the System Settings, we then have an
opportunity to set the Primary Language Environment.
Uempty
Primary Language Environment
Option 2 of the Installation and Settings menu:
Type the number for the Cultural Convention (such as date, time, and
money), Language and Keyboard for this system and press Enter, or type 106
and press Enter to create your own combination.
88 Help ?
99 Previous menu
Choice [1]:
Notes:
Overview
At this point in the installation process, you can change the language and cultural
convention that will be used on the system after installation. This screen might actually
display a number of language options, such as French, German, Italian, Byelorussian,
Ukrainian, and so forth.
It is recommended that if you are going to change the language, change it at this point
rather than after the installation is complete. Whatever language is specified at this
point is obtained from the installation media.
Cultural convention determines the way numeric, monetary, and date and time
characteristics are displayed.
The Language field determines the language used to display text and system
messages.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define how the primary language environment after the installation is set.
Details — The visual shows the list of language environments that can be selected. The
environment will be governed by three settings:
• Cultural Conventions which will govern such things as the date format, the monetary
symbol, the sorting collation order, and so forth
• Language which will set the language for the messages
• Keyboard which will govern the character set that is available
In reality, this screen will display many language options. Users can also create their own
specific combinations by typing 67.
If English (United States) is chosen, a second menu is displayed. On this menu,
choose the type of keyboard being used: 1 for the default keyboard and 2 for the 122-key
keyboard.
Point out that "C(POSIX)" is an English based POSIX standard compliant language
environment. This is often sufficient for many systems.
Additional Information — The language in which the system will be run should be
selected at this point, if at all possible. If a different language is needed after installation is
complete, the install media needs to be available in order to install the appropriate new
language filesets. If the language filesets are not found, an error message is generated but
the change looks like it occurred successfully. However, when the system is rebooted the
console will not be able to come up because the system can't find the language information
it needs to send messages to the console. The system appears to boot correctly but there
is no terminal access. To recover from this condition, the system will have to be booted in
service mode from external bootable media and the language set back to a supported
language environment.
Transition Statement — Now, let’s look at the advanced options that can be set.
Uempty
Install Options for 32-bit Machines
Option 3 of the Installation and Settings menu:
Install Options
Either type 0 and press Enter to install with current settings, or type the
number of the setting you want to change and press Enter.
1 Desktop .................................................................... CDE
2 Enable Trusted Computing Base........................... No
3 Import User Volume Groups................................... Yes
4 Graphics Software..................................................... Yes
5 Enable System Backups to install any system...... Yes
(Installs all devices and kernels)
Notes:
Desktop
The screen shown is what is presented if running on a 32-bit hardware platform.
The first prompt is either:
- Installation Package Set for ASCII consoles
Options are Minimal or Default
- Desktop for graphical consoles
Options are CDE, Gnome, KDE, or NONE
The example in the visual has a graphical console.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Graphics Software
The Graphics Software option is available in a New and Complete Overwrite
installation, as well as Preservation installation. It will install graphics software support.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
1 Desktop..................................................................... CDE
2 Enable Trusted Computing Base........................... No
3 Enable CAPP and EAL4+ Technology.................... No
(English only, 64-bit kernel enablement, JFS2 file systems)
4 Enable 64-bit Kernel................................................. Yes
5 Create JFS2 File Systems........................................ Yes
6 Graphics Software.................................................... Yes
7 Enable System Backups to install any system...... Yes
(Installs all devices and kernels)
>>> 8 Install More Software
0 Install with the current settings listed above.
88 Help ?
99 Previous Menu
>>> Choice [8]: _
© Copyright IBM Corporation 2005
Notes:
Introduction
If you are installing on a 64-bit hardware platform, the installation software detects that
and presents some additional installation options.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Provide additional information on the 64-bit installation options.
Details — Focus on the additional options provided on the 64-bit machines.
Additional Information —
Transition Statement — Let’s look at what additional software we can install at this point.
Uempty
Install More Software
Either type 0 and press Enter to install with current settings, or type the
number of the setting you want to change and press Enter.
88 Help ?
99 Previous Menu
Notes:
Overview
The Install More Software option is available in the New and Complete Overwrite
installation method, as well as the Preservation installation method. Select Install More
Software to choose additional software to install after the BOS installation process
finishes. A software bundle file corresponds to each selection that contains the required
packages and filesets.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the options on the Install More Software screen.
Details — The software bundles available are:
• Mozilla - Mozilla Web browser
• Kerberos_5 - Kerberos
• Server - Server filesets
• While we select the default desktop environment on the previous panel, here we have
the choice to install the software for alternate desktop environments.
Kerberos is a popular method for authenticating a client to a service it wishes to use. It
avoids transmitting passwords in clear text by using private keys to encrypt tickets which
are passed between the principals that participate in the security domain.
Additional Information —
Transition Statement — Now that all the selections have been made, the installation
process begins. Let’s look at the status indicator.
Uempty
Begin Installation
Please wait . . . . . .
Notes:
Overview
The installation media contains information stored on it to determine the sizes that the
standard AIX file systems have. These are set large enough for the installation to
succeed but do not leave much free space after installation. You can dynamically
increase the size of any of the file systems once AIX has been installed. If you are
installing from a system image backup tape, the file systems created are the same sizes
and names as those on the system when the tape was created.
The files are restored from the media and then verified. This takes some time but can
be left unattended. After the BOS has installed, the appropriate locale optional program
will also be installed.
Once the installation has completed, the system automatically reboots from the newly
installed operating system on disk.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the status indicator screen.
Details — A number of tasks are performed to complete the installation including creating
a new boot logical volume, and customizing the locale and console information into the
newly installed operating system.
While the BOS is installing, the status indicator screen (as seen on the visual) is displayed.
The screen reports what percentage of the tasks are complete. Note that the percentage
indicator and the elapsed time are not linear; (that is, if it reports that 50% has completed in
four minutes, this does not indicate that the total installation time will be eight minutes).
All logical volumes and file systems are set to minimal standard sizes, but may be
increased later.
During the installation phase, only the software for the devices that are connected and
powered on will be installed. All other device software will be installed on demand.
Additional Information —
Transition Statement — Let's take a look at the 'big picture' of what occurs during the
installation of AIX.
Uempty
Installation Flowchart - All Systems
Start the system
Change:
Installation Method
Select the console
Destination Disks
Language
Select language
Install Options:
Begin
Desktop
with default TCB
settings? 64-bit/JFS2 (64-bit platform)
no Graphics Software
Import User Volume Groups
Verify default install
Enable System Backups
method and settings
yes
Default yes Install More Software:
settings need to be Mozilla
changed? Kerberos_5
Server
no GNOME Desktop
Install from media KDE Desktop
Perform customization
© Copyright IBM Corporation 2005
Notes:
Introduction
The flowchart in this visual summarizes the installation steps we have discussed.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Consider the complete flow of events for the installation process.
Details — This visual should be used as a summary for all the points that have been
discussed so far.
It can be used as a reference chart by the students.
Additional Information —
Transition Statement — Having installed the operating system, the system needs to be
customized. Let's view the options that can be set from this screen.
Uempty
Configuration Assistant Menu
Notes:
Introduction
After installing AIX, the operating system runs with default settings; one user (root), the
date and time set for where the system was manufactured, and other very general
settings. You probably want to change some or all of these settings. Also, you must
provide system and network information if you want to communicate with other
systems.
The Configuration Assistant and Installation Assistant provide step-by-step instructions
for completing each customization task. Examples of tasks that can be performed are
setting the system date and time, setting root's password and configuring the network.
Complete the tasks in the order that the Configuration Assistant / Installation Assistant
lists them. It is helpful to complete all customization tasks before you use your system.
If using a graphics terminal for the installation, the newly installed BOS reboots and
starts the Configuration Assistant, which guides you through completing customization
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
tasks. When you use the Configuration Assistant immediately after BOS installation,
you have at first to accept the license agreement and only the tasks that apply to your
type of installation will be shown.
If an ASCII terminal was used for the installation, an ASCII-based Installation Assistant
is displayed instead. Both the graphics-based Configuration Assistant and the
ASCII-based Installation Assistant provide comparable support.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. AIX 5L can be installed from which of the following:
(select all that are correct)
a. 8 mm tape
b. CD-ROM
c. Diskette
d. 4 mm tape
Notes:
Checkpoint Solutions
1. AIX 5L can be installed from which of the following:
(select all that are correct)
a. 8 mm tape
b. CD-ROM
c. Diskette
d. 4 mm tape
2. True or False? A Preservation Install preserves all data
on the disks.
Preserves SOME of the existing data on the disk selected for
installation. Warning: This method overwrites the user (/usr),
variable (/var), temporary (/tmp), and root (/) file systems. Other
product (application) files and configuration data are destroyed.
3. What is the console used for during the installation process?
The console is used to display all the system messages and
interact with the installation.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Now, let’s do an exercise with the Configuration Assistant.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Configuration
Assistant
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 2. AIX 5L V5.3 Installation 2-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4908 AIX 5L Version 5.3 System Management Concepts:
Operating System and Devices (Chapter 13)
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how system management tasks were carried out before
management tools were available.
Details — This visual should be used to illustrate the difficulties that would exist if tools
were not available to aid system administrators.
The goal in AIX V4 and AIX 5L has been to overcome many of the problems with the
traditional approach to system administration by providing a single consistent easy-to-use
interface for system management, while still providing administrators who are familiar with
and feel comfortable with the traditional methods the flexibility to continue using these
traditional methods, at least for most tasks.
Additional Information —
Transition Statement — What are the goals of today’s system management tools?
Uempty
System Management Objectives
• Minimize time and resources spent managing systems
• Maximize reliability, performance, and productivity
• Provide remote system management solutions
AIX
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
AIX Administration
Web-based
SMIT System
Manager
High-level commands
Low-level Intermediate-level
commands commands
System
System Kernel Object Data ASCII
Resource
calls services Manager files
Controller
Notes:
Overview of SMIT
The System Management Interface Tool (SMIT) provides a menu-driven interface that
provides access to most of the common system management functions within one
consistent environment.
SMIT does not perform any system management functions directly. It is a user interface
that constructs high-level commands from the user's selections and then executes
these commands on demand. Those commands could be entered directly by the user
to perform the same tasks.
SMIT does not cover every possible system management task, and occasionally there
will be a need to run AIX commands or edit ASCII files directly to complete a particular
system administration task. However, SMIT does make the most frequent or
complex/tedious tasks much easier with a greater degree of reliability.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the tools available for system management.
Details — We’re introducing two tools now, but only one of them (SMIT) will be covered in
detail in this unit. The Web-based System Manager will be discussed in more detail later in
the course.
The basic idea behind both tools is that they present the system administrator with a
menu-driven front end, with built-in help information and lists. These can be used to carry
out most system administrative tasks.
Depending on the menus selected and the options entered, the tools will build the
high-level command with all the correct options and will then execute the command when
the user specifies this action.
High-level commands in turn call on lower-level commands which interact directly with the
system, that is, the ODM, kernel, and so forth.
While SMIT has been around for a while, the Web-based System Manager was new with
AIX V4.3 and has been enhanced in AIX 5L. Traditionally, SMIT is used to administer the
system it is running on. The advantage of Web-based System Manager is that you can sit
at a PC or remote AIX system and perform system administration tasks on another AIX
system. While SMIT can be run in graphics or ASCII mode, the Web-based System
Manager can only be run in graphics mode. The Web-based System Manager will be
covered in more detail later in the course.
Additional Information —
Transition Statement — We’ll discuss the Web-based System Manager in more detail
later in the course. In this unit, however, we’ll focus on SMIT. Let's start by looking at the
components that make up the SMIT user interface.
Uempty
System Management Interface Tool (SMIT)
ASCII or AIXwindows (Motif) User Interface Components
menu help
submenu help
submenu
help
name selector
list
help
pop-ups dialog panel
list
output panel
© Copyright IBM Corporation 2005
Notes:
Available interfaces
SMIT provides a flexible user environment. The user can use an ASCII or an
AIXWindows-based interface. These interfaces provide the same facilities, but the
interaction is slightly different.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Use of keys
In the ASCII mode, in order to select from the menus, you have to use the up and down
arrow keys. This moves a highlighted bar over the menu items. Press <Enter> to select
the highlighted item.
You can also use some of the keyboard function keys to perform other functions, such
as exiting SMIT or starting a shell.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Illustrate the SMIT ASCII version of a menu screen.
Details — The visual shows the very first menu which will be seen if the command smit is
entered with no options.
Point out that there are function keys with each type of screen. However, we are not
showing the complete set here. You could consider the ones listed on this visual now, or
leave them to be considered until later when a complete list is provided in the student
notes.
Additional Information — Many times, when using SMIT in the ASCII mode, the menus
and dialog panels come up distorted. That is the result of not having an appropriate TERM
variable value. Setting and exporting this variable can solve the problem. For example,
executing export TERM=vt320 might solve the problem. See documentation for the tic
command (in the AIX 5L Version 5.3 Commands Reference) and the terminfo directory (in
the AIX 5L Version 5.3 Files Reference) for details on terminal types and the terminfo
database which is used by curses-based user interfaces.
Transition Statement — Let's look at the AIXWindows version of the same menu.
Uempty
SMIT Main Menu (Motif)
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Dialog Screen
Schedule a Job
[Entry Fields]
YEAR [05] #
MONTH [Jun] +
DAY (1-31) [22] #
* HOUR (0-23) [] #
* MINUTES (0-59) [] #
SHELL to use for job execution Korn (ksh) +
* COMMAND or SHELL SCRIPT (full pathname) []
Notes:
Special symbols
Special symbols on the screen are used to indicate how data is to be entered:
* This is a required field
# A numeric value is required for this field
/ A pathname is required for this field
X A hexadecimal value is required for this field
? The value entered will not be displayed
+ A pop-up list or ring is available
An * symbol in the leftmost column of a line indicates that the field is required. A value
must be entered here before you can commit the dialog and execute the command.
In the ASCII version, a + is used to indicate that a pop-up list or ring is available. To
access a pop-up list, use the F4 key. A ring is a special type of list. If a fixed number of
options are available, the Tab key can be used to cycle through the options.
In the Motif version, a List button is displayed. Either click the button or press <Ctrl-l>
to get a pop-up window to select from.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
F8 (or ESC-8) Image - save the current screen to a file (A) and show the
current fastpath
F9 (or ESC-9) Shell - start a sub-shell (A)
F9 Reset all fields (M)
F10 (or ESC-0) Exit - exit SMIT immediately (A)
F10 Go to command bar (M)
F12 Exit - exit SMIT immediately (M)
Ctrl-l List - give a pop-up list of possible values (M)
PgDn (or Ctrl-v) Scroll down one page
PgUp (or ESC-v) Scroll up one page
Home (or ESC-<) Go to the top of the scrolling region
End (or ESC->) Go to the bottom of the scrolling region
Enter Do the current command or select from a single-selection
pop-up list
/text Finds the text in the output
n Finds the next occurrence of the text
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Output Screen
Command: OK stdout: yes stderr: no
[TOP]
UID PID PPID C STIME TTY TIME CMD
root 1 0 4 20:15:04 - 1:49 /etc/init
root 1719 1 0 20:16:14 - 0:10 /etc/syncd 60
root 2003 1 0 20:16:19 - 0:00 /etc/srcmstr
root 2233 1 0 17:16:14 - 0:00 /usr/lib/errdemon
ray 3525 1 0 20:01:28 0 0:00 -ksh
root 3806 2003 0 19:16:23 - 0:00 /etc/syslogd
ray 4162 3525 6 20:53:22 0 0:04 smit
root 5355 1 0 20:16:27 - 0:12 /etc/cron
root 6649 2003 0 20:16:32 - 0:00 qdaemon
ray 7303 4162 8 20:09:45 0 0:00 ps -ef
[MORE...6]
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
SMIT
smit.script
List of
commands
• $HOME/smit.log
Keeps a log of all menu and dialog screens visited, all
commands executed and their output. Also records any errors
during the SMIT session.
• $HOME/smit.script
Shell script containing all AIX commands executed by SMIT.
Notes:
Overview
SMIT creates two files in the $HOME directory of the user running SMIT. If these files
already exist, then SMIT will append to them. These files can grow quite large over
time, especially during installations, so the user must maintain them and truncate them
when appropriate.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the log files associated with SMIT.
Details — Since SMIT is a tool that can be executed by all users, all users that execute the
smit command will have these files created in their $HOME directory. Users must regularly
monitor and truncate these files so that disk space is not wasted.
The consideration mentioned above applies even more so for the system administrator
user accounts and for the root user, as these users will be frequently carrying out
operations through the tool.
The files can be used in a number of situations:
• Since all entries in the files are time stamped, these files are helpful in determining
when certain activities occurred on the system.
• The smit.script file contains the commands that have been executed, so these can be
used as the basis of creating shell scripts
We will see in the next visual how you can specify different files to be used for logging.
Additional Information — All users can use SMIT. However, since SMIT just builds
commands, whether someone can successful run something through SMIT depends on
whether they could run the same task from the command line. For example, any user can
display all of the processes running on the system because they can run the ps command
from the command line. But, a regular user cannot add a user account through SMIT, just
as they cannot successfully run the mkuser command from the command line.
In AIX 5L V5.3, smit now creates an additional output file: $HOME/smit.transaction. This
new file is always created in the home directory. It is created to provide some consistency
with the Web-based System Manager which creates a $HOME/websm.transaction file.
While basically the same in format and usage as the smit.script file, smit.transaction is
supposed to only include the final cmd_to_exec and none of the cmd_to_discover,
cmd_to_list, and so forth, output which might be included in smit.script. As of this writing,
the smit.transaction file is an undocumented feature of the smit command, though a
discussion of it can be found under APAR IY40249. This feature is included in
AIX 5L V5.2.0.0 ML02 and later.
Transition Statement — Let's consider some different options that can be used when
running SMIT.
Uempty
smit Command Options
• General syntax:
smit [-options] [ FastPath ]
Notes:
Introduction
The command smit is used to invoke SMIT. It is not particularly common to run smit
with any options, although a number of them do exist. Some of the more commonly
used options will be described here.
Using a fastpath
Using a SMIT fastpath can be very helpful. Fastpaths are names that specify individual
screens within SMIT. If you want to by-pass the menu system and go straight to a
particular screen, use the command smit fastpath. When using SMIT, you can view
the fastpath screen name (for the current screen) by pressing F8 (or Esc+8) - Image.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. Specify the SMIT function keys that can be used for the
following:
a) List the command that will be run: ____
b) List the screen name which can be used for the
fastpath: ____
c) Take a screen image: ___
d) Break out into a shell: ___
e) Return to the previous menu: ___
2. Specify two ways you can request the ASCII character
version of SMIT from an X-windows environment
command prompt:
• ________________
• ________________
Notes:
Checkpoint Solutions
1. Specify the SMIT function keys that can be used for the
following:
a) List the command that will be run: F6
b) List the screen name which can be used for the
fastpath: F8
c) Take a screen image: F8
d) Break out into a shell: F9
e) Return to the previous menu: F3
2. Specify two ways you can request the ASCII character
version of SMIT from an X-windows environment
command prompt:
• smitty
• smit -C
Additional Information —
Transition Statement — Now, it’s time for an exercise.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
This exercise allows you to get familiar with SMIT.
The exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 3. System Management Interface Tool (SMIT) 3-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4374 AIX 5L Version 5.1 Installation Guide
SC23-4389 AIX 5L Version 5.2 Installation Guide
SC23-4887 AIX 5L Version 5.3 Installation Guide
GI10-0729 AIX 5L Version 5.1 Release Notes
GI10-0739 AIX 5L Version 5.2 Release Notes
GI10-0756 AIX 5L Version 5.3 Release Notes
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Define the package definitions and naming conventions
• Identify how software products and updates are installed
and managed on the system
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
AIX
LPPs
AIX documentation
Expansion Pack
Bonus Pack
Web Download Pack
Notes:
Introduction
The AIX 5L operating systems are delivered on multiple CDs. During the ordering
process, it is necessary to indicate the system type.
Licensed Program Products (LPPs) are separately orderable products that will run on
the AIX operating system.
The contents of the Expansion and Bonus Packs vary over time. Their purpose is to
acquaint users with tools and products that may be valuable in their business
environment.
For more details on either the Expansion Pack or the Bonus/Web Download Pack go to:
http://www.ibm.com/servers/aix/expansionpack
AIX documentation
The AIX 5L V5.3 documentation comes in a 2 CD set. It contains the full AIX
documentation library in many different languages, in addition to the infocenter run time
environment.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the AIX product offerings.
Details — AIX is delivered on multiple CDs. For example, AIX 5L V5.3 is delivered on 8
CDs. The Expansion Pack is delivered at no charge and includes products that may be
valuable in the customer's business environment.
Licensed Program Products (LPPs) are separately orderable products that the customer
may need such as DB2/6000, CICS/6000 and ADSM.
Additional Information —
Transition Statement — Let's take a look at the terminology that goes with the packaging.
Uempty
Packaging Definitions
LPP: Collection of packages
bos Complete product
package: package:
Collection of filesets
bos.INed bos.adt
Notes:
Package
A package contains a group of filesets with a common function. It is a single, installable
image.
Fileset
A fileset is the smallest individually installable unit. It is a collection of files that provides
a specific function. For example, bos.net.tcp.client is a fileset in the bos.net package.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the packaging terminology that the students may encounter.
Details — Make sure everyone understands the association of each of the definitions.
• Fileset - Smallest individual installable unit
• Package - Collection of filesets built to form one installable image; for example, bos.net
• LPP - One or more packages bundled together; for example, bos, SNA
Additional Information —
Transition Statement — One other item is used when discussing software, the term
bundle.
Uempty
Bundles
• A bundle is a collection of packages and filesets suited for a particular
environment
• Predefined system bundles in AIX 5L V5.3 include:
– AllDevicesKernels
– Alt_Disk_Install
– App-Dev
– CC_Eval.Graphics
– CDE
– GNOME
– Graphics
– KDE
– Kerberos_5
– Media-Defined
– Mozilla
– PerfTools
– Server
– cas_client and cas_server
– devices
– Infocenter
– openssh_client and openssh_server
– wsm_remote
© Copyright IBM Corporation 2005
Notes:
Overview
Since there are thousands of filesets, having to determine which individual fileset you
want on your machine could be a time-consuming task. AIX has bundles which offer a
collection of filesets that suit a particular purpose. For example, if you are developing
applications, the App-Dev bundle would be the logical choice to install.
Some filesets within a bundle will only be installed if the prerequisite hardware is
available. For example, a graphic adapter is needed to run AIXWindows.
In some cases, bundles are equivalent to product offerings. Often, however, they are a
subset of a product offering or a separate customized bundle. The bundles available
may vary from configuration to configuration and AIX version to AIX version.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the default system bundles.
Details — The standard bundle definitions that control what selections appear in SMIT or
the Web-based System Manager are stored in /usr/sys/inst.data/sys_bundles.
The following are examples of predefined bundles in AIX 5L V5.3:
• Application Development Bundle (App-Dev)
A collection of software packages used for developing application programs.
• Media-Defined Bundle (Media-Defined)
Filesets from the installation media.
• Other predefined system bundles are:
- CDE
- GNOME
- KDE
- devices
- wsm_remote
Additional Information — It is important to note that bundles do not themselves contain
any software packages or filesets, but are only a list of fileset names with references to the
appropriate media that will contain the software. When using a bundle definition to drive the
software installation process, you will be prompted to mount the correct installation media if
it is not already found in the drive.
Transition Statement — Let's see how filesets are named.
Uempty
Fileset Naming
bos.terminfo.print.data
Message convention:
LPP.msg[.lang].package.fileset
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Software Updates
# oslevel
5 . 3 . 0 . 0
Notes:
Introduction
As new software is created for AIX, you want to upgrade your system to maintain the
latest features and functionality.
The numerical information that shows what level of software you currently have
installed is broken into four parts:
- Version
- Release
- Modification
- Fix
You can see this using the oslevel command.
Types of upgrades
When you want to upgrade the system, how you do it depends on what type of upgrade
you are performing. Changes to the version or release levels require you to perform a
migration installation as discussion in the AIX 5L V5.3 Installation unit. If you want to
make a change to the modification or fix levels, use the smit update_all command.
These changes provide fixes to defects or additional functions to the BOS or optional
software products.
Version and release upgrades must be purchased. Modification and fix-level upgrades
are available at no charge. They are provided on CD (order via AIX Support Center) or
they can be downloaded from the Web. AIX updates are available at
http://www.ibm.com/servers/eserver/support/pseries/aixfixes.html. This Web site will be
discusses in more detail later in this unit.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the four parts of software components and use that information to
determine what type of software upgrade is needed.
Details — Explain that the oslevel command shows the current operating system level.
Explain the four parts of the numbering system:
• Version
• Release
• Modification
• Fix
Upgrades made to the version or release level come on bootable media and must be
purchased and installed using migration. You may want to take a minute to review the
procedures for performing a migration (This would be good place to generate interaction by
asking the student how to do this.)
Upgrades to the modification or fix levels are done using smit update_all.
The AIX documentation uses several terms referring to the same software upgrades.
Maintenance level, service update and software update all refer to the same thing. These
can be obtained via the Web.
Changes to the modification or fix levels are referred to as maintenance level updates or
service updates. They provide fixes to defects or additional functions to the BOS or optional
software products. Optional software products are any software product that do not install
with the BOS. Optional software products might be included with AIX or they might be
purchased separately.
Additional Information — This should provide some clarification for you. It doesn't need
to be discussed unless someone asks a question about this:
Following is an example of a fileset and a fileset update:
• bos.net.tcp.client 4.1.0.0 is a fileset. bos.net.tcp.client 4.1.0.1 is an update to that
fileset. If another fileset update, bos.net.tcp.client 4.1.0.2, is generated, this update
will contain all the fixes that were in the bos.net.tcp.client 4.1.0.1.
• If a cumulative AIX update is generated, the modification level of the fileset will
increment, resulting in bos.net.tcp.client 4.1.1.0, which would contain all previous
fixes.
• The old FixDist known from AIX V4.3 has been replaced by a Web interface.
Transition Statement — Once you are ready to begin your update or installation, there are
different software states that are used. Let's look at those.
Uempty
Software States
Applied:
FILESET 5.3.0.3
(New Version)
FILESET 5.3.0.1
Commit
Install or
5.3.0.3 (Old Version)
Reject
Applied FILESET 5.3.0.1
FILESET 5.3.0.3 (Old Version)
Committed:
Committed
Install FILESET 5.3.0.3
5.3.0.3
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The applied state gives you the opportunity to test the newer software before
committing to its use. If it works as expected, then you can commit the software which
will remove the old version from the disk.
If the newer version is causing a problem, you can reject it which removes the newer
version and recommits the old version.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
Use the SMIT fast path smit install to access the Software Installation and
Maintenance menu.
You can also use the Web-based System Manager to install software.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Install Software
Update Installed Software to Latest Level (Update All)
Install Software Bundle
Update Software by Fix (APAR)
Install and Update from ALL Available Software
Notes:
Introduction
Use the smit install_update fast path to access this menu.
Install Software
This option allows you to install or update to the latest level of software available on the
installation media. This allows you to install everything on the installation media if so
desired. This is most commonly used to install optional software not currently installed
on you system.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the Install and Update Software SMIT menu.
Details — Briefly mention each of the options. This menu is the starting point when
installing software or applying maintenance to the system.
We will not go into detail on each option. Mention the option Update Software by Fix
(APAR). This is one method of applying an APAR fix. Later in the unit, we will discuss the
instfix command which is another method of applying an APAR fix.
The option Install Software is often the only option that will work if installing specific
language and message sets.
Additional Information —
Transition Statement — From this SMIT menu, let's choose the first option, Install
Software. Before seeing the next screen, SMIT will ask that you to choose an input device,
such as the CD-ROM or tape. (The resulting menu is the same as would be shown if the
second option was chosen, Update Installed Software to Latest Level except the
software to install line will show with [update_all] instead of [_all_latest].
Uempty
Install Software
Install Software
Notes:
Introduction
The SMIT Install Software dialog screen allows you to install all or selected software
from the installation media. If any updates exist for these products, they are also
installed.
To perform an update_all, the SMIT screen will be identical except in the SOFTWARE
to install line you will see [update_all].
The input device is usually CD-ROM, tape or diskette. However, it is also possible to
install software that has already been loaded to disk. The directory
/usr/sys/inst.images can be used for this purpose.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
PREVIEW only?
The PREVIEW only? option allows you to preview the results of the installation without
actually performing the software install. The system displays information on space
requirements and a list of software products and updates that are installed.
License agreements
Beginning with AIX 5L V5.1, software license agreements are shipped and displayed
electronically, saving paper and allowing for electronic software distribution in the
future. If a product has an electronic license agreement, it must be accepted before
software installation can continue.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Software Inventory
# smit list_installed
List Installed Software and Related Information
lslpp command:
-L Lists the installed software
-h Shows the history of a software product
© Copyright IBM Corporation 2005
Notes:
Introduction
Use the SMIT fast path smit list_installed to access the List Installed Software
and Related Information menu. This menu provides information about the software
and fixes installed on a system.
Most of the SMIT options on this menu actually execute the lslpp command. The
following command options can be used to view specific software information:
-l Displays the name, level, state and description of the fileset
-h Displays the installation and update history for the fileset
-p Displays requisite information for the fileset
-d Displays dependent information for the fileset
-f Displays the names of the files added to the system during installation of the
fileset
-w Lists the fileset that owns a file
-b List software for the specified bundle name
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
The lslpp command is used to list the installed software on the system. The various
options of the lslpp command allow you to view selected information on the software
installed.
The output of the lslpp command displays the fileset name, the level of the product, its
state (applied or committed), and a description of the product.
Other options include:
-d Displays filesets that are dependents on the specified software
-f Displays names of files added to the system during the installation of specified
filesets
-p Lists requisite information for a specified fileset
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Fix Repository
Available updates
(from IBM Web site)
Fix repository
(locally stored Installed fixes
filesets)
Notes:
Overview
When working with modifications or fixes, it is common to download the fixes to a
directory on your local hard drive before installation. This location is commonly referred
to as the fix repository.
While /usr/sys/inst.images is a standard location for storing software images and will
appear in the SMIT Input Device/Directory (F4) list, you may choose to use any
directory for this purpose.
Managing the fix repository includes knowing how up to date it is relative to what is
available and what in the repository has been installed.
AIX provides a reporting facility to compare the installed software, repository software
and IBM Web site available software. Any two of these can be compared to obtain a
report.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
IBM Eserver support provides a Web site interface (Fix Central) to access fix
information. Two ways to navigate to this Web page are:
- Via Fix Central at www.ibm.com/eserver/support/fixes
Identify the Server as pSeries and Product or fix type as AIX operating system.
After clicking Continue, the screen shown in the visual is displayed.
- Go directly to the AIX Fix Central Web site:
www.ibm.com/servers/eserver/support/pseries/aixfixes.html.
Specific fixes
These are generally available fixes that resolve specific problems.
Click on the AIX version you are running. Then, on the next screen, you can select the
fixes by:
- Fileset or PTF number
- APAR number or abstract
Then, give it a search string.
Another screen will be displayed listing the fixes that have matched your criteria. Select
the fixes from the search results that you want to add and click Add to the download list.
Then, click Continue to go to the packaging options screen.
Emergency fixes
When resolution to a problem cannot wait for a generally available fix, IBM may provide
a way around the problem in the form of an emergency fix.
IBM provides a common method for installing and uninstalling emergency fix packages
for the AIX operating system. This solution uses integrated tools to ensure a seamless
and safe application of fixes and reduces the risk associated with installation of
generally available fixes onto systems that have emergency fixes installed.
The emergency fix management solution allows you to track and manage emergency
fixes on systems running AIX. The solution consists of the efix manager, the efix
packager and associated System Management Interface Tool (SMIT) screens.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Critical fixes
IBM periodically publishes information about generally available fixes that may apply to
your system.
Fixes identified as critical may also be classified as HIPER, PE, security or may warrant
special awareness.The information displayed can be helpful in determining if a fix
should be applied. However, parts or all of it may not be applicable to your environment.
Determine your system's AIX maintenance level by running the oslevel -r command,
then select the appropriate package. If your level is greater than what is seen in this list,
then IBM has not identified any critical fixes for your operating system level at this time.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Figure 4-15. More Fix Services Screen (from Fix Central) AU1411.0
Notes:
Introduction
Selecting More fix services on the previous visual’s screen, gives you the screen in
this visual. There are two sections:
- Automating downloads
- Compare report
Automating downloads
AIX 5L V5.3 introduces the Service Update Management Assistant (SUMA). You can
configure your system to periodically check for updates from IBM. This tool can be used
to automatically download the latest fixes for the operating system and cluster products.
While the bos.suma package was released with AIX 5L V5.3, the AIX 5L V5.1 and AIX
5L V5.2 SUMA packages and related updates have been made available for download
from the IBM support Web site. SUMA will be discussed later in this unit.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the two options available on the More fix services screen.
Details — Automated downloads (using SUMA) will be discussed later in this unit, just
introduce it here.
Additional Information —
Transition Statement — When you select the AIX version you’re interested in under
Compare report, you will see the screen shown on the next visual.
Uempty
Compare Report Screen (from Fix Central)
Notes:
Introduction
The Compare report screen shown in this visual is displayed after you click on the AIX
version you’re interested in from the More fix services screen shown in the previous
visual.
This process to compare software versions consists of three steps:
1. Download the data file from IBM’s Fix Central Web site
2. Run the compare_report command or smit compare_report on your AIX
system
3. Upload the file created by compare_report
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the Compare report screen.
Details — Identify the steps to compare software versions. This Compare report screen
will do the first and last steps. The next few visuals discuss the comparison reports.
Additional Information —
Transition Statement — Let’s look at how we can create reports for comparison of
software versions.
Uempty
Software Service Management
# smit service_software
Notes:
Introduction
The SMIT Software Service Management menu allows access to Service Update
Management Assistant (SUMA) functions, which significantly simplify the system
update process by allowing policy-based automatic downloads of maintenance updates
from the Web. The Software Service Management menu also allows generation of
reports to manage filesets installed on a system, filesets contained in a repository, and
filesets available from the IBM Fix Central Web site. It also provides a way to clean up
and rename software images in a repository.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
specific new fixes and entire maintenance levels, so that the time spent on such system
administration tasks is reduced. The SUMA implementation allows for multiple
concurrent downloads to optimize performance and has no dependency on any Web
browser.
SUMA policies can be run without extensive configuration. Filtering options allow
comparisons against an installed software inventory, a fix repository, or a maintenance
level to ensure only desired fixes will be downloaded. SUMA provides the option to
send an e-mail notification containing a list of what’s available for download, as well as
detailed summary statistics of a download.
SUMA can be accessed through the suma command or through the smit suma fast
path.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Comparison Reports
# smit compare_report
Comparison Reports
Notes:
Introduction
The SMIT Comparison Reports menu or the compare_report command allows you to
generate several comparison reports to verify that the filesets for a particular fix or
preventive maintenance package are installed by comparing filesets installed on a
system to another source. This source could be a fix repository, such as an lpp_source
or a directory of fixes, or a downloaded list from the IBM Fix Central Web site.
If you want to verify that your lpp_source is up to date, you can also compare a fix
repository to a downloaded list.
You can perform these actions in the smit compare_report fast path or using the
compare_report command.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The report that is generated contains information on filesets in the fix directory that are
back-level from latest (lowerthanlatest2.rpt).
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Flag Description
Specifies that no report files should be saved to disk. This flag is
-v
not valid with the -t or -Z flags.
The name of the file containing the software installed on the base
-b BaseRp
system (generated with lslpp -Lc).
The name of the file containing the software installed on another
-o OtherRp system that will be compared to a base system (generated with the
command lslpp -Lc).
Specifies a file that contains the list of available updates. This file
-r ServiceRp
can be obtained from the Fix Central Web site.
Transition Statement — Let’s look at the Software Maintenance and Utilities SMIT
menu.
Uempty
Software Maintenance and Utilities
# smit maintain_software
Software Maintenance and Utilities
Move cursor to desired item and press Enter.
Notes:
Overview
The fast path smit maintain_software allows you to commit, reject and remove
software. You will also find the other menu items useful.
Copying software
With the Copy Software to Hard Disk for Future Installation and Copy Software
Bundle to Hard Disk for Future Installation options, you can copy filesets from the
installation media to the hard drive without actually performing an installation. This
allows you to install it later without needing the original installation media. To Copy all
Software to Hard Disk for Future Installation use the following command:
# gencopy -d /dev/cd0 -t /usr/sys/inst.images all
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checking software
If you are experiencing problems with your software, the Check Software File Sizes
After Installation and Verify Software Installation and Requisites will check and
verify the system by analyzing it to determine if there is problem. It compares
information stored on the disk to the information stored in ODM.
Cleanup
The Clean Up After Failed or Interrupted Installation option resets your software
installation back to the beginning after a failed install. A failed install is usually due to a
power failure or a system shutdown occurring before the installation is complete. You
then need to start your installation/update over.
Repository management
The Rename Software Images in Repository, Clean Up Software Images in
Repository, and Service Update Management Assistant (SUMA) options are also on
the SMIT Software Service Management menu. These were already discussed in this
unit.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
instfix Command
• Installs a fix:
# instfix -k IY58143 -d /dev/cd0
• Searches for a fix:
# instfix -ik IY58143
All filesets for IY58143 were found.
• Searches for a fix by keyword:
# instfix -s SCSI -d /dev/cd0
• List which AIX BOS maintenance levels are partly or full
installed:
# instfix -i | grep ML
All filesets for 5.3.0.0_AIX_ML were found.
All filesets for 5300-01_AIX_ML were found.
• List which filesets are missing in a partly installed AIX BOS
maintenance level:
# instfix -ciqk 5300-01_AIX_ML | grep :-:
© Copyright IBM Corporation 2005
Notes:
Introduction
The instfix command allows you to install a fix or a set of fixes without knowing any
information other than the Authorized Program Analysis Report (APAR) number (which
is given to you by your Support Center) or other unique keywords identifying the fix.
The instfix command can also be used to determine if a fix is installed on your
system.
Uempty -f Install filesets for multiple keywords or fixes using an input file. Note that the
output of the -T option produces a suitable input file format. -f results in
instfix using standard input.
-i Use with -k or -f option to display whether fixes or keywords are installed.
This option is for information only. Installation is not attempted when this
option is used.
-a Use only with -i to optionally display the symptom text associated with a fix.
-d Specify the input device (required for all but -i).
-c Output should be in colon delimited format.
Examples
The examples on the visual do the following:
- Install all filesets associated with fix IY58143 from the CD in the /dev/cd0 drive:
# instfix -k IY58143 -d /dev/cd0
- List which AIX BOS Maintenance Levels are partly or fully installed:
# instfix -i | grep ML
All filesets for 5.3.0.0_AIX_ML were found.
All filesets for 5300-01_AIX_ML were found.
- List which filesets are missing in a partly installed AIX BOS Maintenance level:
# instfix -ciqk 5300-01_AIX_ML | grep :-:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the instfix command.
Details — This is a very useful command which can be used to extract update specific
information as well as installing fixes.
Additional Information — Fix information is organized in a Table of Contents on the fix
installation media. After a fix is installed the fix information is kept on the system in a fix
database.
The explanation of the last example is not obvious. The instfix report output in this case
is colon delimited, as requested by the -c flag. The fifth field of the output contains a single
code to indicate the status of the maintenance level. The character interpretations are as
follows:
! Not installed
+ Superseded
- Downlevel
= Correct
Thus, by greping for the “:-:” value, we are looking for filesets which are downlevel on our
system.
Transition Statement — Time for a checkpoint.
Uempty
Checkpoint
1. Which of the following states can your software be in, in order for
you to be able to use it? (select all that apply)
a. Applied state
b. Removed state
c. Install state
d. Commit state
2. What command is used to list all installed software on your
system? _______________
3. Which of the following can you install as an entity?
(select all that apply)
a. Fileset
b. LPP
c. Package
d. Bundle
4. What is the difference between the SMIT menus: Install Software
and Update Installed Software to Latest Level (Update All)?
_________________________________________________
_________________________________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
1. Which of the following states can your software be in, in order for you
to be able to use it? (select all that apply)
a. Applied state
b. Removed state
c. Install state
d. Commit state
2. What command is used to list all installed software on your system?
lslpp -l
3. Which of the following can you install as an entity? (select all
that apply)
a. Fileset
b. LPP
c. Package
d. Bundle
4. What is the difference between the SMIT menus: Install Software and
Update Installed Software to Latest Level (Update All)?
Install Software by default installs everything from the installation
media (except printer and devices) onto the system.
Update Installed Software to Latest Level (Update All) installs only
updates to filesets already installed on your system.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Now, let’s do an exercise to install filesets.
Uempty
Exercise 4: AIX Software Installation
Notes:
Introduction
This lab gives you the opportunity to install filesets and show software installation
history.
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details —
Additional Information —
Transition Statement — Now, let’s summarize this unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 4. AIX Software Installation and Maintenance 4-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — Now, onto the next unit.
References
SC23-4887 AIX 5L Version 5.3 Installation Guide and Reference
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
Notes:
Introduction
The AIX documentation library is available from two sources; the installable AIX
Information Center, and the IBM AIX Information Center that is available on the external
Web. The Web-based IBM AIX Information Center contains the latest AIX information.
This external Information Center is available at the following URL:
http://publib16.boulder.ibm.com/pseries/index.htm. You will be prompted for your
geographical region, language, and AIX release level.
This unit covers the installation and configuration of the information center.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Documentation Client
• Web browser software
Notes:
Overview
In addition to providing SMIT to make system administration tasks easy, beginning with
AIX V4.3, softcopy documentation can be loaded on a documentation server. Any other
computer in the network with appropriate Web browser software (for example, the
Netscape Navigator) can then become a documentation client.
When users on a client computer request an AIX document, the request is sent to the
Web server on a documentation server which then sends back the requested item.
When searches are performed, they are done on the server computer and the results
are then sent back to the user on the client computer.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Configuration steps
The steps outlined above are used to configure an AIX 5L V5.3 documentation server or
online documentation for a standalone pSeries system.
1. Configure TCP/IP on the AIX system. This is discussed later in the course.
2. Install the Web browser software. The Mozilla Web browser for AIX is available on a
CD that can be ordered with AIX. It is Mozilla for AIX. It can also be downloaded
from the Web site: http://www.ibm.com/servers/aix/browsers
3. Install the AIX documentation. AIX provides a separate 2 CD set AIX 5L V5.3
Documentation (5765-G03). It contains the full AIX documentation library in many
different languages. The package names are of the format: infocenter.aix.[lang].
For example you may choose to install: infocenter.aix.EN_US. You may choose
between several categories of documentation within the package.
Uempty 4. Install the Information Center run-time environment. On the same AIX 5L V5.3
Documentation CD, there is a fileset: infocenter.aix.rte. This will provide the eclipse
based Web server engine and documentation access application.
5. Configure the Documentation Services. This is typically done through SMIT and is
covered next.
6. The AIX 5L V5.3 Documentation includes System User’s Guides, Installation
Guides, System Management Guides, Programming Guides, Product and
Application Documentation, and References and Technical References. This
documentation can be installed to disk.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the steps necessary to install the AIX 5L V5.3 online documentation.
Details — Remind the students that TCP/IP configuration will be covered in a later unit.
Additional Information —
Transition Statement — Let's assume that all the steps have been completed except for
the configuration of the Documentation Services. We will use SMIT to complete this step
next.
Uempty
Change/Show Documentation Services
# smit change_documentation_services
[Entry Fields]
DEFAULT_BROWSER = [mozilla]
IC_DOCUMENT_SERVER_MACHINE_NAME = [sys103]
IC_DOCUMENT_SERVER_PORT = [64111] #
IC_DOCUMENT_SERVER_TYPE = DOCSERVER +
IC_DOCUMENT_DIRECTORY = /opt
Notes:
Introduction
Use the SMIT fastpath smit change_documentation_services to access this menu.
This menu is also accessed via the System Environments option on the main SMIT
menu. Choose the option Change/Show Documentation Services.
The Web-based System Manager can also be used to configure the AIX 5L V5.3 online
documentation.
Menu fields
The IC_DOCUMENT_SERVER_MACHINE_NAME should be set to the host name of
the documentation server machine. If acting as both the client and the server, this would
be set to your own hostname.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The IBM Eserver pSeries Information Center is a Web application that serves as a
focal point for all information pertaining to pSeries and AIX. It provides access to the
with AIX 5L V5.3 documentation, as well as access to a message database to search
on error numbers, identifiers and LED’s. FAQs, How-To’s, and many more features are
provided.
Uempty On any AIX 5L V5.3 system with the Information Center installed and configured, you
can access it by:
- Running the command infocenter from the command line. This command starts
the default browser with the URL defined by your configuration.
- Starting the Information Center with the Information Center icon located on the
Help panel of the CDE desktop.
Once in the Information Center, you are presented with a main Web page which has a
variety of hyperlinks to get to the many sources of information. Some links are to Web
sites on the Internet (in the main panel). Others are to the documentation installed on
the Information Center server (in the Contents panel on the left).
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Familiarize the students with how to invoke and use the Information Center.
Details —
Additional Information —
Transition Statement — Let us look at how to access the documents installed on the
Information Center server.
Uempty
Information Center Documents
Notes:
Overview
The contents list in the left panel of the Web page has categories of documents that you
can access. You can repeat clicking on these to drill down to the individual document
you are interested in reading. As you narrow it down, the appropriate collection of
documents or manuals appears in the main panel.
The main panel has three documents you may access for each manual. The HTML
Web pages, an abstract, and the PDF file. Use the PDF file if you wish to either print all
or some of the manual or if you wish to download it to your PC for future offline access.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to access the documentation.
Details —
Additional Information —
Transition Statement — Next, we will take a look at the search facility in the Information
Center.
Uempty
Information Center Search
Notes:
Overview
The Information Center has a search engine which examines the documents to find the
one with information you seek. Entering a search string in the Search field and clicking
Go generates a list of search results ordered by relevance. Clicking the item you think is
the best selection causes the Web page for that section to appear in the main window.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to search the documentation.
Details — The Advanced search button identifies how to form a complex search string
and also allows you to restrict what categories of documents you wish to search.
The complex search string is a Boolean combination of strings including wild cards.
The categories of documents are:
- Information center home
- Information center Assistance
- Hardware documentation
- AIX information
- AIX Message Center
- AIX compiler information
- Cluster information
Additional Information — To speed searches, the search facility uses an index based on
the contents of the documents. The first time someone uses the search facility, it builds the
index. This can take a long time.
Transition Statement — Let's review with some checkpoint questions.
Uempty
Checkpoint
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
Additional Information —
Transition Statement — Now, let’s do an exercise with the AIX Information Center
Uempty
Exercise 5: Information Center
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details —
Additional Information —
Transition Statement — Now, let’s summarize the unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 5. Configuring AIX Documentation 5-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — Now, onto the next unit.
References
SC23-4920 AIX 5L Version 5.3 Web-based System Manager
Administration Guide
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
PC or Linux
Remote Client
Client-Server
# wsm -host <managed-host>
© Copyright IBM Corporation 2005
Notes:
Introduction
AIX V4.3 introduced the Web-based System Manager, which is the next step in the
evolution of AIX system administration tools. There have been many enhancements to
the Web-based System Manager since AIX 5L V5.1. It is considered the default system
administration tool for AIX 5L.
The Web-based System Manager can be run in standalone mode, that is, you can use
this tool to perform system administration functions on the AIX system you are currently
running on.
The Web-based System Manager also supports a remote management. In this
environment, it is possible to administer an AIX system from a remote PC or from
another AIX system using a graphics terminal. In this environment, the AIX system
being administered is the server and the system you are performing the administration
functions from is the client.
Client requirements
Supported Microsoft Windows clients for AIX 5L V5.3 are:
- Windows 2000 Professional version
- Windows XP Professional version
- Windows Server 2003
Supported Linux clients are PCs running:
- Red Hat Enterprise Version 3
- SLES 8 or SLES 9
- Suse 8.0, Suse 8.1, Suse 8.2, and Suse 9.0 using desktops KDE or GNOME only
The PC Web-based System Manager Client installation needs a minimum of 300 MB
free disk space, 512 MB memory (1 GB preferred) and a 1 GHz CPU.
To download Web-based System Manager Client code from an AIX host, use the
address: http://<hostname>/remote_client.html
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the AIX 5L V5.3 Web-based System Manager.
Details — The visual shows three of the environments in which the Web-based System
Manager can be run: standalone, remote client, and client-server.
Use the standalone environment if you wish to administer the AIX system from the system
itself, that is, not across the network. Use the remote-client or client-server environment if
you wish to administer the AIX system from across the network. In this environment, the
AIX system being administered is the server and the system doing the administration work
is the client. The server does not require a graphics terminal. However, the client will need
graphical support.
Because the Web-based System Manager is written in Java, the client can be any machine
with a browser that supports Java V1.4.2 (for AIX 5L V5.3). Thus, the client can be another
AIX system with a graphics terminal or a PC running Windows 2000/2003/XP Professional
or one of the supported distributions of Linux.
Building on the client-server model, it is now possible to manage an AIX system from
anywhere on the Internet or intranet.
The Web-based System Manager code and Java are both installed with the base AIX
operating system. There is no additional charge for either of these software packages. It is
also necessary to configure TCP/IP to run the Web-based System Manager, even when
running in standalone mode. More information on TCP/IP will be covered later in the
course.
Additional Information — Web-based System Manager security is an optional feature
that provides for the secure operation of the Web-based System Manager servers and
clients. It is based on public key cryptography, the Secure Socket Layer (SSL), and the
standard AIX login security.
The Web-based System Manager security fileset, sysmgt.websm.security, is available on
the AIX 5L V5.3 Expansion Pack.
The icon for the security application is available in the System container when:
• The security software has been installed from the Expansion Pack
• You are running Web-based System Manager in local mode
• You are logged in as the root user
Please refer to the AIX 5L Version 5.3 System Management Guide for information or
installing and configuring Web-based System Manager security.
Transition Statement — Let's take a look at how we access the Web-based System
Manager.
Uempty
Accessing the Web-based System Manager
• Standalone mode:
# wsm
• Client-server mode:
– From the AIX 5L client:
# wsm -host <managed-host>
• Applet mode:
– Point your browser to:
http://<managed-host>/wsm.html
Notes:
Introduction
The Web-based System Manager can be configured to run in several different modes.
The operating environments in which Web-based System Manager can be started are
standalone application, client-server, applet, and remote client.
Standalone mode
To access the Web-based System Manager from the command line, use the wsm
command.
To start the Web-based System Manager console from the Common Desktop
Environment (CDE), do the following:
1. Select the Application Manager icon in the CDE front panel
2. Select the System_Admin icon
3. Select the Management Console icon
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Client-server mode
You can manage your local machine or machines that have been configured for remote
management from the Web-based System Manager console. You can select a different
host than your local machine as the managed host. To do this, use the following
command: /usr/websm/bin/wsm -host [managed-host]. The managed host you
specify as [managed-host] displays under the Navigation Area as the first name under
the list of hosts that can be managed. This host is also used to load the Web-based
System Manager user preference file ($HOME/WebSM.pref). Using the -host
argument displays the console to the machine you are using, but uses the preferences
file of the remote host you specify.
Applet mode
In applet mode, point your browser to: http://<managed-host/>wsm.html. The
managed-host is the machine that contains the Web-based System Manager
application.
In applet mode, you can only manage a set of machines that have the same version of
Web-based System Manager installed.
Be aware that AIX 5L V5.1 is using Java 1.3.0, AIX 5L V5.2 is using Java 1.3.1, and
AIX 5L V5.3 is using Java 1.4.2. Your browser plug-in-version must be compatible to the
Java version on the AIX server.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the various methods to invoke the Web-based System Manager.
Details — The visual shows how to access the Web-based System Manager from both the
standalone and remote management environments.
Accessing the Web-based System Manager from standalone mode implies that you are
performing the system administration tasks directly on the AIX system. Access the
Web-based System Manager from either the command line or from the CDE Application
Manager.
Accessing the Web-based System Manager from a client system allows for AIX to be
remotely administered through a graphical interface. There are two ways this can be done.
If the client is an AIX system, you can use the command
wsm -host <managed-host>, or you can use your Web browser. If the client machine is a
non-AIX machine, you will need to use a browser. The URL to access the Web-based
System Manager is http://<managed-host>/wsm.htm.
The managed-host used in the URL or the Web-based System Manager application prompt
must be resolvable.
Additional Information — Some set up is needed on the server before remote access to
the Web-based System Manager can be made. This is discussed shortly.
In applet mode, you can only manage a set of machines that have the same version of
Web-based System Manager installed. The reason for this is that applets in general are
restricted for security reasons to loading Java classes only from the HTTP server running
the applet. While the Java classes needed to operate the Web-based System Manager
console come from the managed machine, another set of Java classes is used to operate
tasks on the managed machines. These classes must be loaded from the machine being
managed (this is different from the managed machine) in order for these classes to match
the operating system being managed. In applet mode, this situation is not possible.
Transition Statement — Let's assume you use one of the listed methods to access the
Web-based System Manager. Let's take a look at what you will see.
Uempty
Using the Web-based System Manager (1 of 3)
Notes:
Console window
The visual shows the Web-based System Manager Console window containing two
primary panels. The panel on the left displays the machines that you can manage from
the Console window. This panel is referred to as the Navigation Area. The panel on the
right (the Contents Area) displays results based on the item selected in the Navigation
Area. You select the machine to perform management operations from the Navigation
Area. As you navigate to the desired operation in the Navigation Area, the Contents
Area is updated to show the allowable choices.
Session log
There is a session log that is a facility of the console. It keeps track of changes made on
managed hosts during a Web-based System Manager session. To view the session log,
select Console -> Session Log.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the Web-based System Manager console.
Details — The visual shows the Web-based System Manager console.
Point out that this application is intuitive, object-oriented and easy-to-use.
Also, point out the different icons (also referred to as plug-ins) displayed on the screen.
These icons provide support for most of the functions that are currently supported by SMIT.
There is a session log that is a facility of the console. It keeps track of changes made on
managed hosts during a Web-based System Manager session. Entries in the log include:
- Time and date of change
- Who made the change
- Host where the change was made
- Short message
- If generated by an application, intermediate results, warnings or error conditions
Also, note that the Web-based System Manager will create a log in the home directory of
the user with the generated commands (analogous to smit.script):
$HOME/websm#.transaction.
Transition Statement — Suppose you want to change the system date and time. In the
Content area, double-click the System Environment icon, then the Settings icon. Or, in
the Navigation area you can expand the System Environment label, then double-click the
Settings label. We will use this as an example of how to use the Web-based System
Manager.
Uempty
Using the Web-based System Manager (2 of 3)
Notes:
Toolbar functions
The visual shows a Web-based System Manager window with the System
Environment: Settings plug-in running in the Contents area. Above the Navigation
Area and Contents Area, there is a toolbar with symbols for managing the window.
From left to right, the symbols support the following functions: Back to previous screen,
Forward to next screen, Up one level, Stop reloading, Reload now, Shutdown,
Broadcast message, Find, Show properties of highlighted object, Icon (to return to icon
mode if currently viewing details), Details (which lists each icon and provides an
explanation of each). Most of these functions can also be accessed via the View option
on the menu bar.
Date/Time icon
If you select the Date/Time icon, this allows you to set the date and time on the system.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — In our example, we have chosen System Environment, then Settings. This is
the window that will be displayed.
Details — Explain some of the options in the tool bar and in the menu bar as outlined in the
student notes. These options will vary depending on the window being used.
In our example, double-click Date/Time.
Transition Statement — The next page shows what you will see if you double-click the
Date/ Time icon.
Uempty
Using the Web-based System Manager (3 of 3)
Notes:
Overview
Note that the Web-based System Manager supports an easy-to-use point-and-click
environment where information can be entered. Use this window to set the system date
and time (only the root user can perform this function). When finished, click OK to apply
your change.
Additional information on the Web-based System Manager can be accessed through
the Internet using the URL: http://www-1.ibm.com/servers/aix/wsm/ .
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the window used to change the system date and time.
Details — Be sure to point out that most of the Web-based System Manager applications
are similar to this, providing point-and-click support to perform various system
management functions.
Note that in this application there is a second option, Time Zone. Click this option to
change the system's time zone.
Daylight Savings Time Dates can vary from country to country. Click this button to
change the dates from the U.S. defaults of the first Sunday in April and the last Sunday in
October.
Transition Statement — Now, we will look at how to configure the Web-based System
Manager.
Uempty
Installation for a Remote Client
• Install the Web-based System Manager (usually done by
default with the base)
• Install an HTTP server:
– IBM HTTP Server (IHS2) on AIX 5L V5.3 Expansion Pack
• Configure the HTTP server (more detail on the next visual)
– configassist
• Test the HTTP server with a browser
• Enable the Web-based System Manager server:
# /usr/websm/bin/wsmserver -enable
• Install the Web-based System Manager client on Windows
or Linux platforms (more detail coming up)
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
If Web-based System Manager is installed, you will see output similar to the following:
# lslpp -h sysmgt.websm.framework
Fileset Level Action Status Date Time
------------------------------------------------------------------------
Path: /usr/lib/objrepos
sysmgt.websm.framework
5.3.0.0 COMMIT COMPLETE 05/18/05 13:39:50
5.3.0.10 COMMIT COMPLETE 05/18/05 13:45:00
Path: /etc/objrepos
sysmgt.websm.framework
5.3.0.0 COMMIT COMPLETE 05/18/05 13:44:07
The following optional filesets can be installed to add additional functionality to
Web-based System Manager. They are not installed by default.
- sysmgt.msg.Locale Language.websm.apps
Enables the locale language to be used if the LANG environment variable is set or if
the -lang argument is used with the wsm command.
- sysmgt.websm.security
Adds support for Secure Socket Layer communication between client and server.
This fileset supports 40-bit encryption and is available on the Expansion Pack.
- sysmgt.websm.security-us
Adds support for Secure Socket Layer communication between client and server.
This fileset supports 128-bit encryption and is available on the Expansion Pack.
Export and import laws could make this fileset unavailable in some countries.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show the complete steps to configure the Web-based System Manager for
client machine access.
Details — Walk through the steps using the student notes as a guide. They are very
detailed.
The Web-based System Manager will install as part of the BOS if there is a graphics
adapter in the machine at the time of installation. No additional configuration is needed
after the installation to allow it to work locally.
The installation and configuration of the HTTP Server is only needed to support the
download and configuration of the remote client application. Once this application is
installed on the PC client, the actual Web-based System Manager connection does not
depend on the managed machine having the HTTP Server installed. After using the IBM
HTTP Server to download the remote client software for your PC or Linux platforms, you
may wish to disable the HTTP Server by executing:
# /usr/HTTPServer/bin/apachectl stop.
In client-server mode, the Web-based System Manager client requests server services
from a managed machine through inetd port 9090. To enable a machine to be a
Web-based System Manager server, type the command:
/usr/websm/bin/wsmserver -enable. This will update the TCP/IP services so that inetd
daemon will listen for Web-based System Manager-client requests on port 9090. By
default, Web-based System Manager is configured during installation not to accept client
requests.
To disable a machine so that it cannot be managed from a Web-based System Manager
client, type the command: /usr/websm/bin/wsmserver -disable. This will remove port
9090 from those ports that are responded to by the inetd daemon. This disables the
machine from responding to new Web-based System Manager client requests. It does not
terminate existing Web-based System Manager server processes.
Additional Information — The package name for the IBM HTTP Server on the
AIX 5L V5.3 Expansion Pack CD is IHS2.
Transition Statement — In the lab, you will have a chance to experiment with the
Web-based System Manager. You will also have the opportunity to set up the Web-based
System Manager server and connect from a client browser. If we are using a PC as the
client we will need to provide that client with additional software.
Uempty
Configure the HTTP (Web) Server
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to configure the HTTP (Web) server to allow remote clients to
manage this platform using the Web-based System Manager.
Details —
Additional Information —
Transition Statement — Next, we will take look at the Web-based System Manager
Remote Client Installation.
Uempty
Remote Client Installation
Notes:
Installation options
To install the Web-based System Manager remote client on a PC running Windows or
Linux, access the AIX Web Server from the client's browser, with the URL of:
http://<managed-host>/remote_client.html
The Web page provides two options for installation of remote client software:
- InstallShield
- Java Web Start (beginning with AIX 5L V5.2.3.0)
The InstallShield is pretty straightforward. It downloads the code and installs using the
InstallShield standard.
The advantage of Java Web Start is that every time the client application runs, it
checks to see if there is a remote server application software update and automatically
downloads the changes.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
HMC Management
• Hardware Management Console (HMC)
• Partition configuration and control
– Dynamic partitioning for LPARs (AIX 5L V5.2 and later)
• Capacity Upgrade on Demand (CUoD)
• Diagnostics
• Operational management
IBM
• Remote HMC control
IBM
Notes:
Diagnostics
A challenge faced with the pSeries system running LPARs is standard AIX error
handling. The HMC interacts with each active partition to handle problem determination
functions.
Operational management
Once your partitions are active, the HMC continues to function as a management
platform, handling operational tasks.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the role of HMC in an LPAR environment.
Details — The main focus here is to explain the importance of the HMC when working with
an LPAR managed system. It is needed for resource allocations, service boot operations,
and LED value display. It also provides access to the LPAR system consoles via a virtual
console window.
Do not try to teach LPAR management here. That is a topic in other courses. Here we want
to build a basis for wanting to have remote access to the HMC platforms.
Additional Information —
Transition Statement — Let us see how we can access the HMC.
Uempty
Remote Access to the HMC
3
SSH access
to HMC
HMC commands
Network
2
Windows, Linux,
or AIX client via
the Web-based
System Manager Alternate
1 HMC
Notes:
Overview
It is often desirable to be able to access the HMC from a remote workstation. This is
especially true when the managed system is a Power4 platform where the HMC is
required to be physically close to the managed system.
Remote operation is possible using a Web-based System Manager graphic interface or
using line commands via a Secure Shell facility. The Web-based System Manager client
may be another HMC, an AIX system running the Web-based System Manager, or a
Linux/Windows platform with the Remote Client software installed.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
remote client and to access the HMC each time). The Web-based System Manager
client can be loaded from the AIX standard distribution software or directly from the
HMC for Windows PCs and Linux (on Intel) workstations. To install the client on
Windows PCs and Linux workstations from the HMC, open a Web browser to the
following Web address where hmc-hostname is the actual hostname of the HMC:
http://hmc-hostname/remote_client.html
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Application
Groups and
Navigation Window Applications
Contents Window
Status
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. True or False? The Web-based System Manager is available
for client access automatically after the BOS is installed.
_____________________________________________
_____________________________________________
2. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode, use the wsm command to access the
Web-based system manager.
c) It is possible to manage an AIX 5L system from a remote
AIX 5L system using an ASCII terminal.
____________________________________________
____________________________________________
____________________________________________
____________________________________________
© Copyright IBM Corporation 2005
Notes:
Checkpoint Solutions
1. True or False? The Web-based System Manager is available
for client access automatically after the BOS is installed.
False. The Web-based System Manager server must be
configured and enabled for client access.
2. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode, use the wsm command to access the
Web-based system manager.
c) It is possible to manage an AIX 5L system from a remote
AIX 5L system using an ASCII terminal.
C is false. However, with a graphics terminal it is possible
to manage different systems simultaneously by adding
the remote systems in the Navigation window of Web-
based System Manager.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Now, let’s do an exercise on installing, configuring, and using the
Web-based System Manager.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
This lab allows you to set up the Web-based System Manager and learn how to use this
interface. If you have other machines in your classroom that are networked together,
you can also try to perform remote administration using the Web-based System
Manager.
The exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 6. Web-based System Manager 6-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4910 System Management Guide: Operating System and
Devices
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Describe the system startup process
• Explain how to shut down the system
• Describe the contents of the /etc/inittab file
• Manage the system environment
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Startup Modes
Normal mode
Login prompt
All processes running
Multi-user mode
Maintenance mode
Maintenance menu
Recover root password
Fix machine that won't boot
Diagnostics
AIXDiagnostics
AIX Diagnostics
© Copyright IBM Corporation 2005
Notes:
Normal mode
When you power on your system, one of the first things it does is determine which
device it should use to boot the machine. By default, the machine uses the normal boot
list, which usually contains one or more hard drives. When the machine does a normal
boot, it will complete the full AIX boot sequence and start processes, enable terminals
and generate a login prompt to make it available for multi-user access. It also activates
the disks, sets up access to the files and directories, starts networking and completes
other machine specific configurations.
Maintenance mode
If your system does not boot or you have lost the root password, you need to boot your
machine using bootable media other than the hard drive (like an installation CD or
bootable backup - mksysb tape). This boots you into maintenance mode. To do this, you
need to ensure that the device that contains your alternate boot media (CD or tape) is in
the boot list. When you boot from the new media, you are given backdoor access to
your system.
Typically, by pressing the F5 key, you use the default firmware bootlist, which always
contains the CD as boot media. Pressing F5 causes the machine to use the default
bootlist on some of the smaller older machines. On some other machines, this action
causes use of the service bootlist. The following example illustrates building of the
service bootlist:
# bootlist -m service cd0 hdisk0 hdisk1
Diagnostics
There is one other boot option - to boot into diagnostics. This can be accomplished by
using bootable media specifically designed for diagnostics or by invoking the diagnostic
mode when the hard drive is the boot device during a service boot. The System
Administration II class (Q1316/AU16) includes a discussion of diagnostics.
Boot lists
All machines have a normal boot list and one or more service boot lists. By default, the
normal boot list is used. The service boot list is invoked (like SMS) during the initial
stages of the boot sequence using function key F6.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Boot
Notes:
Introduction
If you want to set the boot lists or view the system hardware configurations without the
aid of AIX, you can use the System Management Services (SMS) programs.
Invoking SMS
To invoke SMS, power on (or reboot) the system. You hear one beep when the machine
first powers on. About 30 to 45 seconds later, when POST discovers the keyboard, you
hear a different tone. This is what you are listening for. Also, you probably hear the
monitor activate. You have about a 15 second time frame to press F1. If you hear the
music play, you've waited too long. As the monitor warms up, you might see hardware
icons appear on the screen. You want to press the F1 key before it reaches the last
hardware device (speaker). Don't wait for the screen to warm up however, because
many times as the icons are beginning to appear, the music is sounding, and it is too
late. If you are in a noisy room, and you do see the keywords or icons for the discovered
Uempty devices on the screen (for example, on an LED display), wait for the keyword or icon for
the keyboard to be displayed before pressing F1. Timing is everything!
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to load the SMS programs.
Details — Cover the information using the student notes.
Additional Information — If the machine doesn't have a graphical monitor and is using a
ASCII terminal, instead of graphical icons, text will appear as the hardware checks are
completed. This will be the indication to press the appropriate key. If the keyboard doesn't
have function keys, or if you see an ASCII (non-graphical) prompt to use the numeric keys,
use the 1 key instead.
The term “firmware” can be related to the System Management Services programs. These
programs are considered part of System ROS. System ROS is specific to each system
type. There is a piece of software called Software ROS. The systems are designed for the
System ROS to pass control to an intermediary software whose purpose is to provide the
complex environment initialization required by AIX. System ROS is necessary for AIX to
boot, but it does not build the data structures required by AIX to boot. This is done by
Software ROS. Software ROS forms an IPL control block which is compatible with AIX.
Both System ROS and Software ROS are considered “firmware.” For further reading about
firmware, System ROS, and Software ROS, refer to the Redbook 'Managing AIX on
PCI-Based RISC System/6000 Workstations (40P/43P)' - SG24-2581.
This is the graphical version of the System Management Services programs that are found
on the 43P models 140 and 150 (as found in many of our classrooms). The exact
configuration of this menu will vary depending on the model of PCI RS/6000 system being
used. For example, on some systems, the SMS ASCII menu will display:
• 1. Display Configuration
• 2. Select Boot Devices
• 3. Utilities
• 4. Select Language
As another example, an E20 will display:
• 1. Select Boot Devices
• 2. Test the Computer
• 3. Utilities
• 4. Select Language
Cover the student notes for an explanation of the related tasks under the four main tasks.
The students will hear more about some of these tasks in following units.
Transition Statement — Let's now see what happens when a PCI RS/6000 boots up.
Let's assume that the system is booting in normal mode from the hard disk.
Uempty
PCI RS/6000 Start Up Process Overview
PowerOn
POST
INIT
Normal IPL
Notes:
Introduction
During the boot process, a number of steps must be completed. The LED panel will
provide information on the boot progress. Some LED values displayed are model
specific. These values can be found in the Service Guide for that specific model. Other
codes, particularly those displayed in later stages of the boot process, are generic AIX
codes, which are the same on all AIX systems.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Bootstrap code
Once the POST is completed, the system locates and loads bootstrap code. This stage
is completed by System Read Only Storage (System ROS) stored in the firmware. The
bootstrap code, sometimes referred to as Software ROS or level 2 firmware, takes
control and builds AIX specific boot information, then locates, loads and turns control
over to the AIX boot logical volume (BLV). Because these machines can run different
operating systems, the System ROS is generic boot information for the machine and is
operating system independent. The Software ROS is AIX information created based on
the machine type and is responsible for completing machine preparation to enable it to
start an AIX kernel.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# bootinfo -p
# bootinfo -y
32 32-bit
64 64-bit
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List architectures supported by different versions of AIX 5L and explain how to
determine the architecture type.
Details —
Additional Information — Mention bootinfo -p as the way to determine architecture
type.
Mention bootinfo -y as the way to determine bit addressing.
Transition Statement — All the system messages that are produced during a boot
process are logged in a file. Let's see how to view that file.
Uempty
The alog Command
User Boot Install
NIM
Applications Process Process
alog program
/var/adm/ras/bootlog
/var/adm/ras/BosMenus.log
Use the /var/adm/ras/bosinst.log
alog /var/adm/ras/nimlog
command /var/adm/ras/conslog
to view /var/adm/ras/errlog
logs
To view the boot log:
# alog -o -t boot
Notes:
Overview
The alog command is a BOS feature that provides a general-purpose logging facility
that can be used by any application or user to manage a log. The alog command reads
standard input, and writes the output to standard out and copies it to a fixed size file at
the same time.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
/etc/inittab
Format of the line: id:runlevel:action:command
init:2:initdefault:
brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot
powerfail::powerfail:/etc/rc.powerfail 2>&1 | alog -tboot > /dev/console ...
mkatmpvc:2:once:/usr/sbin/mkatmpvc >/dev/console 2>&1
atmsvcd:2:once:/usr/sbin/atmsvcd >/dev/console 2>&1
load64bit:2:wait:/etc/methods/cfg64 >/dev/console 2>&1 # Enable 64-bit execs
tunables:23456789:wait:/usr/sbin/tunrestore -R > /dev/console 2>&1 ...
rc:23456789:wait:/etc/rc 2>&1 | alog -tboot > /dev/console # Multi-User checks
fbcheck:23456789:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot > /dev/console ...
srcmstr:23456789:respawn:/usr/sbin/srcmstr # System Resource Controller
rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons
rcnfs:23456789:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons
cron:23456789:respawn:/usr/sbin/cron
piobe:2:wait:/usr/lib/lpd/pio/etc/pioinit >/dev/null 2>&1 # pb cleanup
qdaemon:23456789:wait:/usr/bin/startsrc -sqdaemon
writesrv:23456789:wait:/usr/bin/startsrc -swritesrv
uprintfd:23456789:respawn:/usr/sbin/uprintfd
shdaemon:2:off:/usr/sbin/shdaemon >/dev/console 2>&1 # High availability daemon
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
. . .
Notes:
Introduction
The /etc/inittab file lists the processes that init will start, and it also specifies when to
start them.
If this file gets corrupted, the system will not boot properly. Because of this, it is a good
idea to keep a backup of this file.
Format of entries
The individual line entries in /etc/inittab contain the following fields:
- id - Up to 14 characters that identify the process. Terminals use their logical device
name as an identifier.
Uempty - runlevel - Defines what run levels the process is valid for. AIX uses run levels of
0-9. If the telinit command is used to change the runlevel, a SIGTERM signal will
be sent to all processes that are not defined for the new run level. If, after 20
seconds, a process hasn't terminated, a SIGKILL signal is sent. The default run level
for the system is 2, which is AIX multiuser mode.
- action - How to treat the process. Valid actions are:
• respawn: If the process does not exist, start it
• wait: Start the process and wait for it to finish before reading the next line
• once: Start the process and do not restart it if it stops
• sysinit: Commands to be run before trying to access the console
• off: Do not run the command
- command - The AIX command to run to start the process.
Run levels
AIX uses a default run level of 2. This is the normal multi-user mode. You may want to
perform maintenance on your system without having other users logged in. The
command shutdown -m places your machine into a single user mode terminating all
logins. Once the machine reaches the single user mode, you will be prompted to enter
root password. When you are ready to return to normal mode, type telinit 2.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the content of the /etc/inittab.
Details — Go through the format of the file, explaining each of the four fields.
AIX does not follow the System V R4 run level specification with special meanings for run
levels 0,3,5 and 6. In AIX, run levels of 0-1 are reserved, 2 is the default and 3-9 can be
defined according to the system administrator's preference. The telinit command can be
used to change the run level for the system. This can also be accomplished using the
fastpath smit telinit. When the telinit command is used to change the run level, the
system will respond by telling you which processes are terminating or starting as a result of
the change in the run level and by displaying the message:
INIT: New run level: n (where n is the new run level)
Use the command shutdown -m to enter maintenance mode. When the system enters
maintenance mode from another run level, only the system console is used as the terminal.
Students will execute this command in the machine exercise.
To add records into the inittab file you should use the mkitab command. For example to
add an entry for tty4 enter:
# mkitab “tty4:2:respawn:/usr/sbin/getty /dev/tty4”
You can use the -i option to add records after a particular entry.
To change currently existing entries in this file, use the chitab command. For example, to
change tty4's runlevel enter:
# chitab “tty4:23:respawn:/usr/sbin/getty /dev/tty4”
Point out all instances where the alog command is used in this file.
Also explain some of the commands that are started from this file - mention what getty
does, also qdaemon, cron, srcmstr (which will be discussed in this and later units) and
perhaps some other programs that are started up.
Additional Information — The inittab file is reread by the init daemon every 60
seconds. The telinit q command is only needed if you can't wait for the next 60 second
check.
Be sure to stress this file is read top to bottom. This is why the wait action is important.
There are dependencies in this file like rcnfs and rctcpip. NFS is network file system
which allows sharing of file systems across the network. NFS cannot work if the line above
it, rctcpip, which starts networking, is not started and completed. Notice that rctcpip's
start action is wait.
The student notes discuss using shutdown -m to reach maintenance mode. The
documentation indicates that telinit S will do the same thing. However, telinit doesn't
seem to kick everyone off the system. Using shutdown is the better choice.
Uempty Some new entries in the inittab were added with AIX 5L V5.1. Look for ctrmc (Resource
Monitoring and Control subsystem) and shdaemon (System hang detection daemon) in the
inittab listing on the visual.
While not shown on the visual, the students may notice some new AIX 5L V5.3 items
further down in the inittab. The naudio entry is for support of the /dev/paud0 sound card
device. Some programs (such as Java) are hard coded to use this device for audio. If the
only audio device or devices are named /dev/aud1 and/or /dev/aud2 instead, then this
script will rename a device as required. The perstat entry is to collect boot time Volume
Group information that will be used in the reporting of certain system performance metrics.
Transition Statement — (A good lead into the next page is to point out the lines in inittab
that are started by the System Resource Controller (SRC) - qdaemon and writesrv. Also,
point out the SRC master line - srcmstr. Then, say something like the sentence given
outside the parentheses.) Now, let's explain what SRC is.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
• Start a subsystem:
# startsrc -s lpd
0513-059 The lpd Subsystem has been started. Subsystem PID is 12472.
• Refresh a subsystem:
# refresh -s lpd
0513-095 The request for subsystem refresh was completed successfully.
• Stop a subsystem:
# stopsrc -s lpd
0513-044 The lpd Subsystem was requested to stop.
Notes:
Introduction
In this section, we will discuss some examples of SRC commands.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List the commands used by the SRC.
Details — Go through each example on the visual. The lpd subsystem is used to show
how to list the status, start a subsystem, refresh a subsystem and shutdown a subsystem.
Additional Information — There are other options that can be used with each of these
commands, such as those used to specify different methods to stop a subsystem. For more
information, refer to the man pages.
As you cover the examples, explain that these commands can also work with the -g option.
But, be aware that using the -g option will effect all subsystems in the group. If you ask to
start a group, every subsystem in the group will be started.
SRC subsystems should always be started using startsrc if you want to be able to use
SRC facilities to monitor and stop them. When they are started using the daemon
executable, the SRC is not the parent and is thus unable to manage them.
Transition Statement — Let's next look at how to stop processes.
Uempty
Stopping Processes
•# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 May 04 - 0:11 /etc/init
root 2626 1 0 May 04 - 1:17 /usr/sbin/syncd 60
root 4136 1 0 May 04 - 0:00 /usr/sbin/srcmstr
root 4964 4136 0 May 04 - 0:00 /usr/sbin/inetd
root 6734 1 0 May 04 - 0:02 /usr/sbin/cron
root 8022 4136 0 May 04 - 0:00 /usr/sbin/qdaemon
root 9036 1 0 May 04 - 0:00 /usr/sbin/uprintfd
root 9345 1 0 May 04 - 0:02 /usr/bin/program
# kill 9345
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show students how to properly shutdown a process.
Details — The kill command and the stopsrc command are used to stop processes.
Processes started by SRC should be stopped by SRC. Other processes can be terminated
with kill.
Make sure the students understand how to read the ps output.
Additional Information — There are some selective subsystems which are defined to the
SRC with a respawn attribute which causes the SRC to restart them if they die for any
reason, such as being killed. An example is the qdaemon. In that circumstance, the only
way to avoid the respawn is to use the stopsrc command to shut them down.
Transition Statement — Now that we know the proper way to shut down processes, let's
look at how to properly shutdown a machine.
Uempty
System Shutdown
• The shutdown command:
– Gracefully stops all activity on the system and advises all
logged on users
– Warns users of an impending shutdown
Notes:
Introduction
The SMIT shutdown fastpath or the shutdown command is used to shut the system
down cleanly.
If used with no options, shutdown displays a message on all enabled terminals (using
the wall command), then (after one minute) disables all terminals, kills all processes on
the system, syncs the disks, unmounts all file systems, and then halts the system.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Flags
The following flags can be used with the shutdown command:
-d Brings the system down from a distributed mode to a multiuser mode.
-F Does a fast shutdown, bypassing the messages to other users and
bringing the system down as quickly as possible.
-h Halts the operating system completely; same as the -v flag.
-i Specifies interactive mode. Displays interactive messages to guide the
user through the shutdown.
-k Avoids shutting down the system.
-m Brings the system down to maintenance (single user) mode.
-r Restarts the system after being shutdown with the reboot command.
-t Restarts the system on the date specified by mmddHHMM [yy] where:
- mm specifies the month
- dd specifies the day
- HH specifies the hour
- MM specifies the minute
-l Since AIX 5L V5.1, this option creates a new file (/etc/shutdown.log) and
appends log output to it. This may be helpful in resolving problems with the
shutdown procedure. While the output is generally not extensive, if the root
file system is full, the log output will not be captured.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The System Environments selection in SMIT controls many different aspects of the
system.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show that a shutdown can be performed using SMIT.
Details — The first item will shut down the system. However, there many good things to
discuss on this screen. This screen seems to have a number of odds and ends related to
system management. You should take a few minutes to walk through each item, giving a
brief description of each. See the student notes for information.
Not all of these items are covered in this class. Many of the details are covered in System
Administration II.
The Change System User Interface item is generally of interest to the students. This
determines the default interface at boot up. It is either CDE (with the graphic login prompt)
or the standard ASCII command-line login. A reboot will be needed for a change specified
here to take effect.
Additional Information — The time on AIX machines is kept using CUT (GMT).
Everything is converted from that time based on your time zone. AIX uses daylight saving
from the last Sunday in March through the last Sunday of October. You now have the
flexibility to provide different parameters if necessary.
Transition Statement — If you need to change the language environment on your system,
you can do so. Let’s discuss this process now.
Uempty
Manage System Language Environment
# smit mlang
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Code sets
Industry-standard code sets are provided by means of the ISO8859 family of code sets,
which provide a range of single-byte code set support. The Personal Computer (PC)
based code sets IBM-850 and IBM-932 are also supported. IBM-850 is a single-byte
code set while IBM-932 is a multibyte code set used to support the Japanese locale.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. What is the first process that is created on the system
and which file does it reference to initiate all the other
processes that have to be started?
____________________________________________
____________________________________________
Notes:
Checkpoint Solutions
1. What is the first process that is created on the system
and which file does it reference to initiate all the other
processes that have to be started?
The initial process is init, which checks /etc/inittab
for information regarding other processes that have to
be started.
Additional Information —
Transition Statement — Now, it’s time for an exercise.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
• Multi-user mode
• Boot using System Management Services
• System Resource Controller (SRC)
• Resetting the run level (INIT)
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 7. System Startup and Shutdown 7-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
Online System Management Guide: Operating System and
Devices
Unit Objectives
After completing this unit, you should be able to:
• Describe the difference between logical and physical
devices
• Describe the purpose of the ODM predefined and
customized databases
• Describe the different states of a device
• Describe the format of device location codes
• Use SMIT to add/show/change/delete devices
Notes:
Device Terminology
• Physical Devices
• Ports
• Device Drivers
• Logical Devices
• /dev Directory
Notes:
Device terminology
In order to attach peripherals such as terminals and printers to an AIX system, you must
tell AIX the characteristics of these devices so that the operating system can send the
correct signals to the adapter where the device is connected. A number of pieces of
hardware and software must interact correctly for the device to function correctly.
- Physical Devices - Actual hardware that is connected in some way to the system.
- Ports - The physical connectors/adapters in the system where physical devices are
attached. Most ports are programmable by the system software to allow attachment
of many different types of devices.
- Device Drivers - Software in the kernel that controls the activity on a port and the
format of the data that is sent to the device.
- Logical Devices - Software interfaces (special files) that present a means of
accessing a physical device to the users and application programs. Data appended
Uempty to logical devices will be sent to the appropriate device driver. Data read from logical
devices will be read from the appropriate device driver.
- /dev - The directory which contains all of the logical devices that can be directly
accessed by the user. (Some of the logical devices defined are only referenced in
the ODM customized database and cannot be accessed by users.)
Instructor Notes:
Purpose — Explain the terminology used when dealing with devices.
Details — Suggestion: Try to get the students to define these for you. In most cases, you
will have some pretty good definitions coming from the class.
Additional Information — Question: What is your definition of a physical device?
Answer: Something you can touch.
Transition Statement — We shall now look at the different types of devices that are
present on the system.
Uempty
Listing of /dev Directory
# ls -l /dev
brw-rw--rw 1 root system 20,0 Oct 29 02:25 fd0
brw-rw--rw 1 root system 20,64 Oct 29 02:26 fd1
crw-rw--rw 1 root system 20,0 Oct 29 02:25 rfd0
crw-rw--rw 1 root system 20,64 Oct 29 02:26 rfd1
:
:
crw-r--r-- 1 root system 22,0 Oct 29 02:25 rmt0
crw-r--r-- 1 root system 22,1 Oct 29 02:25 rmt0.1
:
:
crw------- 1 root system 14,1 Oct 29 02:44 hdisk0
crw------- 1 root system 14,2 Nov 1 05:31 hdisk1
crw------- 2 root system 14,1 Oct 29 02:44 rhdisk0
crw------- 1 root system 14,2 Nov 1 05:31 rhdisk1
rmt0
fd0 rmt1
Notes:
Types of devices
There are a large number of devices that can be configured in the system. Devices can
be one of two types:
- Block device is a structured random access device. Buffering is used to provide a
block-at-a-time method of access. This is usually only used for disk file systems.
- Character (raw) device is a sequential, stream-oriented device which provides no
buffering.
Most block devices also have an equivalent character device. For example, /dev/hd1
provides buffered access to a logical volume whereas /dev/rhd1 provides raw access
to the same logical volume.
ls -l /dev output
The ls -l command allows you to see the type of a file. A special file (in the /dev
directory) will be indicated by a b in the first column for a block device or a c for a
character device.
Normally, the fifth field contains a numeric value indicating the number of bytes in the
file. For devices, it shows the major and minor device numbers. The device rmt0 shown
in the listing has a major device number of 22 and a minor device number of 1. This
indicates that the code to handle major device 22 must already be in the kernel, and it
must handle device number 1 correctly. While not shown here, there would be files for
rmt0 with minor numbers of 0 through 7, each of which must be handled correctly by
the device driver. More precisely, the major number refers to the software section of
code in the kernel which handles that type of device, and the minor number to the
particular device of that type or the operation mode of a device of that type.
Notes:
Introduction
The predefined and customized databases store information about all of the logical
devices in the system and their attributes. It is managed by the Object Data Manager
(ODM).
Predefined database
The predefined database contains configuration data for all possible devices supported
by the system. The SMIT menus have options to install non-supported drivers. The
contents of the predefined database is largely defined at installation time, ensuring that
you always have support for devices in your system.
Configuration Manager
The Configuration Manager is a program that automatically configures devices on your
system during system boot and run time. The Configuration Manager uses the
information from the predefined and customized databases during this process, and
updates the customized database afterwards.
Instructor Notes:
Purpose — Show how the device information and support are held in AIX.
Details — The Object Data Manager (ODM) is a repository for information about this
system. The ODM enables up to 1000 device configurations.
It contains device support, device vital product data, software support for these devices,
and so forth.
The ODM is divided into two areas:
• Predefined contains the supported devices
• Customized contains the configured devices
There is a small terminology mismatch between SMIT and the ODM menu interfaces that
look after devices in AIX:
SMIT ODM The World
supported predefined (unknown, not installed yet)
defined customized defined
configured customized available
Entries in the predefined configuration database are initially created at software installation
time. Under AIX 5L V5.1 and AIX V4, the installation programs install device software for
every type of device detected on the system and a default set of common device types. An
entry in the predefined configuration database is created for each type of device software
installed.
Beginning with AIX 5L V5.2, all known device drivers are installed, unless the default
installation value is changed. This enables a backup of a system to be easily loaded on
another system.
Additional Information —
Transition Statement — We will now take a look at these classifications of devices and
see the differences between the ODM databases.
Uempty
List All Supported Devices
PdDv (Predefined Devices)
# lsdev -P -H
class type subclass description
memory totmem sys Memory
tape 4mm4gb scsi 4.0 GB 4mm Tape Drive
disk osdisk scsi Other SCSI Disk Drive
adapter 22100020 pci IBM PCI Ethernet Adapter (22100020)
adapter 14101800 pci IBM PCI Tokenring Adapter (14101800)
adapter ppa isa_sio Standard I/O Parallel Port Adapter
adapter isa_keyboard isa_sio Keyboard Adapter
..
..
Notes:
Introduction
Default characteristics for known device types are stored in the ODM predefined
database.
Devices are classified by:
- Class indicates what the device does
- Type indicates what model it is
- Subclass indicates how it can be attached to the system
There are also definitions for some unknown devices which can be attached to the
system (for example, non-IBM serial or parallel printers or SCSI disk drives). These
devices are either intelligent and need little configuration, or the device attachment
method is standard (for example, parallel or RS232) and no features of the device are
assumed when it is added.
Notes:
Introduction
The devices that have been customized in the system are described in the ODM
customized database. Each device has a logical device name, status, location and
various attributes.
Uempty Devices may appear in a defined state after a restart. If this is the case, it may be
because the device is powered off or no longer exists on the system.
Devices with a location code are physical devices. Devices without a location code are
logical devices. Location codes depend on the type of device and the adapter to which
the device is connected.
The lsattr -E -l [resource name] command provides detailed information on the
effective attributes currently configured for specified devices. In the example, it provides
configuration information on the system itself.
- The -C option for lsdev pulls the customized information from the ODM
- The -E option for lsattr shows the effective attributes
- The -l option for both commands is the logical device name
- The -c option for both commands is the class of device
- The -a attribute option for the lsattr command displays information for a
specific attribute
Another command that can be used to list information about devices found in the ODM
customized database is lscfg -v. The listing is sorted by parent, child and device
location. Specific hardware information about devices will be listed such as EC level,
FRU number, part number, and so forth. The output also displays the model
architecture and bus type.
Instructor Notes:
Purpose — Show how to view the configured devices on the system.
Details — Spend some time discussing the lsattr example as students will be working
with sys0 during the exercise. Under the column titled user_settable, will be the values of
True or False. This indicates whether or not the associated value can be changed. In most
cases, these values will not be changed unless performing more advanced functions such
as performance and tuning.
The administrator can also use SMIT to change a device state from available to defined, or
from defined to available.
One command that almost everyone wants to know is how to determine how much memory
is on the system. You can also view memory size using smit chgsys. The resulting SMIT
menu will display the amount of memory on the system. The command
lsattr -El sys0 -a realmem will show the total amount of memory. To see the size of an
individual memory card, you can use the same command to see the characteristic of that
card: lsattr -El mem0.
The student notes also mention the lscfg -v command. Be sure to explain this command
as it is mentioned again in the checkpoint questions. If students are at terminals, you may
want them to execute this command to display the output.
Additional Information —
Transition Statement — As we have seen, devices may exist in one of several states. We
shall now look at these in some more detail.
Uempty
Device States
Predefined Database
Undefined Supported
Device
rmdev -dl
Customized Database
rmdev -dl
Defined Not Usable
mkdev -l
or rmdev -l
cfgmgr
Available Ready for
Use
Notes:
Device states
The most common device states are:
- Undefined - The device is a supported device but is not configured. It does not
reside in the customized database.
- Defined - The device has been added to the customized database. It has been
allocated a logical device name, a location code and attributes have been assigned
to it. But, it is still unavailable for use.
- Available - The device resides in the customized database. The device is fully
configured and is ready for use.
When a device is first identified, it is configured and put into the Available state.
If a device that has been configured in the past is powered off and the machine is
rebooted, the device will appear in the Defined state. This indicates that the system
knows it is supposed to be there, but because it was not powered on, it cannot be used.
cfgmgr
The command that is executed at boot time to discover and configure attached devices
is cfmgr. After booting the system, if a device is either removed/powered-off or
attached/powered-on, the state of the device in the ODM is not automatically changed.
Rather than running mkdev or rmdev on the specific device, you would typically execute
cfgmgr. cfgmgr would discover any new devices or will re-assess the state of any
devices already defined in the ODM customized device database.
Self-Configuring Devices
2. Answer:
- CD-ROM
- 10-80-00-3,0
1. Who are you?
Device
cfgmgr Driver
4a) Load device driver
4b) Make /dev/cd0
ODM: 3. cd0 defined entry
cd0
defined Device
Kernel Driver
10-80-00-3,0
/unix 39
ODM: # ls -l /dev/cd0
cd0 br--r--r-- root system 39, 0 /dev/cd0
available
10-80-00-3,0 5. Device available
Notes:
Configuring devices
cfgmgr is a program that runs during boot that configures devices. It can also be run
safely from the command line on a system that is up and running. cfgmgr identifies all
self-configuring devices as long as they are powered on and matches them to the
information in the predefined database. It then uses the predefined information to
complete a customized database entry for the device.
All devices are self-configuring except for parallel and serial devices. So, except for
things like printers and ASCII terminals, configuring a device requires only attaching it
and power it on before booting the machine. Since cfgmgr runs during the boot
process, no more intervention is required by the administrator.
You see that for SCSI devices, you need to set a unique SCSI ID on the device before
attaching it. Once that is done, configuration of the device is handled by AIX.
Notes:
Introduction
The SMIT Devices menu (fastpath: # smit devices) is used to manage the
configuration information about the devices in the system. This information controls the
way the kernel and applications behave towards the physical devices attached. The list
of devices varies depending on what you have configured or installed on your system.
Devices can also be managed using the Web-based System Manager.
Uempty - Printer/Plotter
This submenu allows you to configure printer devices and also queues for local
printers and remote printers.
- TTY
Used for any non-printer device attached to a serial port. (For example: terminal,
modem, and direct connection.)
- PTY
Used for a pseudo-terminal device. It provides the appearance of a real ASCII
terminal to the application, but does not have any physical port attachment. It is
used for applications such as AIXWindows and TCP/IP communications.
- Communications
Used for adapters for various types of communications. (For example: Token Ring,
Ethernet, MultiProtocol, X.25, 3270, and Fiber Optic.)
Instructor Notes:
Purpose — Show the options available in the SMIT Devices menu.
Details — Most of the device-related actions in SMIT can take place while the system is
operational and users are accessing it.
Additional Information —
Transition Statement — We will show an example of how to use this screen to configure
an ASCII terminal in just a few minutes. But, first we need to look at location codes in order
to understand how to fill in the SMIT screens.
Uempty
Device Addressing
• Location codes are used for device addressing
• The location code for a device is a path from the adapter in
the CPU drawer or system unit, through the signal cables
and the asynchronous distribution box (if there is one) to the
device
• Location codes consist of up to four fields of information
depending on the type of device
• Location codes differ based on model type
Notes:
Location code
Every logical device is assigned a location code when it is attached to the system.
Location codes depend on the type of device and the adapter to which it connects.
The location code is another way of identifying the physical device.
The location codes exist to provide the system with a method of locating the device and
establishing relationships between devices and their adapters. If a hardware failure
occurs, the location code is often displayed or referred to in the LED.
Instructor Notes:
Purpose — Overview of AIX location codes.
Details — This visual is intended as an introduction. It is just a starting point. The following
visuals cover this with specific examples and will help clarify the concept.
Different machine models will have specific values. Make sure students understand this.
The visual shows examples of the 43P Model 150. Location code values for all other model
types can be found in the service guides for that model.
Explain the format of the location codes, AB-CD-EF-GH.
AB-CD is an adapter.
Additional Information — As you go through the following visuals, emphasize to the
students that they are not expected to totally analyze the structure of the AIX location
codes. Many aspects vary from machine to machine. What is important is that they keep a
copy of a current lsdev listing in their log book. Using that listing, they should be able to:
• Look up the logical name of a device given the location code
• Identify the parent adapter from the first two pairs of the location code of a device
• Recognize how the device is connected to the parent adapter given the last two pairs in
the location code (for example, SCSI address, or port # in a RAN)
Transition Statement — Let's look at what the letters mean.
Uempty
Location Code Format for PCI Devices
AB-CD-EF-GH
EF The connector ID
Notes:
Introduction
Knowing how to interpret location codes allows you to quickly locate a device based on
the software definition. If you have several of the same type of devices, hard disks for
example, it allows you to easily identify the exact disk that is having the problem.
The actual values used in the location codes vary from model to model. For specific
values, you need to reference the Service Guide for your model. These can be found
online at the IBM Information Center:
http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/
Uempty For integrated devices, like the built-in keyboard port, the C position will be a letter A-Z
and the D position will be a 0. For example 01-F0 shows the keyboard adapter is on the
ISA bus (01) and is an integrated adapter (F0). The letters are assigned in the order in
which they are discovered during configuration. Each integrated device is assured a
unique value.
Instructor Notes:
Purpose — To provide an example of location codes for the Model 150.
Details — Explain the visual contents.
EF - Connector ID is easier to explain with the discussion of the 128-port async adapter.
Be sure to stress that specific location code values can be found in the Service Guides for
that model.
Additional Information — In the student notes, there is information about the Model 150.
Since some student might be using other models in the classroom, they will see differences
from what is covered in the lecture material.
The Service Guides use the AB-CD-EF-GH formatting. Other AIX documentation may use
the AA-BB-CC-DD formatting. Since the Service Guides are the source of specific location
code values, we are using that formatting in this unit.
Transition Statement — Let's look at a picture that show the addressing for serial devices.
Uempty
Location Code Example: Non-SCSI
28-Port Asynchronous Controller
1P-10-11-01 1P-10-11-07
System Unit
0 1 2 3 4 5 6 7
1
128-Port 8 9 10 11 12 13 14 15 Remote
Adapter Async Node 1P-10-22-04
(RAN)
2 1
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
1P-10 1 2
8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15
1P-10-21-10
Notes:
Non-SCSI example
The example in the visual illustrates non-SCSI device location codes for a pSeries
system.
A 128-port asynchronous adapter allows 128 serial devices (like ASCII terminals) to be
attached to the adapter. The adapter has two connectors (or ports) on the card. Each
connector can support a serial bus.
On each bus, boxes that contain ports are connected to each other. These boxes are
called Remote Asynchronous Nodes (RANs). Each of the two connectors can support
four RANs. Four RANs on two connectors give a total of eight RANs. Each RAN has 16
ports. That gives a total of 128 ports.
Location code
The location code must account for each piece of the puzzle.
AB-CD is the same as previous examples. It provides the adapter card address. In our
example, the adapter card is plugged into slot 5 on the PCI bus.
E identifies the connector on the adapter card, 1 or 2.
F identifies the RAN. RANs are numbered in ascending order going away from the
adapter, 1-4.
GH is the two-digit port number. For example, port 7 is 07. The range of numbers is
00-15.
AB-CD-EF-G,H
AB-CD Identifies the bus and the adapter location
Same as with non-SCSI devices
Notes:
AB-CD position
The AB-CD positions contain the same information we have already covered. It
indicates where the adapter card (SCSI controller) is attached: the bus and slot number.
EF position
The EF position identifies the SCSI bus. If the controller provides only a single SCSI
bus, the EF position is 00. If the controller provides for dual SCSI buses, each bus must
Uempty be identified by a unique address. With dual SCSI, the card's internal bus is identified
with 00 and the card's external bus is identified with 01.
G,H position
The G,H position provides two pieces of information. The G position is the SCSI
address or SCSI ID of the device. The SCSI ID is set on the device itself. It is usually
accomplished by setting jumpers or switches on the device. Some devices have dials or
push buttons that are external that allow an easy method to set the ID. Set the SCSI ID
so that it doesn't conflict with another device on that bus. When cfgmgr runs it will
recognize the ID that is set on the hardware and set the G position accordingly.
The H is usually a 0. If the SCSI devices has multiple devices within it, then the logical
unit number (LUN) is used to uniquely identify each device. Non-zero numbers are used
with RAID arrays or some CD jukeboxes.
Instructor Notes:
Purpose — To provide an explanation of SCSI addressing on a pSeries system.
Details — Explain positions AB-CD are the same as before. It identifies the location of the
adapter.
The EF position will be 00 or 01. Single SCSI is always 00. Dual SCSI has two buses, the
internal 00 and the external 01.
G,H is the SCSI ID, LUN. Reference the student notes for an explanation. When
configuring a SCSI ID, stress ensuring that the number selected does not duplicate an
existing ID on the that bus.
To help identify existing SCSI IDs, use lsdev -Cs scsi.
Additional Information —
Transition Statement — Let's take a look at an example.
Uempty
Location Code Example for SCSI Device
SCSI Devices (Disk, Tape, CD-ROM)
System
Unit
10-80-00-4,0
SCSI 10-80-00-6,0
Adapter 7 4
SCSI Bus 6
10-80
0
SCSI ID
Notes:
Instructor Notes:
Purpose — Discuss an example of a location code for a SCSI device.
Details — Cover the example using the student notes.
Ask the student to determine the internal disk's location code. It is 10-80-00-0,0.
Additional Information — SCSI adapters default to ID's of 7. That ID is changeable but
should not be changed without good reason. In a high availability (HA) environment, disks
can be connected to two systems at once via one SCSI bus. If the SCSI adapter on both
machines default to 7, there will be SCSI conflict. In an HA environment, it is necessary to
assign new ID's to SCSI card for that reason.
This information is here for the instructor. It is not suggested that you cover HA-related
topics.
Transition Statement — Let's look at a representation of a typical 43P Model 150.
Uempty
Location Code Example: PCI
Standard I/O Standard
Keyboard
Diskette Serial
Adapter
Adapter Port 1
01-K1
01-D1 01-S1
Bridge
01-D1-00-00 01-K1-01-00
SCSI Disk
Drive
10-80-00-4,0
Notes:
Instructor Notes:
Purpose — Explain the relationship between the PCI and ISA buses on the PCI pSeries
systems.
Details — The visual shows a partial view of devices attached to a PCI-based pSeries
system. This example was based on a 43P Model 150, so be sure to point out that this is
just an example and location codes and device locations will vary by system and model.
Our example shows both the PCI bus (pci0) and the ISA bus (isa0). A bridge exists
between the two buses. In our example, the two standard serial ports, as well as the
keyboard (and mouse - not shown) are attached to the ISA bus.
Note that all devices attached to the PCI bus will have a location code beginning with 10.
The ISA bus itself will also have a location code beginning with 10. Any devices attached to
the ISA bus will begin with location code 01.
Additional Information —
Transition Statement — In addition to the AIX locations codes we also have physical
location codes. This may seem redundant, but it is necessary to handle situations where
multiple AIX operating systems are running on one pSeries machine. Since each AIX
instance could be using the same AIX location code for different devices, we need to have
a way to uniquely identifying devices on the machine. Let us, take a look at layout of one of
these machines that can be logically partitioned.
Uempty
pSeries 670 and 690 Location Codes
U1.35-P2-X1
U1.35-P1-F1
Unused
U1.35-P1-X2
U1.35-P1-X3
U1.35-P1-X4
U1.35-P1-V1
U1.35-P1-V2
U1.35-P1-V3
Example of hardware location
code format
U1.18-P1-M1
U1.18-P1-M2
U1.18-P1-M3
U1.18-P1-M4
U1.18-X2
U1.5-P1-I1/Z1
U1.18-X1
U1.18-P1-M8
U1.18-P1-M6
U1.18-P1-M5
U1.18-P1-M7
| | | |
Front view of rack
U1.9
U1.5
Notes:
Introduction
Physical addressing has been in place throughout the history of the RS/6000 and
pSeries family of products. An important change with the pSeries 670 and 690 servers
is that the I/O drawers are installed at specific locations within the rack. We include the
visual above primarily as reference. Our focus is on I/O drawer addressing.
The example in the visual above shows location codes for the pSeries 670 and 690.
The Service Guide for each type of system contains charts to look up the location
codes.
Notes:
S1
S2 TTY
Notes:
Introduction
Most devices self-configure using cfgmgr. One type of device that does not, is an ASCII
terminal. The next few visuals go through the process of adding an ASCII terminal to
provide an example of what is required to manually configure a device.
First steps
First, physically attach the terminal to the serial port. Be sure to note which serial port it
is attached to. We need that information as we complete this process.
To begin the configuration, use smit tty. This screen is used to manage the
configuration of asynchronous devices.
To add the terminal, select Add a TTY.
Attachment
TTY Type
Parent Adapter
Notes:
Introduction
Once you select Add a TTY, you will then be asked the TTY Type and which Parent
Adapter the terminal is attached to.
TTY type
In this example, the choices for TTY type are rs232 and rs422. rs232 is the most
common TTY type.
To select the correct parent adapter, you need to know where the device is physically
attached. This is where the serial port is important.
In our example from the previous page, the terminal was attached to serial port 1.
Therefore, we select sa0 - Standard I/O Serial Port 1.
Instructor Notes:
Purpose — To show the how to determine the correct selection from the SMIT screens.
Details — You will need to select the TTY Type, then select the port where the device is
attached. Point out that the location code clearly defines the physical port. Adapter names
sometime get confusing because they are numbered starting with 0. Port numbers and
adapter names do not match.
Additional Information — Since we just talked about the 128-port async adapter, be sure
to point out the other adapters on the list.
Transition Statement — Let’s take a look at the device nomenclature for the example
we’re talking about before we continue with the Add a TTY screen.
Uempty
Device Nomenclature
For the built-in serial connection, the nomenclature looks like this:
sa0 sa1
Built-in adapters
on system planar
Serial ports s1 s2
For the 128-port adapter, the nomenclature looks like this:
Notes:
Pictorial view
This visual shows a picture and the associated nomenclature for the scenario we’re
discussing on adding a TTY.
Instructor Notes:
Purpose — Show a picture of the scenario for the TTY we’re adding.
Details — Point out the naming conventions.
Additional Information —
Transition Statement — Now that we know where it is attached, it is time to define the
terminal's characteristics. Let's take a look at that screen.
Uempty
Add a TTY
Add a TTY
Notes:
PORT number
There is only one mandatory field on this screen and that is the PORT number. The F4
key will provide a list of possible port numbers. For the first built-in serial port it is s1, for
the second it is s2. On a 16-port RAN, the choices are 0-15. Select the one to which the
terminal is connected. The combination of the appropriate RAN selected on the Parent
Adapter selector screen and the port number shown here provides the system with the
correct location code.
You must supply the port number to uniquely locate the device. The value required
depends upon the adapter specified. For example:
Built-in serial port S1 s1
Built-in serial port S2 s2
8-Port Adapter 0-7
16-Port Adapter 0-15
Each 16-PORT RAN 0-15
Enable LOGIN
The Enable LOGIN attribute will be set to disable by default. If you are adding a
terminal that should have a login prompt, you should change this to enable.
TERMINAL type
The TERMINAL type attribute is used to assign the TERM environment variable when a
user logs in on the device. You must set this to the name of a supported terminal type.
The list of supported terminals can be found in directories located in
/usr/share/lib/terminfo.
• lscfg -v
– Provides details of all devices including manufacturer, type
and model number and part numbers
• getconf -a
– Provides the values of all system configuration variables
Notes:
# getconf MACHINE_ARCHITECTURE
chrp
# getconf KERNEL_BITMODE
32
# getconf HARDWARE_BITMODE
32
# getconf REAL_MEMORY
131072
Instructor Notes:
Purpose — To show how to document the device configurations.
Details — You should stress the importance of good documentation. Device configuration
is one area that must be documented. You should suggest that administrators create a
book for each system and keep track of all changes that are made to the system.
Cover the commands shown in the visual and student notes.
Additional Information —
Transition Statement — Let's take a look at some checkpoint questions to see how much
you remember.
Uempty
Checkpoint (1 of 2)
1. Is it possible to use SCSI ID 7 for a new tape drive?
_______________________________________________
_______________________________________________
2. Use the output on the next visual (lsdev -C -H) to answer the
following four questions.
a) What will happen if we attempt to add another device with
the SCSI address set to 4?
_______________________________________________
_______________________________________________
b) Can the 8 mm tape drive be currently used? Why?
_______________________________________________
_______________________________________________
c) Where is the printer connected? __________________
d) The Ethernet adapter is installed in what slot?
_______________________________________________
_______________________________________________
© Copyright IBM Corporation 2005
Notes:
Checkpoint (2 of 2)
# lsdev -C –H
name status location description
sys0 Available System Object
pci0 Available PCI Bus
isa0 Available 10-58 ISA Bus
ppa0 Available 01-R1 Standard I/O Parallel Port Adapter
lp0 Available 01-R1-00-00 IBM 4039 LaserPrinter
sa0 Available 01-S1 Standard I/O Serial Port 1
tty0 Available 01-S1-00-00 Asynchronous Terminal
mem0 Available Memory
scsi0 Available 10-80 Wide SCSI I/O Controller
rmt0 Defined 10-80-00-3,0 5.0 GB 8 mm Tape Drive
hdisk0 Available 10-80-00-4,0 SCSI Disk Drive
ent0 Available 10-60 IBM PCI 10/100 Ethernet Adapter
Notes:
Checkpoint Solutions
1. Is it possible to use SCSI ID 7 for a new tape drive?
No. The SCSI adapter itself uses ID 7. So, it cannot be used
for other devices.
2. Use the output on the next visual (lsdev -C -H) to answer the
following four questions.
a) What will happen if we attempt to add another device with
the SCSI address set to 4?
The operation will fail as there is already a device
(SCSI Disk Drive) configured at this location.
b) Can the 8 mm tape drive be currently used? Why?
No, because it is in the defined state. You have to first make
it available by either using SMIT or the mkdev command.
c) Where is the printer connected? The parallel port
d) The Ethernet adapter is installed in what slot?
It is an integrated adapter which does not occupy a slot on
the PCI bus.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Now, it’s time for an exercise on devices.
Exercise 8: Devices
Notes:
Introduction
This lab gives you an opportunity to examine the device configuration of the classroom
system.
The exercise can be found in your Student Exercise Guide.
Unit Summary
• A physical device is the actual hardware attached to the
system
• A logical device is the software interface used by programs
and users to access a physical device
• Device information is stored in the ODM in two databases:
customized and predefined
• Devices can exist in a number of different states:
unavailable, defined, available and stopped
• Location codes are used to describe exactly where a
device is connected into the system
• Device attributes can be modified through SMIT
• To create, modify, or remove device definitions, it is
sometimes necessary to use commands such as mkdev,
chdev and rmdev
© Copyright IBM Corporation 2005
Notes:
References
Online System Management: Operating System and Devices
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Describe the terminology and concepts associated with:
– Physical volumes
– Volume groups
– Logical volumes
– Physical partitions
– Logical partitions
• Describe how file systems and logical volumes are
related
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Components
The basic components or building blocks of AIX storage are:
- Files
- Directories
- File systems
- Logical storage
- Physical storage
- Logical Volume Manager (LVM)
As a user, you work with files and directories. As a system administrator, you work with
the others as well.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Partition 1 Partition 4
Partition 2
Partition 5
Partition 3
PROBLEMS:
• Fixed partitions
• Expanding size of the partition
• Limitation on size of a file system and a file
• Contiguous data requirement
• Time and effort required in planning ahead
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Logical volume
Notes:
Introduction
The AIX Logical Volume Manager controls disk storage resources by mapping data
between a simple and flexible logical view of storage space and the actual physical
disks.
This visual and these notes provide a brief overview of the basic components of LVM.
Components
A hierarchy of structures is used to manage disk storage:
- Volume groups
- Physical volumes
- Physical partitions
- Logical volumes
- Logical partitions
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Give a brief overview of the LVM terms.
Details —
Additional Information —
Transition Statement — Let's begin our look at the Logical Volume Manager by seeing
how physical disks are viewed by the operating system.
Uempty
Physical Storage
PP1
Volume PV1 PP2
group A PP3
PP4 Physical
PP5 volume
PP6 /dev/hdiskn
Volume PV2 PV3 PV4 PV5
group B
PPn
Notes:
Introduction
Disk space on a physical volume (PV) is allocated to logical volumes (LVs) in chunks
called physical partitions (PPs). Each physical partition size is the same across all the
disks in a volume group (VG). The PP size is set at the time the VG is created. The size
is set in megabytes on power of two boundaries (for example: 4 MB, 8 MB, 16 MB, and
so forth). The default is 4 MB.
In AIX 5L V5.2 and later, LVM will default the PP size of a new VG to the smallest PP
size (equal or greater than 4 MB) which will allow full addressing of the largest disk in
the VG given the selected maximum number of PPs per PV (defaults to 1016). The
smallest PP size is 1 MB, which is supported by using a larger number of PPs per PV.
When a PV is added to a system, a file called hdiskn is added to the /dev directory. n is
a number allocated by the operating system. It is usually the next available number.
This file may be used to access the device directly but this is not often done.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Volume Groups
• Volume group
Volume Group Max Max LVs Max PPs per Max PP
types: Type PVs VG Size
í Normal
Normal 32 256 32512 1 GB
í Big (1016 * 32)
í Scalable 128 512 130048 1 GB
Big
(1016 * 128)
• Limits Scalable 1024 4096 2097152 128 GB
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Expand on the different types of volume groups and their limits. Also, define
the advantages of separate VGs.
Details — We haven't discussed how to create a volume group yet. The command mkvg is
new to the students. However, since we discussed the concept of a volume group and the
maximums for volume groups, it is important to introduce the concept of big VGs, scalable
VGs and factors.
Existing volume groups can be converted to scalable or big volume groups and the -t factor
can be changed as well. Both of these can be done dynamically. To modify an existing VG,
the command is chvg instead of mkvg.
Discuss the main reasons for having external VGs as opposed to internal, and what
considerations have to be made when adding a new disk to the system.
The rootvg includes paging space, the journal log, boot data and dump storage usually
each in its own logical volume. The rootvg has attributes that differ from the user-created
VGs. For example, it cannot be imported or exported (moved) like other VGs can.
Point out that VGs can contain disks of different sizes. Only the physical partitions within a
VG must be the same size.
Additional Information — Once a volume group is converted to big or scalable, it cannot
be converted back dynamically. It also cannot be used on earlier versions of AIX that don't
support big volume groups.
Transition Statement — There is a portion of the disk which holds all the administrative
information related to the VG in terms of the PVs and the LVs. It is called the Volume Group
Descriptor Area (VGDA).
Uempty
Volume Group Descriptor Area (VGDA)
Three disk or more
One disk VG Two disk VG VG
VGDA VGDA
Notes:
Quorum
There must be a quorum of VGDAs available to activate the volume group and make it
available for use (with the varyonvg command). A quorum of VGDA copies is needed
to ensure the data integrity of management data that describes the logical and physical
volumes in the volume group. A quorum is equal to 51% or more of the VGDAs
available.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
A system administrator can force a volume group to varyon without a quorum. This is
not recommended and should only be done in an emergency.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Logical Storage
Physical volumes
1 4 1 4
7 2 3 7 2 3
10 10
8 9 8 9
13 16 13 16
14 15 19 14 15
19 22 22
20 21 25 20 21
25 28 28
26 27 31 26 27
31 34 34
32 33 32 33
35 38 35 38
36 37 41 36 37
41 44 44
42 43 42 43
47 50 47 50
48 49 48 49
1 2 3 4 1 2 3 4 Logical
Partitions
Logical Logical
volume volume
© Copyright IBM Corporation 2005
Notes:
Logical partition
A physical partition is the smallest unit of allocation of disk. Each logical partition maps
to a physical partition which physically stores the data.
Obviously, the logical partitions within a volume group are the same size as the physical
partitions within that volume group.
Logical volume
A logical volume consists of one or more logical partitions within a volume group.
Logical volumes may span physical volumes if the volume group consists of more than
one physical volume. Logical volumes do not need to be contiguous within a physical
volume because the logical partitions within the logical volume are maintained to be
contiguous. The view the system sees is the logical one. Thus, the physical partitions
they point to can reside anywhere on the physical volumes in the volume group.
Uempty Logical volumes may be increased in size at any time, assuming that there are sufficient
free physical partitions within the volume group. This can be done dynamically through
SMIT even when users are doing work in that logical volume. However, logical volumes
cannot easily be decreased and require a file system backup and restore to a
re-created smaller logical volume.
The mapping of which logical partition corresponds to which physical partition is
maintained in the VGDA for the volume group. It is both a physical view and a logical
view.
LVM mapping
The Logical Volume Manager (LVM) consists of the logical volume device driver (LVDD)
and the LVM subroutine interface library. The LVM controls disk resources by mapping
data between a more simple and flexible logical view of storage space and the actual
physical disks. The LVM does this using a layer of device driver code that runs above
traditional disk device drivers.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the terms LV and LP.
Details — Define the terms in connection with the physical side of things. Also point out:
• Data can be placed on any disk/partition within the VG. This will obviously cause
fragmentation, as there are no restrictions as to where the data should be placed. The
operating system needs to have a contiguous view of all the data and so it creates LVs.
• The naming convention used for system defined LVs is /dev/hdx and for user created
LVs (if a name is not specified) is /dev/lvxx.
• An LV can only contain one file system. Although we have not defined file systems yet,
it is important to mention this here and warn the students that there will be more on file
systems coming up. It is very important to establish a clear relationship between an LV
and a file system and to stress that these go hand in hand.
• A LP is always the same size as a PP.
More details on the AIX physical partition enhancements will be covered in the next unit.
Additional Information —
Transition Statement — Now that you know what a logical volume is, how are they used?
Uempty
Uses of Logical Volumes
• A logical volume may contain one of the following, and only one
at a time:
– Journaled (JFS) or enhanced journaled file system (JFS2)
– Journal log (/dev/hd8)
– Paging space (/dev/hd6)
– Boot logical volume (/dev/hd5)
– Dump device
– Nothing (raw logical volume)
• Examples of JFS/JFS2 logical volumes:
/dev/hd1 /home
/dev/hd2 /usr
/dev/hd3 /tmp
/dev/hd4 /
/dev/hd9var /var
/dev/hd10opt /opt
/dev/lv00 /myfilesystem)
© Copyright IBM Corporation 2005
Notes:
Introduction
When you install the system, you automatically create one volume group (rootvg)
which consists of a base set of logical volumes required to start the system. rootvg
contains such things as paging space, the journal log, and boot data, each usually in its
own separate logical volume.
You can create additional logical volumes with the mklv command or go through the
SMIT menus. This command allows you to specify the name of the logical volume and
to define its characteristics.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Journal log
The journal log is the logical volume where changes made to the file system structure
are written until such time as the structures are updated on disk. Journaled file systems
and enhanced journaled file systems is discussed in greater detail later in the course.
Paging space
Paging space is fixed disk storage for information that is resident in virtual memory but
is not currently being maintained in real memory.
Dump device
When you install the operating system, the dump device is automatically configured for
you. By default, the primary device is /dev/hd6, which is the paging logical volume, and
the secondary device is /dev/sysdumpnull. For systems migrated from versions of AIX
earlier than V4.1, the primary dump device is what it formerly was, /dev/hd7.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
A file system is a directory hierarchy for storing files. It has a root directory and
subdirectories. In an AIX system, the various file systems are joined together so that
they appear as a single file tree with one root. Many file systems of each type can be
created.
Because the available storage is divided into multiple file systems, data in one file
system could be on a different area of the disk than data of another file system.
Because file systems are of a fixed size, file system full errors can occur when that file
system has become full. Free space in one file system cannot automatically be used by
an alternate file system that resides on the same physical volume.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define what a file system is.
Details — You can have many different file systems connected under the hierarchical tree.
However, from an end user's point of view, everything looks the same.
The student should be familiar with the concept of files and directories.
Typically, the students will be using JFS or JFS2 file systems, the default types of file
systems for AIX. We will consider journaling a little later on. But, these are files that exist on
your local disks. However, there is a feature where remote file systems can also be made
to appear as if they belong and reside on your local disks, this being network file systems.
We will not be discussing NFS in this course. There are also cache file systems that are
related to NFS. Students may discover this when creating file systems.
Additional Information — JFS and JFS2 use journaling techniques to maintain their
structural integrity. This will be discussed in more detail later in this unit. The network file
system (NFS) is a distributed file system that allows users to access files and directories
located on remote computers and use them as if they were on the local system. Further
discussion of this type of file system is beyond the scope of this course. CD-ROM file
system is a type that allows access to the contents of a CD-ROM through normal file
system interfaces.
Discussion Items - Ask the students if they know what the CD-ROM file system is
commonly used for?
Answer: In AIX V4.2 and earlier, the CD-ROM file system was often used for InfoExplorer.
In AIX V4.3 and later, the CD-ROM file system may be used for the Web-based
documentation.
There is a another file system, PROCFS, it is not actually on any disk but is mapped to
memory for used by the operating system in recording stats.
Transition Statement — Why do we use file systems in AIX?
Uempty
Why Have Multiple File Systems
• Can strategically place it on disk for improved
performance
• Some tasks are performed more efficiently on a file
system than on each directory within the file system, for
example, back up, move, secure an entire file system
• Can limit disk usage of users by file system (quotas)
• Maintain integrity of the entire file system structure, for
example, if one file system is corrupted, the others are not
affected
• Special security situations
• Organize data and programs into groups for ease of file
management and better performance
Notes:
Benefits
A file system is a structure that allows you to organize your data. It is one level in the
hierarchy of you data. By placing data in separate file systems, it allows for ease of
control and management of the data.
File systems can be placed on the disk in areas that provide the best performance.
Many times, backups and recoveries are done at a file system level.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
/ (root)
home sbin opt lpp proc usr dev tftpboot var mnt etc tmp
/ / / / /
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the standard AIX file systems.
Details — The picture shows all the default AIX file systems connected to their default
mount points. Explain that each file system connects to the tree by an empty directory
which is commonly known as the mount point.
Also, highlight that every file system must reside on a logical volume. Remind the students
of the default AIX file systems and their logical volumes which have all been labeled on the
diagram.
Have a discussion as to how big the file systems are, pointing out that /usr is the largest.
As the system is customized, these file systems can be extended to hold new applications
and user data, or new file systems can be created. The choice as to when and how to do
this depends upon the users and applications on the system. The usual recommendations
are not to add user applications or data to /, /usr or /var because these will be removed if
the system is ever reinstalled, and only use /tmp as a scratch area. Create new file
systems as needed for applications and data.
Additional Information — On a networked system, diskless/dataless or in a code serving
environment, some (or all) of these may be remotely accessed via the Network File System
(NFS).
/lib is actually a symbolic link to /usr/lib. /bin is actually a symbolic link to /usr/bin.
Transition Statement — Let's take a moment to review the terms we have just learned.
Uempty
Let’s Review
5. V______ G______
1. V______ G______
D ______ A______
VGDA 6. P______ V______
2. P______ P ______
3. L_____ P______
4. L______ V_______
© Copyright IBM Corporation 2005
Notes:
Instructions
Label the items shown in the picture above.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Give the students a chance to review the different terms.
Details — This is a usually a good place for a break. During the break have the students
label the items on the visual to review the terminology.
5. Volume Group
1. Volume Group___
Descriptor Area__
VGDA 6. Physical Volume
2. Physical Partition
3. Logical Partition
4. Logical Volume
© Copyright IBM Corporation 2005
Additional Information — As you are going over the answers, also review these points
with the students.
• PVs have a naming convention of /dev/hdiskx where x is a number allocated by the
operating system. It is usually the next available number.
• A PV can only belong to one VG.
• There can be many VGs defined on one system. These can be used to separate out the
operating system from the application code, from the application data, and so forth.
There can be up to 255 VGs per system.
• The default VG that contains the operating system is rootvg which is created by
default.
Uempty • Since most disks are larger than 4 GB, the PP size will normally need to be changed.
PP size can be changed in increments of the power of 2 up to 1024 MB, unless the
-t factor is changed or a scalable VG is used.
• The default limit for the number of physical partitions per physical volume is 1016. AIX
provides support for multiples of 1016 PPs per PV, up to a maximum of 130,048 PPs
per PV. Be aware that if you choose to have more than 1016 PPs per PV, you will
decrease the maximum number of physical volumes supported in the volume group.
Again this is for non-scalable VGs. Scalable VGs do not use the -t factor and do not
have this trade off for a given PV; With scalable VGs, the maximum PPs are managed
as a pool for the entire VG.
Transition Statement — Let’s continue by discussing the /etc/filesystems file.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
/etc/filesystems
/:
dev = /dev/hd4
vol = root
mount = automatic
check = false
vfs = jfs
log = /dev/hd8
type = bootfs
/home:
dev = /dev/hd1
vol = /home
mount = true
check = true
vfs = jfs
log = /dev/hd8
/home/team01:
dev = /dev/fslv00
vfs = jfs2
log = /dev/loglv00
mount = true
options = rw
account = false
© Copyright IBM Corporation 2005
Notes:
What is /etc/filesystems?
The /etc/filesystems file documents the layout characteristics, or attributes of file
systems. It is in a stanza format which means a resource is named followed by a colon
and a listing of its attributes in the form of attributes = value.
Each stanza in the /etc/filesystems file names the directory where the file system is
normally mounted.
Uempty vol Used by the mkfs command when initiating the label on a new file
system.
mount Used by the mount command to determine whether a file system
should be mounted by default. Possible values are:
automatic File system mounted automatically at system startup.
true File system mounted by the mount all command.
This command is issued during system initialization to
automatically mount such file systems.
false File system will not be automatically mounted.
check Used by the fsck command to determine the default file systems to be
checked. True enables checking.
vfs Specifies the type of mount. For example, vfs=jfs2.
log The device to which log data is written, as the file system is modified.
(This option is only valid for journaled file systems).
type Used to group together related file systems which can all be mounted
with the mount -t command.
account Used to determine the file systems to be processed by the accounting
system.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the contents of the /etc/filesystems file.
Details — The /etc/filesystems file serves two purposes:
• Documents the layout characteristics of the file system
• Frees the person who sets up the file system from having to enter and remember items
such as the device where the file system resides, because the information is defined in
this file
Each stanza names the directory where the file system is normally mounted.
Note: From AIX File System Development - Austin, the free parameter in /etc/filesystems
free = true
is there because it is a component of traditional UNIX systems. The df command in
traditional UNIX would use it to determine which file systems to report. It is totally ignored
by any and all AIX commands.
Additional Information — UNIX system administrators who are familiar with other flavors
of UNIX may wish to compare this file to /etc/fstab or /etc/vfstab.
Transition Statement — In the /etc/filesystems file the term mount is used. What is
mounting?
Uempty
Mount
•mount is the glue that logically connects file systems to the
directory hierarchy
• File systems are associated with devices represented by
special files in /dev (the logical volume)
• When a file system is mounted, the logical volume and its
contents are connected to a directory in the hierarchical tree
structure
What to Where to
mount mount it
© Copyright IBM Corporation 2005
Notes:
Mount points
Full path names must be used when specifying the mount point. If SMIT is used to
create the file system, the mount point is created automatically.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To describe what mounting is.
Details — The process of mounting is a key piece to understanding how the individual file
systems are joined to form the view of the system the user sees. A file system has to be
mounted in order for it to be available for use.
The mount command has many options. The visual shows an example of this command. In
the example, /dev/lv00 is the logical volume and /home/patsie is the mount point. This is
the mount point that we will use in the examples on the next two pages. The mount point is
always a directory and it should be empty.
Additional Information — mount=automatic is reserved for those file systems, such as
/ (root), which are necessary for the boot process. The attribute of mount=true is the
proper way to automatically mount a user defined file system at system reboot.
Transition Statement — Let's look at the directory tree structure before and after a file
system is mounted.
Uempty
Mounting Over an Empty Directory
Before... After...
home home
.profile .profile
.exrc data doc .exrc data doc
myscript myscript
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how file systems are connected to form a single view to users.
Details — Discuss how even though each file system is a separate entity, they are
connected together via the mount point directories so that the system of files and
directories are seen as one large file system to end users.
In the example shown, /home/patsie is the mount point. Again, mention that the mount
point must be a directory and it should be empty. The next page will illustrate what happens
if the mount point is not empty.
Additional Information — While the student notes state that the user does not see the
difference between file systems, this is only true for the navigation of the tree structure.
There are situations where the user will be aware of working with separate file systems. For
example, hard links can only be built if the source and target are in the same file system;
otherwise a symbolic link must be used. Another example is the use of the mv command
with very large files. If the source and target are in the same file system, then mv is an
almost instantaneous rename. If they are in different file systems, then the data has to be
copied to the target file system before deleting the original file and the move takes much
longer.
Transition Statement — Since file systems can be mounted on a directory which has the
required permissions, they can be “mounted over” directories that have files in them. Let's
see what happens if you do this.
Uempty
Mounting Over Files
Before... After...
home home
.profile
.exrc data doc
myscript
.profile
.exrc data doc
myscript
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show that file systems can be mounted over existing files and directories.
Details — Simply show students how this can happen and stress that the files don't go
anywhere, they are still there. They simply can't be accessed while the file system is
mounted over the directory that contains the files.
Additional Information —
Transition Statement — How can you tell what file systems are on the system?
Uempty
Listing File Systems
# lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs 32768 -- yes no
/dev/hd1 -- /home jfs2 90112 -- yes no
/dev/hd2 -- /usr jfs 1277952 -- yes no
/dev/hd9var -- /var jfs 65536 -- yes no
/dev/hd3 -- /tmp jfs 65536 -- yes no
/dev/cd0 -- /infocd cdrfs -- ro yes no
/dev/lv00 -- /home/john jfs2 32768 rw yes no
/proc -- /proc procfs -- -- yes no
/dev/hd10opt -- /opt jfs 65536 -- yes no
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List all the file systems defined on the system.
Details — The information displayed is as follows:
Name The device (LV or CD-ROM) or remote directory name
Nodename (NFS only) the remote system name
Mount Pt The directory which is the mount point
VFS Virtual file system type: jfs = journaled file system,
jfs2 = enhanced journaled file system, cdrfs = CD-ROM,
nfs = network file system
Size Size in 512 byte blocks (data is allocated in 4KB clusters)
Options mount options, options attribute in /etc/filesystems
Auto Mount at system startup, mount attribute in /etc/filesystems
Account Advanced accounting turned on for this file system
Please note that when the lsfs command is executed, the output of the command will be
slightly different if accounting is on as accounting information will also be shown.
Additional Information —
Transition Statement — Let's see how we can list all the logical volumes on a system.
Uempty
Listing Logical Volume Information
# lsvg -l rootvg
LVNAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd6 paging 64 64 1 open/syncd N/A
hd5 boot 1 1 1 closed/syncd N/A
hd8 jfslog 1 1 1 open/syncd N/A
hd4 jfs 2 2 1 open/syncd /
hd2 jfs 156 156 1 open/syncd /usr
hd9var jfs 1 1 1 open/syncd /var
hd3 jfs 3 3 1 open/syncd /tmp
hd1 jfs2 1 1 1 open/syncd /home
hd10opt jfs 2 2 1 open/syncd /opt
lv00 jfs2 2 2 1 open/syncd /home/john
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List the attributes of a logical volume.
Details — Do not spend too much time going through all the attributes. This will be covered
in more detail in the next unit.
Additional Information —
Transition Statement — Now, it’s time for some checkpoint questions.
Uempty
Checkpoint (1 of 3)
1. How many different physical partition (PP) sizes can be
set within a single VG? ____________
2. By default, how big are PPs?
____________________________________________
____________________________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions (1 of 3)
Additional Information —
Transition Statement — Let’s continue with more checkpoint questions.
Uempty
Checkpoint (2 of 3)
Use the following output to answer the questions below:
# lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs 8192 -- yes no
/dev/hd1 -- /home jfs 90112 -- yes no
/dev/hd2 -- /usr jfs 507904 -- yes no
/dev/hd9var -- /var jfs 8192 -- yes no
/dev/hd3 -- /tmp jfs 16384 -- yes no
/dev/hd10opt -- /opt jfs 65536 -- yes no
/dev/cd0 -- /infocd cdrfs ro yes no
/dev/lv00 -- /home/john jfs 8192 rw yes no
5. With which logical volume is the /home file system associated? __________
6. What type of file systems are being displayed? ________________________
_______________________________________________________________
7. What is the mount point for the file system located on the /dev/lv00 logical
volume? ________________________
8. Which are the system supplied logical volumes and their associated file
systems? ______________________________________________________
_______________________________________________________________
9. Which file system is used primarily to hold user data and home directories?
____________________
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions (2 of 3)
Use the following output to answer the questions below:
# lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs 8192 -- yes no
/dev/hd1 -- /home jfs 90112 -- yes no
/dev/hd2 -- /usr jfs 507904 -- yes no
/dev/hd9var -- /var jfs 8192 -- yes no
/dev/hd3 -- /tmp jfs 16384 -- yes no
/dev/hd10opt -- /opt jfs 65536 -- yes no
/dev/cd0 -- /infocd cdrfs ro yes no
/dev/lv00 -- /home/john jfs 8192 rw yes no
5. With which logical volume is the /home file system associated? /dev/hd1
6. What type of file systems are being displayed? Journaled file systems (JFS),
enhanced journaled file systems (JFS2), and CD-ROM (CDRFS)
7. What is the mount point for the file system located on the /dev/lv00 logical
volume? /home/john
8. Which are the system supplied logical volumes and their associated file
systems? /dev/hd4 (/), /dev/hd1 (/home), /dev/hd2 (/usr), /dev/hd9var (/var),
/dev/hd3 (/tmp), /dev/hd10opt (/opt)
9. Which file system is used primarily to hold user data and home directories?
/home
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Let’s continue with more checkpoint questions.
Uempty
Checkpoint (3 of 3)
Use the following output to answer the question below:
# lsvg -l rootvg
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions (3 of 3)
Use the following output to answer the question below:
# lsvg -l rootvg
Additional Information —
Transition Statement — Now, let’s do an exercise.
Uempty
Exercise 9: LVM Commands
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review the exercise.
Details —
Additional Information —
Transition Statement — Let’s summarize what we’ve learned in this unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 9. System Storage Overview 9-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — Now, unto the next unit.
References
Online System Management Guide: Operating System and
Devices
GG24-4484 AIX Storage Management
SG24-5432 Logical Volume Manager from A to Z: Introduction and
Concepts Redbook
SG24-5433 Logical Volume Manager from A to Z: Troubleshooting
and Commands Redbook
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Volume Groups
Logical Volumes
Physical Volumes
Paging Space
Notes:
Introduction
The SMIT Logical Volume Manager menu is used to manage many aspects of the
system's storage. The Web-based System Manager can also be used to manage the
Logical Volume Manager.
Volume groups
The SMIT Volume Groups menu provides facilities to manipulate the volume groups in
the system.
Physical volumes
The SMIT Physical Volumes menu allows the user to configure the physical volumes
(fixed disks) in the system. This menu duplicates options on the Fixed Disks menu of
Devices.
Paging space
The SMIT Page Space menu allows a user to add, delete, activate and list the paging
spaces available.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the options available through SMIT for the LVM.
Details — Use this visual as a roadmap to further discussion of the Logical Volume
Manager and its structure. If you have two overhead projectors you may wish to leave this
up until you get to the next SMIT visual for volume groups. We will consider the first three
options of the screen in this unit. The paging space option will be described in the Paging
Space unit.
Additional Information —
Transition Statement — First, let's do a quick review of volume group concepts.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Volume Groups
Volume group
PV PV
Notes:
Physical volume
A physical volume is an actual disk or hard disk. There is a limit of 128 physical volumes
per volume group unless it is a scalable volume group which can have up to 1024
physical volumes. A physical volume that supports removable media should be
assigned to a volume group containing itself and no other members.
Volume group
A volume group is a collection of related physical volumes on a processor that:
- Are not members of another volume group
- Share a single physical partition size
When you install your AIX system, one volume group called rootvg is automatically
created.
There can be a maximum of 255 volume groups per system.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lsvg
rootvg
payrollvg
# lsvg -o
rootvg
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lsvg rootvg
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 159 52 24..00..00..00..28
hdisk1 active 159 78 32..02..00..12..32
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lsvg -l rootvg
rootvg:
LVNAME TYPE LPs PPs PVs LV STATE MOUNT POINT
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
VOLUME GROUP name []
Physical partition SIZE in megabytes +
* PHYSICAL VOLUME names [] +
FORCE the creation of volume group? no +
Activate volume group AUTOMATICALLY yes +
at system restart?
Volume group MAJOR NUMBER [] +#
Create VG Concurrent Capable? no +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show students how to add a volume group.
Details — After installation, the system has only one volume group containing the
operating system and that is the rootvg. Other physical volumes that are not in a volume
group can be grouped together into additional volume groups.
Note that physical partition size is a value of 1-1024 MB, and must be equal to the power of
2. The default size is 4 MB. Sizes of 512 MB and 1024 MB are valid for AIX V4.3.1 and
later.
The menu item dealing with concurrent mode is used only if in the HACMP environment,
and is supported in AIX V4.2 and later.
Additional Information —
Transition Statement — Let us look at how adding a scalable volume group differs.
Uempty
Add a Scalable Volume Group
# smit mkvg
[Entry Fields]
VOLUME GROUP name []
Physical partition SIZE in megabytes +
* PHYSICAL VOLUME names [] +
FORCE the creation of volume group? no +
Activate volume group AUTOMATICALLY yes +
at system restart?
Volume group MAJOR NUMBER [] +#
Create VG Concurrent Capable? no +
Max PPs per VG in kilobytes 32 +
Max Logical Volumes 256 +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To explain the AIX 5L V5.3 scalable volume group creation options.
Details — Warn the students not to make the maximums larger than they really need them
to be. The increased size of the control block structures can have a detrimental impact on
performance.
Additional Information —
Transition Statement — Now, let us move on to how we can manage the volume group
after it has been created.
Uempty
Set Characteristics of a Volume Group
# smit vgsc
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the menu of items to be covered on the following visuals.
Details — Note that we will not cover the last item on reorgvg until after discussing logical
volume allocation.
Additional Information —
Transition Statement — First, let us look at what we can do to change the volume group
attributes.
Uempty
Change a Volume Group
# smit chvg
Change a Volume Group
[Entry Fields]
* VOLUME GROUP name rootvg
* Activate volume group AUTOMATICALLY yes +
at system restart?
* A QUORUM of disks required to keep the volume yes +
group on-line ?
Convert this VG to Concurrent Capable? no +
Change to big VG format? no +
Change to scalable VG format? no +
LTG Size in kbytes 128 +
Set hotspare characteristics n +
Set synchronization characteristics of stale n +
partitions
Max PPs per VG in kilobytes 32 +
Max Logical Volumes 256 +
Notes:
Quorum of disks
The SMIT option A QUORUM of disks required to keep the volume group on-line?
determines if the volume group is automatically varied off (deactivated) after losing its
quorum of physical volumes. Selecting no means that the volume group stays active
until it loses all of its physical volumes. However, if this option is set to no then you are
in danger of having backdated VGDAs. To activate a non-quorum user-defined volume
group, all of the physical volumes within the volume group must be accessible or the
activation fails.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the LTG size.
Details — The LTG size is specified either in K or M units implying KB or MB respectively.
When the LTG size is set using the -M flag, the varyonvg and extendvg commands may
fail if an underlying disk has a maximum transfer size that is smaller than the LTG size.
If the -M flag is not used, the varyonvg command will select the optimal LTG size
automatically. This optimal size is the largest common maximum transfer size among the
underlying disks. If an extendvg or reducevg command is subsequently executed and the
optimal LTG size changes, the LVM driver will correct the LTG size on the fly. That is, it will
hold the I/O, modify the LTG size, and then resume.
The lspv command (which will be discussed later) will display the same value as lquerypv
-M but will be shown as MAX REQUEST.
Additional Information — Mention that this is a performance, not a function oriented
option.
Transition Statement — Now, let us move on to the availability topic of hot spares.
Uempty
Hot Spare
Synchronization
Hot spare
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
- Hot spare disks must have at least equal capacity to the smallest disk already in the
volume group. Good practice dictates having enough hot spares to cover your
largest mirrored disk.
Set the hot spare migration policy for the volume group
The chvg -h command sets the migration policy for the volume group. The following
table shows the arguments that can be used with the chvg -h command:
chvg -h
Description
argument
Permits one for one migration of partitions from one failed disk to
y (lower case) one spare disk. From the pool of hot spare disks, the smallest one
which is big enough to substitute for the failing disk will be used.
Migrates partitions from a failing disk to one or more hot spare
Y (upper case)
disks; might use the complete pool of hot spare disks.
n No automatic migration will take place. (Default)
Removes all disks from the pool of hot spare disks for this volume
r
group.
For example, to set an automatic migration policy which uses the one smallest hot
spare disk that is large enough to replace the failing disk in the datavg volume group,
use the command:
# chvg -hy datavg
Set the hot spare synchronization policy for the volume group
The chvg -s command is used to specify the synchronization characteristics. The
following two values are valid for the synchronization argument:
chvg -s
Description
argument
y Automatically attempts to synchronize stale partitions.
n Will not automatically attempt to synchronize stale partitions. (Default)
For example, to automatically synchronize stale partitions for the datavg volume group,
use the command: chvg -sy datavg
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the new LVM hot spare function.
Details — Mention that hot spare capability is a major advantage to the unattended data
center. A data center that is attended, but not 24X7, or has limited system administrator
attention would also benefit from hot spares.
These commands are not replacements for the sparing support available with SSA and
SCSI disk arrays; they complement it. You can also use it with SSA and SCSI disk arrays
when you add one to your volume group.
Additional Information — Review the steps for setting up hot sparing with the students;
emphasize the planning and decision making aspects.
Transition Statement — Let's discuss adding physical volumes or removing physical
volumes from the volume group.
Uempty
Extending and Reducing Volume Groups
hdisk4 hdisk5
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
* VOLUME GROUP name [] +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
varyonvg [ -f ] Volumegroup
# varyonvg datavg
varyoffvg Volumegroup
# varyoffvg datavg
Notes:
Uempty In AIX 5L V5.3 a new option -M was added to allow the specification of a logical track
group size for the volume group, instead of allowing LVM to determine it dynamically.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show how volume groups, other than the rootvg, can be activated and
deactivated.
Details — With non-rootvg volume groups, a useful operation that can be done is to
deactivate the volume group, with the option of removing the volume group completely
from the system (provided the volume group is on an external disk pack).
This proves very useful especially in high security environments, where the volume group
can be kept on external disks, and at night the entire volume group can be deactivated and
disconnected. The external disk pack can then be physically removed and placed in a safe
place where it can locked away until the next day. In the morning the volume group can be
activated again.
Before the varyoffvg command can be used, the logical volumes within it must first be
closed. For example, if the logical volume contains a file system, it must be unmounted.
A volume group that has a paging space on it cannot be varied off while the paging space
is active.
Additional Information —
Transition Statement — Volume groups can be moved from one system to another. Let's
see how this can be done.
Uempty
Import/Export a Volume Group
# smit importvg
[Entry Fields]
VOLUME GROUP name []
* PHYSICAL VOLUME name [] +
Volume Group MAJOR NUMBER [] +#
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to export and import a volume group.
Details — There may be times when a volume group may need to be moved from one AIX
system to another so that the logical volume's and file system's data in the volume group
can be accessed directly on the target system. It may be necessary to remove all
knowledge of a volume group from the system if the file system and logical volume within it
are no longer being accessed.
To remove all knowledge of a volume group from the ODM database, the volume group
needs to be exported. This command does not remove any user data in the volume group,
but only removes its definition from the ODM database.
Similarly, when a volume group is moved, the target system needs to be made aware of the
new volume group. This is done by importing. Importing reads the data in the VGDA to
build the ODM entries.
Once exported, a volume group can no longer be accessed on the system it was exported
from. rootvg cannot be exported because you cannot vary it off.
Once a volume group is changed or created to hold more than 1016 physical partitions per
physical volume (as supported beginning with AIX V4.3.1), it cannot be imported into AIX
versions earlier than V4.3.1. Also, volume groups created in AIX V4.3.1 or later using a
physical partition size of 512 MB or 1024 MB cannot be imported into previous versions of
AIX.
Additional Information — A volume group with a mirrored striped logical volume cannot
be back ported into a version older than AIX 4.3.3.
When importing the volume group, if you do not specify the volume group name (with the
importvg -y flag), it will use the generic name like vg00 or vg01. The previous volume
group name is not the default name when the volume group is imported.
Unless instructed to do so by support personnel, never interrupt an LVM command.
Transition Statement — There are some special concerns in defining and managing
RAID devices with the Logical Volume Manager.
Uempty
Advanced RAID Support
• Checks all disks in a volume group if they have grown in
size:
chvg -g Volumegroup
# chvg -g datavg
# chvg -b y datavg
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Bad block relocation policy should be turned off for RAID devices and storage
subsystems unless the manufacturer tells you otherwise.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Logical Storage
Physical volumes
1 4 1 4
7 2 3 7 2 3
10 10
8 9 8 9
13 16 13 16
14 15 19 14 15
19 22 22
20 21 25 20 21
25 28 28
26 27 31 26 27
31 34 34
32 33 32 33
35 38 35 38
36 37 41 36 37
41 44 44
42 43 42 43
47 50 47 50
48 49 48 49
1 2 3 4 1 2 3 4 Logical
Partitions
Logical Logical
volume volume
© Copyright IBM Corporation 2005
Notes:
Logical volumes
A logical volume is a group of logical partitions which may span physical volumes (as
long as the physical volumes are in the same volume group). A file system resides on
top of a logical volume (LV). A logical volume can be dynamically extended.
Logical partitions
Logical partitions are mapped one-to-one to physical partitions unless they are being
mirrored.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Mirroring
hdisk0 lv00
First copy PP1
PP2 LP1
LP2
hdisk1
Second copy PP1
PP2
hdisk2
Third copy PP1
PP2
• Scheduling policy:
Parallel: Physical partitions written simultaneously
Sequential: Physical partitions written in sequence
© Copyright IBM Corporation 2005
Notes:
Mirroring concept
Mirroring of data over multiple drives protects against a potential hardware failure. The
structure of LVM enables mirroring by manipulating the relationship between the
physical partition and the logical partition.
The AIX mirror function does not apply to a physical disk, only to logical volumes. This
is the most important principle to understand for the AIX LVM mirroring function.
In a normal operating environment each physical partition is mapped to a logical
partition. When you mirror data, the ratio becomes one logical partition to two physical
partitions for a two-way mirror. Or, one logical partition to three physical partitions for a
three-way mirror.
Sequential write
Sequential mirroring performs writes to multiple copies or mirrors in order. The multiple
physical partitions representing the mirrored copies of a single logical partition are
designated primary, secondary, and tertiary. In sequential scheduling, the physical
partitions are written to in sequence. The system waits for the write operation for one
physical partition to complete before starting the write operation for the next one. When
all write operations have been completed for all mirrors, the write operation is complete.
Parallel write
Parallel mirroring simultaneously starts the write operation for all the physical partitions
in a logical partition. When the write operation to the physical partition that takes the
longest to complete finishes, the write operation is completed.
Sequential read
When a sequential read is specified, the primary copy of the read is always read first. If
that read operation is unsuccessful, the next copy is read. During the read retry
operation on the next copy, the failed primary copy is corrected by LVM with a hardware
relocation. This patches the bad block for future access.
Parallel read
On each read, the system checks whether the primary is busy. If it is not busy, the read
is initiated on the primary. If the primary is busy, the system checks the secondary and
then the tertiary. If those are also busy, the read is initiated in the copy with the least
number of outstanding I/Os.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Round-robin read
Round-robin reads alternate between copies. This results in equal utilization for reads
even when there is more than one I/O outstanding.
Synchronizing
When turning on mirroring for an existing logical volume, the copies have to be
synchronized so the new copy contains a perfect image of the existing copy at that point
in time. This can be done by using the -k option on the mklvcopy command at the time
mirroring is turned on or with the syncvg command at a later time. Until the copies are
synchronized, the new copy is marked stale.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Read
request
Forced synchronization
Notes:
Introduction
Mirror Write Consistency (MWC) ensures data consistency on logical volumes in case a
system crash occurs during mirrored writes. The active method achieves this by logging
when a write occurs. LVM makes an update to the MWC log that identifies what areas of
the disk are being updated before performing the write of the data. Records of the last
62 distinct logical transfer groups (LTG) written to disk are kept in memory and also
written to a separate checkpoint area on disk (MWC log). This results in a performance
degradation during random writes.
With AIX 5L V5.1 and later, there are two ways of handling MWC:
- Active, the existing method (prior to AIX 5L V5.1)
- Passive, the new method (beginning with AIX 5L V5.1)
MWC settings
The following syntax is used with either the mklv or chlv command to set MWC
options:
mklv -w y|a|p|n
chlv -w y|a|p|n
Following is a description of the MWC arguments:
Argument Meaning Description
Each write is logged to the MWC log. When the volume
Yes or group is varied back online, the log is used to make logical
y or a
Active partitions consistent. This is the default for mirrored logical
volumes.
The volume group logs that the logical volume has been
opened. After a crash when the volume group is varied on,
an automatic forced synchronization of the logical volume is
p Passive
started. Consistency is maintained while the
synchronization is in progress by propagating the blocks
being read to the other mirrors in the logical volume.
The mirrors of a mirrored logical volume can be left in an
inconsistent state in the event of a system or volume group
n No
crash. There is no automatic protection of mirror
consistency.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Differentiate the active and passive options of MWC.
Details — If crash occurs, upon reboot the last 62 writes to mirrors are examined and one
of the mirrors is used as a source to synchronize the mirrors. For sequential mirroring, the
latest write that occurred is guaranteed to be completed, since there is a definite PRIMARY
disk which is used as the source for synchronization. For parallel mirroring, all mirrors are
guaranteed to be consistent, but the latest write is not guaranteed to be completed after the
crash.
Stress that the passive method reduces write time during normal processing. It actually
increases recovery time; since crashes are relatively rare it improves performance over all.
Additional Information —
Transition Statement — Another thing that you can do with logical volumes is spread the
data across physical volumes using a technique called striping.
Uempty
Striping
• Normal flow of data blocks when a logical volume is spread across
physical volumes:
1 2 3 4 5 6 13 14 15 16 17 18 25 26 27 28 29 30
7 8 9 10 11 12
19 20 21 22 23 24 31 32 33 34 35 36
1 4 7 10 13 16 2 5 8 11 14 17 3 6 9 12 15 18
19 22 25 28 31 34 20 23 26 29 32 35 21 24 27 30 33 36
Notes:
Overview
Striping is a technique for spreading the data in a logical volume across several disks
such that the I/O capacity of the disk drives can be used in parallel to access data on
the logical volume.
Striping is designed to increase the read/write performance of frequently accessed,
large sequential files. Striping can also be used to simply distribute data evenly across a
set of disks so that random I/O can be scattered across many drives simultaneously.
In non-striped logical volumes, data is accessed using addresses to data blocks within
physical partitions. In a striped logical volume, data is accessed using addresses to
stripe units.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Stripe size
The size of the stripe unit is specified at creation time.
Prior to AIX 5L V5.3, the stripe size could range from 4 KB -128 KB in powers of 2
(4 KB, 8 KB, 16 KB, 32 KB, 64 KB, and 128 KB). AIX 5L V5.3 supports the following
stripe sizes: 4 KB, 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, 1 MB, 2 MB, 4 MB, 8 MB,
16 MB, 32 MB, 64 MB, and 128 MB.
Constraints
There are some constraints imposed by implementing striping:
- The number of physical partitions allocated to a striped logical volume must be able
to be evenly distributed among the disks
- At least two physical volumes are required
Performance considerations
There are some considerations in configuring striping for performance:
- Use as many adapters as possible. For example, if multiple disks in the stripe width
are on the same SCSI adapter, a read/write of a stripe will not be able to read/write
the stripe units in parallel.
- Design to avoid contention with other uses of the disks used by the striped logical
volume.
- Create on a volume group dedicated to striped logical volumes
It is not a good idea to mix striped and non-striped logical volumes in the same physical
volume. Physical volumes should be the same size (ideally) within the set used for a
striped logical volume.
Just because a logical volume is striped does not mean that the file’s data blocks are
going to be perfectly aligned with the stripe units. Therefore, if a file block crosses a
stripe boundary, the block gets split up into multiple LVM I/Os.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Striped Columns
Striped logical volume: strip width = 3, upper bound = 6
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
E M C M E
Inner Edge
Inner Middle
Center
Outer Middle (Middle)
Center Edge (Edge)
Notes:
Introduction
When creating or changing a logical volume you can define the way the Logical Volume
Manager decides on which physical partitions to allocate to the logical volume. This
affects the performance of the logical volume.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the logical volume allocation policies.
Details — By default, you do not have to worry where a logical volume is placed on disk
and on which disk it is placed. The LVM handles all the policies for you. However, if you
have a specific requirement you can specify this through SMIT. Policies can also be
changed after you have set up the logical volume. However, this operation requires a little
bit of work because the volume group has to be reorganized.
Additional Information — Ask the students why, in their opinion, certain logical volumes
are good candidates to be placed either at the center or on the edge.
Answer: Disk devices have locations that they can access quicker than others. Based on
the disk documentation, you can select the area on disk that best suits your needs.
Logical volumes on 200 MB, 540 MB and 1 GB disks that contain large sequential files
should be at the edge because sequential performance is better there (there are more
blocks per track at the edge than farther in).
For inter-physical policy, choose 'minimum' on non-mirrored logical volumes to provide the
greatest availability (access to data in case of hardware failure). With this option, you
reduce the risk of losing data because of a disk failure. Each additional physical volume
used for a single physical copy increases that risk.
The 'maximum' setting spreads the physical partitions of the logical volume as evenly as
possible over as many physical volumes as possible. This is a performance-oriented option
because spreading the physical partitions over several disks tends to decrease the
average access time for the logical volume.
Transition Statement — Let's look at SMIT's LVM screens.
Uempty
SMIT Logical Volumes Menu
# smit lv
Logical Volumes
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define the SMIT Logical Volumes screen.
Details — Once again, consider many options in turn. Use this as a roadmap for the pages
that follow.
Additional Information —
Transition Statement — Let's first show characteristics of a logical volume.
Uempty
Show Logical Volume Characteristics
• Physical volume map:
# lslv -l lv00
lv00:/home/john
PV COPIES IN BAND DISTRIBUTION
hdisk0 010:000:000 70% 000:000:007:003:000
# lslv -m lv00
lv00:/home/john
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0134 hdisk0
0002 0135 hdisk0
0003 0136 hdisk0
Notes:
lslv -l lvname
The lslv -l lvname command gives information about the distribution of a particular
logical volume's logical partitions for each physical volume. The information includes
the number of logical partitions on the disk and its copies, if any, on that disk; the
percentage of physical partitions which match the intra-physical volume allocation
policy; the distribution of physical partitions on the physical volume (outer edge, outer
middle, center, inner middle, inner edge).
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
COPIES
The COPIES field of the lslv -l lvname command has the following three fields:
- The number of logical partitions containing at least one physical partition (no copies)
on the physical volume
- The number of logical partitions containing at least two physical partitions (one copy)
on the physical volume
- The number of logical partitions containing three physical partitions (two copies) on
the physical volume
The example in the visual, COPIES (010:000:000), can be interpreted as:
- 010 - Information regarding first copy, that is, 10 physical partitions
- 000:000 - These two fields hold information regarding the second and the third
copies, mirrored copies on the physical volume. By looking at this output, you can
tell if the logical volume is mirrored and if the mirrored copies are on the same
physical volume. If they are all on separate physical volumes, which is the default,
the last two fields will still show 000.
IN BAND
The IN BAND field displays the percentage of physical partitions on the physical volume
that belong to the logical volume and were allocated within the physical volume region
specified by Intra-physical allocation policy.
DISTRIBUTION
The DISTRIBUTION field displays the number of physical partitions allocated within each
section of the physical volume: outer edge, outer middle, center, inner middle, and inner
edge.
The example in the visual, DISTRIBUTION (000:000:007:003:000), shows of the 10
physical partitions, 7 physical partitions are located in the center area and 3 physical
partitions in the inner-middle area of the disk. There is a relationship between the
distribution 000:000:007:003:000 and the copies 010:000:000 whereby the 007:003
numbers indicate the distribution of the 010.
lslv -m lvname
The lslv -m lvname command gives a map of which physical volumes contain which
physical partitions for the logical partitions of the logical volume. Three columns are
given, one for each copy of a logical partition.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Uempty the allocation policies for the new partitions to different values than used by the original
logical volume.
The size of a logical volume may not be decreased automatically. To make a logical
volume smaller, back it up, delete it, create a new logical volume of the desired size and
restore the data.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Change the characteristics of a logical volume.
Details — This shows the various logical volume characteristics that can be changed once
a logical volume has been created.
Additional Information —
Transition Statement — Let's see how to list the attributes of a logical volume.
Uempty
List All Logical Volumes By Volume Group
# lsvg -o | lsvg -i -l
rootvg:
LVNAME TYPE LPs PPs PVs LV STATE MOUNT POINT
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List the attributes of a logical drive.
Details — Do not spend too much time going through all the attributes. The student should
by now be familiar with this type of output.
Additional Information —
Transition Statement — Let's look at the characteristics of a particular logical volume on
the next page.
Uempty
Show Logical Volume Characteristics
# lslv lv02
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List the attributes of a logical volume.
Details — The following attributes are specific to logical volumes so spend a few minutes
going through them: WRITE VERIFY, BB POLICY, and WRITE VERIFY. For further information
on these attributes, see the Web-based documentation. Remind the class that Mirror Write
Consistency was described in the previous section about mirroring.
Additional Information — You could pose the following questions:
• If mirroring is set up, which write policy would be used?
Parallel
• Is this logical volume mirrored?
No, because the number of copies is one
Transition Statement — Let's see how to add or remove a mirror.
Uempty
Add Copies to a Logical Volume
# smit mklvcopy
Add Copies to a Logical Volume
[Entry Fields]
* LOGICAL VOLUME name lv00
* NEW TOTAL number of logical partition 2 +
copies
PHYSICAL VOLUME names [] +
POSITION on physical volume middle +
RANGE of physical volumes minimum +
MAXIMUM NUMBER of PHYSICAL VOLUMES [32] #
to use for allocation
Allocate each logical partition copy yes +
on a SEPARATE physical volume?
File containing ALLOCATION MAP []
SYNCHRONIZE the data in the new no +
logical partition copies?
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
* VOLUME GROUP name vg3
LOGICAL VOLUMES [lv04 lv07] +
Notes:
reorgvg syntax
The syntax is: reorgvg volumegroup [lvname]
For example: reorgvg vg3 lv04 lv07
In AIX V4.2 and later, if you enter the reorgvg command with the volume group name
and no other arguments, the entire volume group is reorganized.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-93
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Physical Volumes
Volume group PV2
PV1
1 4 1 4
2 3 7 2 3
7 10 10
8 9 8 9
13 16 13 16
14 15 19 14 15
19 22 20 22
20 21 25 21
25 28 26 28
26 27 31 27
31 34 32 34
32 33 35 33
35 38 36 38
36 37 41 37
41 44 42 44
42 43 47 43
47 50 50
48 49 48 49
Physical Partitions
• Physical volume (PV)
– Hard disk
• Physical partition (PP)
– Smallest assignable unit of allocation on a physical disk
© Copyright IBM Corporation 2005
Notes:
Overview
A physical partition is a fixed size, contiguous set of bytes on a physical volume (PV).
Physical partitions (PP) must be the same size across an entire volume group.
However, there may be multiple volume groups on a single system, each having a
different PP size.
The limitations for each type of volume group (normal, big, and scalable) such as the
number of physical volumes and size of the physical partitions, was given in the last
unit, System Storage Overview.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-95
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Physical Volumes
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-97
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lspv
# lspv hdisk0
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-99
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lspv -l hdisk0
hdisk0:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
hd1 12 12 00..00..00..12..00 /home
hd3 3 3 00..03..00..00..00 /tmp
hd2 29 29 00..00..17..12..00 /usr
hd4 13 13 00..00..13..00..00 /
hd8 1 1 00..00..01..00..00 N/A
hd6 8 8 00..00..00..08..00 N/A
hd5 1 1 01..00..00..00..00 N/A
hd9var 2 2 00..00..02..00..00 /var
hd10opt 2 2 00..00..02..00..00 /opt
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-101
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# lspv -p hdisk0
hdisk0:
PP RANGE STATE REGION LV NAME TYPE MOUNT POINT
1-1 used outer edge hd5 boot N/A
2-31 used outer edge hd2 jfs /usr
32-32 free outer edge
33-40 used outer middle hd6 paging N/A
41-64 free outer middle
65-65 used center hd8 jfslog N/A
66-66 used center hd4 jfs /
67-73 used center hd2 jfs /usr
74-74 used center hd9var jfs /var
75-76 used center hd3 jfs /tmp
77-77 used center hd1 jfs2 /home
78-84 used center hd2 jfs /usr
85-92 used center paging00 paging N/A
93-95 used center hd10opt jfs /opt
96-159 used inner middle hd2 jfs /usr
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-103
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Uempty partitions per physical volume for this volume group changes to factor multiplied by
1016.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-105
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To discuss how to add a disk to the system, and move the contents of it from
one disk to the other.
Details — Note that whatever way you try to add a disk drive to the system, if you do not
have the correct software installed for that type of device, the system will prompt you to
install the software first from installation media before continuing. Remind the students that
this is true for any device.
If the PP/PV limitation is changed for the volume group, it cannot be imported into AIX
V4.3.0 or earlier versions. The migratepv command enables logical volumes to be moved
from one physical volume to the next in the same volume group. The example shows how
lv02 can be moved from hdisk0 to hdisk6 provided there is room to do so.
Additional Information — Prior to 4.3.3, migratepv could not be used to migrate striped
logical volumes. This was due to the old limitation that striped logical volumes could not be
mirrored. migratepv temporarily mirrors the logical volumes and then breaks the mirror
leaving the single copy in the new location.
Transition Statement — Let’s look at commands that help you to document your disk
storage setup.
Uempty
Documenting the Disk Storage Setup
• List of the disks on the system (PVID and volume group):
# lspv
Notes:
What to document
It’s important to have your storage information readily available in case you have a
problem with your system, or in the very worst case, a totally crashed system. The
commands in the visual help you to get this information.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-107
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Document storage setup.
Details — Encourage the students to have this information readily available in case they
have a problem with their system or in the very worst case, a totally crashed system.
You could also mention having a copy of /etc/filesystems, although this file has not yet
been discussed.
Transition Statement — Before we summarize, let's consider a few questions.
Uempty
Checkpoint
1. True or False? A logical volume can span more than
one physical volume.
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-109
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
1. True or False? A logical volume can span more than one
physical volume.
2. True or False? A logical volume can span more than one
volume group.
3. True or False? The contents of a physical volume can be
divided between two volume groups.
4. True or False? If mirroring logical volumes, it is not necessary
to perform a backup. False. You still need to back up to
external media.
5. True or False? SMIT can be used to easily increase or
decrease the size of a logical volume. False. SMIT can only be
used to increase a file system. Decreasing one requires backing
up the file system, removing it, re-creating it, and then restoring.
6. True or False? Striping is done at a logical partition level.
False. It is done at a stripe unit level.
Additional Information —
Transition Statement — Now, let’s do an exercise with LVM.
Uempty
Exercise 10: Working with LVM (Parts 3-5)
Notes:
Introduction
This lab has you set up a new volume group and a new logical volume. You use this
volume group and logical volumes in future exercises.
The exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-111
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review the exercise.
Details —
Additional Information —
Transition Statement — Let’s summarize what we’ve learned in this unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 10. Working with the Logical Volume Manager 10-113
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — Now, onto the next unit.
References
SC23-4908 System Management Concepts: Operating System
and Devices
SC23-4910 System Management Guide: Operating System and
Devices
GG24-4484 AIX Storage Management (Redbook)
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Identify the components of an AIX file system
• Add an enhanced journaled file system
• Change characteristics of a file system
• Add a RAM file system
• Add a UDF file system on a DVD-RAM
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Indirect
Data Blocks
Blocks
• Superblock
– File system size and identification
– Free list, fragment size, nbpi
• inodes
– File size, ownership, permissions, times
– Pointers to data blocks
• Blocks
– Data blocks contain data
– Indirect blocks contain pointers to data blocks
Notes:
Unit of allocation
An individual file within a file system will, by default, have units allocated to it in blocks
of 4096 bytes. (This may change if you have implemented fragmentation or large files -
both of which will be discussed later.)
Some AIX commands often report file sizes in units of 512 bytes to remain compatible
with other UNIX file systems. This is independent of the actual unit of allocation.
Uempty Superblock
The first addressable logical block on the file system is the superblock. The superblock
contains information such as the file system name, size, number of inodes, and
date/time of creation.
The superblock is critical to the file system and, if corrupted, prevents the file system
from mounting. For this reason a backup copy of the superblock is always written in
block 31.
Inodes
Immediately following the superblock are inodes which contain identifying information
for files, such as the file type, size, permissions, user/group/owner, and
create/modification and last access dates. They also contain pointers to the data blocks
for fragment addresses which hold the data.
Indirect blocks
For larger files the system creates sets of indirect blocks filled with data block
addresses to point to the data block or fragments which hold the data.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the structure of an AIX JFS file system.
Details — The file system contains a list of the unused data blocks and unused inodes on
the file system. These are called the free block list and free inode list. Each block on the
disk must either belong to a file or be pointed to by the free list.
Because the number of inodes is fixed by the NBPI value, there is a maximum possible
number of files that can be created within a JFS file system. It is rare that this number is
insufficient.
The rest of the file system consists of data blocks which can either be allocated to files or
unused, and indirect blocks which contain pointers to data blocks. (These extend the
addressability of the inode and are used for large files.)
When the file system is in use, the superblock and some of the inodes and the free list are
held in memory by the kernel to improve disk performance.
The AIX file systems are called journaled file systems because they use journaling
techniques to maintain the integrity of the file system's structural information (superblock,
inodes) which can be recovered in the event of a system crash.
The data blocks are not journaled, so you may lose data, but you shouldn't lose whole
directories which could happen in other versions of UNIX.
To find a piece of data the file system uses directories to point to inodes which in turn point
to the data blocks.
The file system is oblivious to the LVM and thinks that it has all its data contiguous on disk.
In actuality, the data is on disk in 4 MB increments (the physical partition size) and some of
the data may actually reside in memory at the time.
Additional Information —
Transition Statement — Let's take a closer look at the structure of an inode.
Uempty
Structure of an Inode
permissions
• Contents of an inode
no. of links
type of file
user ID
group ID
file size
addresses of blocks
time modified
inode for file1 time accessed
time changed
access control information
reserved other
$ ls -li /home/team01
2132 drwxr-xr-x 2 team01 staff 512 May 2 14:33 c
2136 drwxr-xr-x 2 team01 staff 512 May 2 14:33 doc
2141 -rw-r--r-- 1 team01 staff 28 May 16 10:11 Manuals
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Identify the major fields in the inode and the importance of the information kept
in it.
Details — All the base permissions, links, userid, groupid, and so forth, are kept in the
inode. The difference between the time changed and time modified is the following: time
changed means that only the inode changed. For example, maybe just the permissions on
the file were changed but not the actual file; whereas the time modified means that the file
actually changed.
The “reserved other” are pointers to the actual data blocks.
Although we have not yet discussed ACLs in this course, you might be asked where ACLs
are kept. ACLs are kept in an extended inode and are not kept in the actual inode itself. We
will have a limited discussion of extended attributes later in the unit.
Only use the following information as reference material for a Standard Journaled File
System only.
Direct addressing:
The first 8 fields are used to contain the absolute address of disk data blocks. Each disk
data block is 4 KB in size. (8 x 4KB = 32 KB). This scheme is used for files that are less
than 32 KB in size.
Single Indirect:
Field number 9 is used to represent where data is located on the disk. Instead of pointing to
a 4 KB block of “real” data, it contains the address of where the system can find 1024
addresses that point to 4 KB blocks of real data each (1024 x 4 KB = 4 MB). This scheme is
used for files in the range 32 KB to 4 MB in size.
Double Indirect:
The block pointed to by field 10 points to 512 entries on the disk. However this time the 512
entries do not point to data but instead point to 1024 addresses that point to data blocks
(512 x (1024 x 4KB) ) = 2 GB.
This scheme is used for files in the range from 4 MB to 2 GB only. Larger blocks of 128 KB
are implemented in files systems enabled for large files (to be discussed shortly).
Additional Information — istat can be used to list inode information, as well.
Transition Statement — File systems can be created so that less than the 4 KB logical
block is allocated for files smaller than 4 KB. This facility is called fragmentation.
Uempty
File System Fragmentation
No fragmentation 4096 bytes
File size = 2000 bytes 2000 bytes
4096 bytes
Fragmentation enabled 1024 1024
2000 bytes
File size = 2000 bytes 1024 1024
Fragment size = 1024 bytes
These free fragments can
be used by other files
Notes:
Use of fragmentation
Fragmentation provides a way to allocate pieces (or fragments) of a 4 KB logical block
to files and directories. Fragment support is helpful for small user files and directories.
JFS fragment support provides a view of the file system as a contiguous series of
fragments rather than logical disk blocks.
Fragment support applies to the last direct block of small user files and directories and
long symbolic links.
Fragment size
Fragment size is specified for a file system at creation time. The allowable fragment
size for JFS file systems are 512, 1024, 2048 and 4096 bytes. The default fragment
size is 4096 bytes.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Different file systems can have different fragment sizes, but only one fragment size can
be used within a single file system. Different fragment sizes can also coexist on a single
system so that administrators can select a fragment size which is most appropriate for
each file system.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Uempty
Variable Number of Inodes
With the default nbpi = 4096 an inode will be created
for every 4096 bytes of file system.
File system
4096 4096 4096
INODES
1
128 bytes
2
Notes:
Use of inodes
In all UNIX implementations, when a file system is created, inodes are written to disk.
For each file or directory, one such data structure is used to describe information
pertaining to the file or directory. JFS also reserves a number of inodes for files and
directories in each file system that is created.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Groupings of related 16 MB
16 MB
inodes and disk blocks
16 MB agsize
16 MB
64 MB
Groupings of related 64 MB
inodes and disk blocks 64 MB agsize
64 MB
Notes:
Uempty Relationship between allowable NBPI values and allocation group size
The allowable NBPI values are dependent on the allocation group size (agsize). For
example, for an agsize value of 8 MB, the only allowable NBPI values are 512, 1024,
2048, 4096, 8192 and 16384 bytes. If you were to double the agsize from 8 MB to 16
MB, the range of NBPI values also doubles to 1024, 2048, 4096, 8192, 16384 and
32768 bytes.
Refer to the table below for more details.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the concept of allocation group size.
Details — Some like to think of an allocation group as a 'chunk' of contiguous disk space.
With a very large allocation group size, you have the potential to improve performance,
since data should be located in contiguous space on disk, and thus there should be less
movement of disk heads.
Note that there is a relationship between the agsize and the NBPI ranges in JFS.
Additional Information — JFS2 also uses allocation groups. Since inodes are allocated
dynamically in JFS2, there is no NBPI parameter.
Transition Statement — Let us look at the optional file system characteristic of doing
automatic compression of the files in the file system.
Uempty
Compressed File Systems
compression = LZ (yes)
fragment size = 1024
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Fragmentation concerns
The use of fragments and data compression does, however, increase the potential for
fragmentation of the disk's free space. Fragments allocated to a logical block must be
contiguous on the disk. A file system experiencing free space fragmentation may have
difficulty locating enough contiguous fragments for a logical block's allocation, even
though the total number of free fragments may exceed the logical block's requirements.
Additional considerations
In addition to increased disk I/O activity and free space fragmentation problems, file
systems using data compression have the following performance considerations:
- Degradation in file system usability arising as a direct result of the data
compression/decompression activity. If the time to compress and decompress data
is quite lengthy, it may not always be possible to use a compressed file system,
particularly in a busy commercial environment where data needs to be available
immediately.
- All logical blocks in a compressed file system, when modified for the first time, will
be allocated 4096 bytes of disk space, and this space is subsequently reallocated
when the logical block is written to disk. Performance costs are, therefore,
associated with this allocation, which does not occur in non-compressed file
systems.
- In order to perform data compression, approximately 50 CPU cycles per byte are
required and about 10 CPU cycles per byte are required for decompression. Data
compression, therefore, places a load on the processor by increasing the number of
processor cycles.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
1025
1026
1 Block 1027
1 4 KB .. 32 Blocks
2 . 128 KB
3 1055
4 1056
..
.
1023
1024
File
1057
132 MB 128 KB
1058
1059
.. 32 Blocks
. 128 KB
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain what large file enabled file systems are and how they differ from the
standard file systems.
Details — AIX V4.2 introduced the concept of large file enabled file systems to
accommodate file sizes greater than 2 GB.
The visual shows an example of the potential for disk space savings with large file enabled
file systems. It is important to note that if this 132 MB file was inside a regular standard file
system defined with 4 KB blocks it would have consumed a total of 33,792 blocks because
the system would have systematically allocated as many 4K blocks as it required. In the
example shown, the total block consumption is only 2048 blocks. This is why it is stated
that only 2 single indirect blocks are required because this works out to only 2 blocks of
1024 each.
Even with a file size of 132 MB, there is disk space efficiency if placed in a large file
enabled file system since fewer pointers are needed in the inode table. However, the 'catch'
is that any file in these file systems will require 32 contiguous 4 KB blocks for sizes beyond
4 MB. The file system may have thousands of free blocks, but if 32 of them are not
contiguous, the allocation will fail. The defragfs command reorganizes disk blocks to
provide larger contiguous free block areas.
Additional Information — Do another example on the board. Suggestion: a 64 MB file
would be (1024 * 4 KB blocks) + (480 * 128 KB blocks) = 64 MB
Transition Statement — Let's do an exercise about inodes and NBPI.
Uempty
Exercise 11:
Working with File Systems (Part 1)
• Part 1:
Inodes and NBPI
Introduction
This exercise can be found in your Student Exercise Guide.
Only do Part 1 - Inodes and NBPI
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details — Be sure to tell the students to ONLY do Part 1. The other parts (2-6) will be done
at the end of this unit.
Additional Information —
Transition Statement — Let’s now look at journal logs.
Uempty
Journal Log
1
Write data
sync / fsync
1) Inode changes to log
2) COMMIT to log
3 3) Update inode 2
4) Sync log
Inodes 4
Data
block JFSLOG
Notes:
The jfslog
The jfslog for each volume group (such as the rootvg /dev/hd8) is a circular log. A
jfslog is created the size of one physical partition, one per each volume group. The
jfslog ensures file system integrity by writing all metadata information to the jfslog
immediately. It does this in the form of transactions, as illustrated in the diagram. File
system metadata consists of changes to the file system structure itself, such as
changes to the inodes and the free list.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Inline logs
An inline log is a new feature specific to JFS2 file systems that allows you to log directly
to the file system. The default inline log size is 0.4% of the logical volume size
(in AIX 5L V5.1).
The following table lists the default inline log size in AIX 5L V5.2 and later.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Compression Yes No
JFS2 uses extent based allocation for high performance and large file size.
.
Notes:
Introduction to JFS2
Enhanced Journaled File System (JFS2) is a new file system type that was introduced
in AIX 5L V5.1. It is based on JFS.
Reference information
The following reference information may be useful when you are reviewing the table on
the visual:
1 Petabyte (PB) = 1024 Terabytes (TB) = (250 ) bytes
1 Terabyte (TB) = 1024 Gigabytes (GB) = (240 ) bytes
1 Gigabyte (GB) = 1024 Megabytes (MB) = (230 ) bytes
1 Megabyte (MB) = 1024 Kilobytes (KB) = (220 ) bytes
1 Kilobyte (KB) = 1024 Bytes = (210 ) bytes
Dynamic inodes
The traditional approach of reserving a fixed amount of space for inodes at file system
creation time required accurate estimates of the number of files that would reside in the
file system. If the estimate was high, disk space was wasted. If the estimate was low, no
files could be added until the file system was expanded. JFS2 dynamically allocates
space for inodes as needed, and frees the space when it is no longer required.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The administration is similar to administration of the BSD Disk Quota System (refer to
http://www.openbsd.org for details) except that AIX added a new method for mapping
the users to the quotas. The quotas are assigned to a Limits class and then the users
are assigned to the class. This greatly simplifies the quota administration. AIX 5L V5.3
has added one new command to administer Limits classes - j2edlimit.
Migration
JFS file systems can co-exist on the same system with JFS2 file systems. However, to
fully utilize the JFS2 features, the following steps will be necessary:
- Backup JFS file system data
- Create new JFS2 file systems
- Restore JFS file system data to new JFS2 file systems
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
$ getea HenryVIII
EAName: Author
EAValue: Shakespeare
Notes:
Uempty EAv1 had restrictions of only eight attributes, 4 KB per attribute, 16-bit encoded names
and no support for user defined attributes. EAv2 effectively eliminates these restrictions.
The primary use for EAv2, currently, is the support for the NFS V4 ACL capability. The
discussion of NFS V4 ACLs is outside the scope of this class.
Managing attributes
AIX 5L V5.3 provides line commands to manage the user defined attributes. To set an
attribute value, you would use the setea command. To view a user attribute, you would
use the getea command.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the concept of extended attributes and the new EAv2 support in
AIX 5L V5.3.
Details — Focus on the fact the AIX 5L V5.3 now allows a choice of the format to be used
when defining a JFS2 file system - we will see this, as well as the compatibility issues with
previous versions of AIX 5L, later.
While we cannot delve into NFS in this course, it should be pointed out that, for most
systems, the only reason to use the newer EAv2 is to support the use of ACLs under NFS
V4.
Additional Information —
Transition Statement — Having discussed the major concepts behind both JFS and JFS2
file systems, let us look at how you can manage these file systems through SMIT.
Uempty
File Systems
# smit fs
File Systems
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show what activities a system administrator can perform with file systems.
Details — Use this as a road map for the next several pages. On some pages the SMIT
screens will be shown. On others, the command. Where the command is simple and
quickly executed on a command line, the command will be shown. For the more complex
commands, the SMIT screens will be shown.
Additional Information —
Transition Statement — Let's see how to list file system information.
Uempty
Listing File Systems
# lsfs
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The data may be presented in line and colon (-c) or stanza (-l) format. It is possible to
list only the file systems of a particular virtual file system type (-v), or within a particular
mount group (-u). The -q option queries the superblock for the fragment size
information, compression algorithm, and the number of bytes per inode.
SMIT fastpath
The SMIT fastpath to get to the screen which accomplishes the same task as the lsfs
command is smit fs. This takes you to the File Systems SMIT menu. Select the List
All File Systems menu item. This selection does not have a dialog panel; it just runs
the lsfs command.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# mount
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to list all the mounted file systems.
Details — The output from this command is similar to that from the lsfs command, but
only the mounted file systems are listed.
The mount command is also used to mount a file system to the tree, as will be seen later.
Additional Information — This example also shows an NFS-mounted file system. We
have mounted budget from the remote server sys4. This file system is mounted on our
local client's mount point of /reports.
Transition Statement — You've now seen how to list file system information. Let's see
how to add file systems in the AIX environment.
Uempty
Add/Change/Show/Delete File Systems
# smit manfs
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how to locate and work with the file system management menus for
different types of file systems.
Details —
Additional Information —
Transition Statement — Let’s first look at the traditional JFS menu.
Uempty
Working with
Journaled File Systems in SMIT
Journaled File Systems
Move cursor to desired item and press Enter.
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the students how to use the SMIT menus for creating file systems.
Details — We will first discuss how to add a file system. The options on the first menu
shown for showing the characteristics of, and removing a file system will be discussed later
in this unit. The option of defragmenting the file system will be discussed in the next unit.
Be sure to point out that there are two options available if adding a file system. The option
to Add a Journaled File System will create both the logical volume and file system for
you. The option to Add a Journaled File System on a Previously Defined Logical
Volume assumes the logical volume has already been created. Ask the students 'Why
would you choose this second option?'. The answer is that you have more control over the
logical volume, its placement on disk, and so forth.
The second SMIT menu is shown for JFS in AIX V4.2 and later. This same menu will be
displayed for either adding a JFS, or adding a JFS to a previously defined logical volume.
Mention that Add a Compressed File System creates a JFS file system in which all data
is compressed automatically using LZ compression before being written to disk and all data
is uncompressed automatically when read from disk. The option to Add a Large File
Enabled Journaled File System creates a JFS file system in which the maximum file size
can be 64 GB (up from 2 GB for a standard journaled file system).
Transition Statement — Let's assume we are going to add a standard JFS file system to a
previously defined logical volume.
Uempty
Add a Standard Journaled File System
on a Previously Defined Logical Volume
Add a Standard Journaled File System
[Entry Fields]
* LOGICAL VOLUME name +
* MOUNT POINT [ ]
Mount AUTOMATICALLY at system restart? no +
PERMISSIONS read/write +
Mount OPTIONS [ ] +
Start Disk Accounting ? no +
Fragment Size (bytes) 4096 +
Number of bytes per inode 4096 +
Allocation Group Size (MBytes) 8 +
Logical Volume for Log [ ] +
Figure 11-18. Add a Standard Journaled File System on a Previously Defined Logical Volume AU1411.0
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
Volume group name rootvg
SIZE of file system
Unit Size Megabytes +
* Number of units [ ] #
* MOUNT POINT [ ]
Mount AUTOMATICALLY at system restart? no +
PERMISSIONS read/write +
Mount OPTIONS [ ] +
Start Disk Accounting ? no +
Fragment Size (bytes) 4096 +
Number of bytes per inode 4096 +
Allocation Group Size (MBytes) 8 +
Logical Volume for Log [ ] +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
algorithm Lempel-Ziv. If you do not want data compression, set this attribute value to
no, which is the default value.
- The allocation group size (-a ag= 8 | 16 | 32 | 64) is a grouping of inodes and
disk blocks within the file system. The default agsize is 8 MB. This attribute only
applies to AIX V4.2 and later.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Figure 11-20. Working with Enhanced Journaled File Systems (JFS2) in SMIT AU1411.0
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
* LOGICAL VOLUME name +
* MOUNT POINT [ ]
Mount AUTOMATICALLY at system restart? no +
PERMISSIONS read/write +
Mount OPTIONS [ ] +
Block Size (bytes) 4096 +
Logical Volume for Log [ ] +
Inline Log size (MBytes) [ ] #
Extended Attribute Format Version 1 +
Enable Quota Management no +
Figure 11-21. Add an Enhanced Journaled File System (JFS2) on a Previously Defined Logical Volume AU1411.0
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to add a JFS2 file system on an existing logical volume.
Details — This visual shows the SMIT menu for creating an Enhanced journaled file
system on a previously defined logical volume. Note that there is no option for specifying
size. The file system will assume the same size as the logical volume.
On this and the next visual, only briefly remind the students of the difference between
letting the logical volume be allocated implicitly vs first creating the logical volume and then
defining the JFS2 upon it. That should have been sufficiently covered during the earlier JFS
discussion.
Instead focus on “block sizes” being effectively the same as “fragment size” and on the
ability to define either an external log or an inline log and size. The AIX 5L V5.3 panel will
show inline as one of the choices on the F4 list for Logical Volume for Log.
Also relate the last two items to the previous discussion about disk quota system support
and EAv2.
You may wish to leave this visual up for comparison with the next visual.
Additional Information —
Transition Statement — Let's see how you could create a JFS2 file system and a logical
volume at the same time.
Uempty
Add an Enhanced
Journaled File System (JFS2)
Add an Enhanced Journaled File System
[Entry Fields]
Volume group name rootvg
SIZE of file system
Unit Size Megabytes +
* Number of units [ ] #
* MOUNT POINT [ ]
Mount AUTOMATICALLY at system restart? no +
PERMISSIONS read/write +
Mount OPTIONS [ ] +
Block size (bytes) 4096 +
Logical Volume for Log [ ] +
Inline Log size (MBytes) [ ] #
Extended Attribute Format Version 1 +
Enable Quota Management no +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how a JFS2 file system can be created.
Details — This visual shows how to create an Enhanced journaled file system. The logical
volume will automatically be created.
You may wish to compare this visual with the previous one. Note that most of the fields that
need to be filled out are the same. However, if adding a file system without a previously
defined logical volume, it is necessary to indicate the size of the file system - this is the
primary difference between the two screens.
Details —
Transition Statement — Once a file system has been created, it needs to be mounted in
order to get access to it. Let's see how this can be done.
Uempty
Mount a File System
[Entry Fields]
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Uempty mounted. (A normal user belonging to the system group can also mount file systems at
any time, provided the user has write permission to the mount point and read
permission on the root directory of the file system to be mounted.)
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the mounting of file systems and what conditions must be satisfied in
order to mount or unmount them.
Details — All of the default mount options for a journaled file system may be overridden if
the appropriate options are used in the mount command.
Mounted file systems may be unmounted using the umount or unmount commands if they
are not in use at the time. Some commands such as the backup command may want to
unmount a file system in order to work. If the file system is in use and cannot be unmounted
the command may fail, depending on the commands requirements.
If you enter unmount -a, then all the mounted file systems will be unmounted. The
unmount all command will unmount all the mounted file systems, except those with
stanzas in the /etc/filesystem file with the mount=automatic attribute.
A device is in use if any file is open for any reason or if a user's current directory is on that
device. The fuser command lists the process numbers of local processes that are using
the files. The -u flag specifies that the login name for the processes should also be listed.
Additional Information —
Transition Statement — You have a file system, and it is mounted. At some later point,
you may wish to make changes to it. Let's see what changes can be made.
Uempty
Change/Show
Characteristics of a Journaled File System
Change/Show Characteristics of a Journaled File System
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Changing permissions
The permissions associated with the file system may be changed (-p ro|rw), and the
change will be effective the next time the file system is mounted.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Change/Show Characteristics
of an Enhanced Journaled File System
Change / Show Characteristics of an Enhanced Journaled File System
[Entry Fields]
File system name /home
NEW mount point [/home]
SIZE of file system
Unit Size 512bytes +
* Number of units [32768] #
Mount GROUP [ ]
Mount AUTOMATICALLY at system restart ? yes +
PERMISSIONS read/write +
MOUNT OPTIONS [ ] +
Start Disk Accounting? no +
Block size (bytes) 4096
Inline Log? no
Inline Log size (MBytes) [ ]
Extended Attribute Format Version 1 +
Enable Quota Management no +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
After:
LP1
Notes:
Uempty Restrictions
There must be enough free space in the remaining physical partitions of the file system
to stored the file data and metadata structures being moved from the freed physical
partitions.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the AIX 5L V5.3 capability to dynamically shrink a JFS2 file system.
Details — See student notes.
Additional Information — There is no command to show exactly how much a file system
can be shrunk, since the df command does not show the size of the metadata. In addition,
the free space reported by the df command is not necessarily the space that can be
truncated by a shrink request due to file system fragmentation. A fragmented file system
may not be shrunk if it does not have enough free space for an object to be moved out of
the region to be truncated, and a shrink does not perform file system defragmentation. In
this case, the chfs command should fail with the returned code 28. However, there is a
rule of thumb. A way to use it is to enter the df command to get information regarding the
file system and look at the size of the Free field. That might be the maximum size that you
can remove from the file system. Use the chfs -a command to shrink the file system and
then check the final size with the df command. Remember that a file system can be
extended or shrunk by a multiple of the physical partition size.
It must be noted that you can not shrink a file system if the requested size is less than a
physical partition size. If you attempt to reduce the size with less than a physical partition
size, the request will be ignored.
The size of the inline log can also be manually increase or decreased in AIX 5L V5.3 with
the logsize attribute of the chfs command.
Transition Statement — Now that we have looked at creating and modifying our file
systems, let us look at how we remove then.
Uempty
Remove a Journaled File System
[Entry Fields]
FILE SYSTEM name +
Remove Mount Point no +
Notes:
Restrictions
In order to remove a file system, it must be unmounted from the overall file tree, and this
cannot be done if the file system is in use, that is, some user or process is using the file
system or has it as a current directory.
Effects of using rmfs command
The rmfs command removes any information for the file system from the ODM and
/etc/filesystems. When the file system is removed, the logical volume on which it
resides is also removed.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Syntax
The syntax of the rmfs command is:
rmfs [-r] [-i] FileSystem
-r Removes the mountpoint of the file system
-i Displays warning and prompts the user before removing the file system
Example:
# rmfs -r /home/george/myfs
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# mkramdisk 4M
/dev/rramdisk0
# mkdir /ramdisk
Notes:
Limitations
Use ramdisk only for data that can be lost. After each reboot, the ramdisk file system is
destroyed and must be rebuilt.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Using a UDF
Once you have created a UDF on a DVD-RAM, you can just treat it like a normal hard
disk. It enables you to read, write, delete, copy, move, mount, unmount and edit a file
within the DVD directory.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss adding a UDF file system on a DVD-RAM.
Details —
Additional Information — Starting with AIX 5L V5.2, DVD-RAM with UDF should be used
for system backup using mksysb. That is much easier then writing to a CD-RW in ISO9660
format.
Transition Statement — Finally, let’s recall a few important points regarding system
storage.
Uempty
System Storage Review
Logical Volume Structure
hd2
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Simple directories
The directories on the left of the bottom portion of the visual are strictly directories that
contain files and are part of the /(root) file system. There is no separate logical volume
associated with these directories.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. Will the size of the file system change when the size of
the logical volume it is on is increased? _________
Notes:
Checkpoint Solutions
1. Will the size of the file system change when the size of
the logical volume it is on is increased? No
Additional Information —
Transition Statement — Let’s move on to the exercise for this unit.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Exercise 11:
Working with File Systems (Parts 2-6)
Notes:
Introduction
This lab has you build on the logical volume you created in the last exercise. It also
gives you an opportunity to create a file system and learn to increase the size of both
the logical volume and file system.
The exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 11. Working with File Systems 11-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4910 System Management Guide: Operating System and
Devices
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Monitor file system growth and control growing files
• Manage file system disk space usage
• Implement basic file system integrity checks
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Space Management
• File systems expand upon notice, NOT automatically
• To keep from running into problems:
– Monitor file system growth
– Determine causes
– Control growing files
– Manage file system space usage
– Control user disk usage
– Defragment file system
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce key concepts regarding management of file system usage.
Details — Make sure students understand the importance of managing file system usage.
If a file system fills up, typically there is no warning to the end user or program. Sometimes
you will end up with unpredictable results, such as the case when data blocks are gone but
directory space is not gone. You may have created a file, and the file exists, but it has zero
length, because there are no more data blocks available. This is why it is so important to
monitor the status of the file systems.
Additional Information —
Transition Statement — Now that we have listed the steps necessary to monitor our file
systems, let's take a closer look at each step.
Uempty
Listing Free Disk Space
• The df command displays information about total
space and available space on a file system
# df
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
• /var/spool/*/*
• $HOME/smit.log
• $HOME/smit.script
• $HOME/websm.log
• $HOME/websm.script
Notes:
Uempty - Example 1:
# cat /dev/null > /var/adm/wtmp
- Example 2:
# > /etc/security/failedlogin
The file /var/adm/sulog can be edited directly.
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Identify common types of files that grow uncontrollably. The system
administrator may want to control these on an ongoing basis.
Details — The files listed tend to grow quite large and need to be cleaned out periodically.
For example, when you do a mksysb backup via SMIT, your smit.log file grows very large
and needs to be reduced or totally erased after the operation.
The wtmp file contains information about users logging in and logging out of the system.
The condition of ttys respawning too rapidly will create failed login entries as well. If
accounting is implemented, this file is managed through accounting. If accounting is not
implemented, then you at least need to reduce this file manually. The who command is used
against this particular file to take a look at the information it contains.
The /etc/security/failedlogin file can also become very large due to the condition of ttys
respawning too rapidly. This creates failed login entries as well.
When there is a bad serial connection to a tty device (terminal or modem) the getty
process which issues the login prompt will die. Since the /etc/inittab specifies that this is a
respawn process, the init process immediately respawns the getty for that tty. Each time
this happens, failed login entries are generated. If the serial connection repeatedly and
rapidly fails, then the respawn happens rapidly, and the error log will grow rapidly.
$HOME/websm.log is used to log the Web-based System Manager. This file can become
quite large since it tracks graphics-based activity.
Additional Information —
Transition Statement — There is a tool to help monitor these and other files that need
periodic clean-up. Let's take a look at skulker.
Uempty
The skulker Command
• The skulker command cleans up file systems by removing
unwanted or obsolete files
• Candidate files include:
– Files older than a selected age
– Files in the /tmp directory
– a.out files
– core files
– ed.hup files
•skulker is normally invoked daily by the cron command
as part of the crontab file of the root user
• Modify the skulker shell script to suit local needs for the
removal of files
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# du /home | sort -r -n
624 /home
392 /home/fred
98 /home/tom
54 /home/mary
52 /home/liz
23 /home/suzy
2 /home/guest
1 /home/steve
Notes:
The -x flag
The -x flag/option is also very useful. When you use du -ax, the report only shows
information from the specified file system. This is the best way to determine what file is
filling a particular file system.
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to determine the directory, file, and/or user that is causing the disk
expansion problem within a particular file system.
Details — Note that the disk usage command is being used against a particular file system
and piped into the sort command. The sort command sorts on the first field, which is a
numeric field as specified by the -n option. The sort output will also be reversed because
of the -r option. The numbers that you see are in terms of 512-byte blocks. Use the -k
option to view sizes in 1 KB blocks.
The point is to identify who the user of file system is and, before expanding the file system,
ask the person if they really need that space.
Additional Information —
Transition Statement — Creating file systems that will allocate smaller logical blocks, a
process referred to disk fragmentation, is one way of saving disk space in an environment
where large numbers of small files are used. Let's see what needs to be considered when
deciding whether or not to use disk fragmentation.
Uempty
Fragmentation Considerations
4096 bytes
4096 bytes
With fragmentation
2000 bytes
Considerations to be made:
Disk space allocation
Disk space utilization
I/O activity
Free space fragmentation
Fragment allocation map
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Options:
Notes:
Uempty Note: Sometimes the estimates for these items provided when running defragfs with
the -q or -r option indicate results different from what is actually done when defragfs
is run without any options.
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to defragment a file system.
Details — Running the command with options will give you statistics as to the state of the
file system before the defragfs command runs. Then, when the command is run to do the
defragmenting, the same statistics are produced again, so a comparison can be made.
Additional Information — This command was introduced with AIX V4.
Transition Statement — Another operation that you can carry out to enhance system
availability is to verify the file systems. Let's see how this is done.
Uempty
Verify a File System
• Command syntax:
Notes:
The -p option
The -p (preen) option is used to check a file system and make only minor changes,
without bothering the user. When fsck is run under SMIT, this option is used.
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint
1. What command can you use to determine if a file
system is full? __________
Notes:
Checkpoint Solutions
1. What command can you use to determine if a file
system is full? df
Additional Information — For question #2, use of the find command with the -size
option would also be a perfectly acceptable answer.
Transition Statement — Let’s move on to the exercise for this unit.
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The lab allows you to get some experience with the file system management tools. It
also allows you to build and test file systems with different characteristics.
This exercise can be found in your Student Exercises Guide
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 12. Managing File Systems 12-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4908 AIX 5L Version 5.3 System Management Concepts:
Operating System and Devices
SC23-4910 AIX 5L Version 5.3 System Management Guide:
Operating System and Devices
SC23-4905 AIX 5L version 5.3 Performance Management Guide
SG24-5765-02 AIX 5L Differences Guide Version 5.2 Edition
SG24-7463-00 AIX 5L Differences Guide Version 5.3 Edition
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Define why paging space is required in AIX
• List and monitor the paging space utilization of the system
• Perform corrective actions to rectify too little or too much
paging space scenarios
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
RAM = 256 MB
RAM Usage
Operating System Database TCP/IP 8 MB FREE
Current applications
Total = 248 MB
RAM Usage
New application
Operating System Database TCP/IP Application
needs RAM > 8 MB
4 KB 4 KB
Paging Space
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Define what paging space is.
Details — Using the diagram in the visual, give a brief overview of how paging works.
While discussing the diagram, be sure to define the terms. Be careful not to go too deeply
into this topic. This is only meant to be a level set of terms for these students who have
never heard the terms before.
Make sure that you emphasize that in AIX, paging space is NOT intended to be used as an
extension to real memory.
Some UNIX operating systems use swap space rather than paging space, and some
people use the terms swap and page interchangeably. Actually, paging in AIX is demand
paging in 4 KB chunks. Swapping moves the entire process (which is most likely greater
than 4 KB) from RAM to disk.
Additional Information — In the AIX environment, paging space is not used for
information that has a “permanent home” in file system space.
Transition Statement — Now that you have an idea of what paging space is, let’s talk
about why we need it.
Uempty
Paging Space
• Is a secondary storage area for over-committed memory
• Holds inactive 4 KB pages on disk
• Is not a substitute for real memory
Paging Space
Physical Memory
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
#
ksh: cannot fork no swap space
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss points related to sizing of paging space.
Details — The AIX VMM manages the use of system memory. It allows applications to
request more memory than there is physically installed in the system and will move pages
of memory to disk to make room for applications. If paging space becomes full, the system
will be unable to start any new processes until some of the running processes terminate or
release allocated memory. This situation should be avoided.
Systems with large amounts of memory typically do not need to have an amount of paging
space equal to or greater than the amount of RAM. Paging space can be smaller than RAM
because, by default, paging space pages are not allocated until the data in the page frame
needs to be paged-out. But, this is tricky because if paging activity begins to occur, the
machine could quickly run out of paging space. Before you size the paging area smaller
than RAM, you should have monitored the machines during peak times to know how much
paging space is generally needed.
Paging space can be added or enlarged easily. Prior to AIX 5L V5.2, reducing the size of a
paging space used to be difficult (involving a reboot). Now, reducing the size of a paging
space has become fairly simple. The paging space is a logical volume and has all of the
same characteristic of a normal logical volume.
Additional Information — The system monitors the number of free paging space blocks
and detects when a paging space shortage exists. When the number of free paging space
blocks falls below a threshold known as the paging space warning level, the system
informs all processes (except the kernel ones) of this condition by sending a SIGDANGER
signal. If the shortage continues and falls below a second threshold known as the paging
space kill level, the system sends a SIGKILL signal to selected processes. (By default,
processed that have a signal handler for the SIGDANGER signal will not be sent a SIGKILL
in this situation. However, in AIX 5L V5.3, this default behavior can be altered by changing
the value of the low_ps_handling setting using vmo.) Also, AIX 5L V5.3 introduced two
paging space garbage collection (PGSC) methods to enhance paging space management.
Refer to the AIX 5L Differences Guide Version 5.3 Edition for more information about
PGSC.
The following information regarding paging space allocation policies is for instructor
background only. Don't try to cover this information in this class.
The following paging space allocation policies are available in AIX:
- Early Page Space Allocation (EPSA)
- Late Page Space Allocation (LPSA)
- Deferred Page Space Allocation (DPSA)
The paging space allocation policy determines when paging space will be allocated for
a process. Individual processes may use the system paging space allocation policy
(which can be set to DPSA or LPSA), or override the system paging space allocation
policy and use EPSA.
Uempty When the early page space allocation (EPSA) policy is used, paging space is allocated
as soon as a memory request is made, even if the memory is not accessed. Thus, if a
process that has specified EPSA uses the malloc() subroutine to allocate memory,
paging-space disk blocks will be allocated and reserved for that process at that point.
So, if the process needs to page out, there will always be paging space slots available
for it.
When the late page space allocation (LPSA) policy is used, the disk block for a paging
space page is only allocated when a page of a segment is used for the first time.
The deferred page space allocation (DPSA) policy is the default policy in AIX. With
deferred page space allocation, the disk block allocation of paging space is delayed
until it is necessary to page out the page. The goal of this policy is to avoid wasted
paging space allocation.
The system paging space allocation policy can be set to either LPSA or DPSA. The
system paging space allocation policy is used for any process that does not override
this system-wide setting by use of the PSALLOC environment variable. For AIX 5L, the
default system paging space allocation policy is DPSA.
The system paging space allocation policy can be displayed or set using the vmo
command.
The environment variable PSALLOC can be used by individual processes to override the
system paging space policy. If the value of PSALLOC is set to early, EPSA will be used
for processes subsequently started in that environment. If the value of PSALLOC is set to
null (or any value other than early), the system paging space policy is used.
Transition Statement — As we have seen in the storage unit, paging space is contained
within a logical volume, and a logical volume can be placed at specific parts of the disk.
Let's see what considerations have to be made for paging space placement.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Placement and size of your paging space will impact its performance. The following
material contains tips regarding placement and size of paging areas.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Consider performance impact of the placement of paging space.
Details — All processes starting during the boot processes are allocated to hd6. After that,
the round robin technique is used to assign paging space.
Cover the points on the visual.
The rc.boot script that controls the boot sequence is where the reference to hd6 is located.
If hd6 ever needs to be reduced in size, the rc.boot script will need to be edited to look for
a different default boot area. This procedure is well documented in the Web-based
documentation.
Never set up two paging areas on the same disk. The two areas will be used equally in the
round-robin scheme and the disk head will be moving back and forth to use each space
equally. This added disk head activity will surely decrease performance.
Additional Information — It used to be true that allocating paging space to the center of
the disk was good practice. However, with many of the newer disks, this is no longer true.
Many of the new disks will perform better on the edges. You would need to check the specs
on the particular disk drive to determine the location that has the best performance.
Transition Statement — Let's see how we can monitor the paging activity.
Uempty
Checking Paging Space
• Check paging activity:
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
hd6 hdisk0 rootvg 64MB 43 yes yes lv
paging00 hdisk2 rootvg 64MB 20 yes yes lv
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
Volume group name rootvg
SIZE of paging space (in logical partitions) [4] #
PHYSICAL VOLUME name hdisk2 +
Start using this paging space NOW? yes +
Use this paging space each time the system is yes +
RESTARTED?
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how to add paging space
Details — Ideally, there should be several paging spaces of roughly equal size, each on
different physical volumes. If you decide to create additional paging spaces, create them
on physical volumes that have the least activity.
Additional Information — When using the method shown on the visual to add paging
space, the inter-physical volume policy will be set to “middle.” The system will then try to
place the paging area in the middle as long as there is room.
To have the policy set to someplace other than “middle,” instead of using this screen, you
would set up the paging area like a standard logical volume using smit lvm. When you use
this method, set the logical volume type to paging and set the policy to the desired
location. It is probably a good idea to name it pagingxx to keep it consistent with the
system's naming convention.
If you use this method, the paging area will not automatically be activated. You will need to
run swapon to activate the paging area. You will also need to ensure that /etc/swapspaces
is updated. You may encounter problems by directly editing /etc/swapspaces. The better
way to do it is to go in to smit pgsp and set the characteristic within SMIT. You can also
use chps -ay pagingxx.
Transition Statement — Once paging space is installed, there are some characteristics
that can be changed. Let's look at those.
Uempty
Change Paging Space
# smit chps
[Entry Fields]
Paging space name paging00
Volume group name rootvg
Physical volume name hdisk2
NUMBER of additional logical partitions [] #
Or NUMBER of logical partitions to remove [] #
Use this paging space each time the system is yes +
RESTARTED?
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The process chps goes through to decrease an active paging space is as follows:
Step Action
Create a new, temporary space from the same volume group as the
1
one being reduced
2 Deactivate the original paging space
3 Reduce the original paging space
4 Reactivate the original paging space
5 Deactivate the temporary space
The primary paging space (usually hd6) cannot be decreased below 32 MB.
When you reduce the primary paging space, a temporary boot image and a temporary
/sbin/rc.boot pointing to this temporary primary paging space are created to make sure
the system is always in a state where it can be safely rebooted.
These command enhancements are also available through the Web-based System
Manager, starting in AIX 5L V5.2.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Make inactive
# swapoff /dev/paging00
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to delete paging space.
Details — When a paging space is removed, the corresponding entry in /etc/swapspaces
is also removed.
The paging space /dev/hd6 cannot be made inactive and therefore cannot be removed. To
remove /dev/hd6, it is necessary to update rc.boot, which is not recommended. In
general, it is not recommended that any of the default paging spaces (hd6, hd61, and so
forth) be removed except by an experienced system administrator. Removing default
paging spaces incorrectly can prevent the system from restarting.
Do not expand hd6, create other paging spaces instead.
Additional Information —
Transition Statement — Let's outline once again what should be done if there is too little
or too much paging space defined on the system.
Uempty
Problems with Paging Space
• Paging space too small:
Dynamically increase the size by allocating more partitions
chps -s LogicalPartitions PagingSpace
Example:
# chps -s 1 paging00
Example:
# chps -d 1 paging00
Notes:
Overview
All ideas on this visual have already been considered. The visual simply pulls together
all the ideas discussed so far.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List corrective suggestions for dealing with too much or too little paging space.
Details —
Additional Information —
Transition Statement — As with all the other logical volumes, the paging space setup
should be documented. Let's see what steps can be taken.
Uempty
Documenting Paging Space Setup
Notes:
Running lsps
Run lsps to monitor paging space activity. Keep good documentation so that you know
what is normal for that system.
A copy of /etc/swapspaces
Keep a copy of /etc/swapspaces so that you know what paging spaces are defined to
started at boot.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to document the paging space setup.
Details —
Additional Information —
Transition Statement — Let’s move on to some checkpoint questions.
Uempty
Checkpoint
1. What conclusions regarding potential paging space problems can
you reach based on the following listing?
Page Physical Volume Size %Used Active Auto Type
Space Volume Group
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
2. True or False? The size of paging00 (in the above example) can
be dynamically decreased.
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Present the checkpoint questions.
Details —
Checkpoint Solutions
1. What conclusions regarding potential paging space problems can
you reach based on the following listing?
Page Physical Volume Size %Used Active Auto Type
Space Volume Group
Additional Information —
Transition Statement — Let’s move on to the exercise for this unit.
Uempty
Exercise 13: Paging Space
Notes:
Introduction
This lab allows you to add, decrease, monitor, and remove paging space.
The exercise can be found in your Student Exercises Guide.
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise for this unit.
Details — Depending on the class, it might be a good idea to remind the students where
the instructions for the exercise are located.
Additional Information —
Transition Statement — Let’s summarize the key points we’ve covered in this unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 13. Paging Space 13-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the key points covered in this unit.
Details —
Additional Information —
Transition Statement — We’ve reached the end of this unit.
References
Online AIX System Management Concepts: Operating
System and Devices
Online AIX System Management Guide: Operating System
and Devices
SG24-5765 AIX 5L Differences Guide Version 5.2 Edition
SG24-5766 AIX 5L Differences Guide Version 5.3 Edition
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Identify issues which have to be considered when deciding
which backup policies to implement:
– Media to be used
– Frequency of the backup
– Type of backup
• List the different backup methods supported through SMIT
and on the command line
• Create a customized installable system image backup
• Execute other useful commands to manipulate the backed
up data on the media
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Why Backup?
• Data is very important:
– Expensive to recreate
– Can it be recreated?
• Disaster recovery:
– Hardware failure
– Damage due to installation/repair
– Accidental deletion
• Transfer of data between systems
• Reorganizing file systems
• Defragmentation to improve performance
• System image for installation
• Checkpoint (before and after upgrade)
• Long term archive
© Copyright IBM Corporation 2005
Notes:
Uempty If you are going to install a number of similar machines, or wish to be able to quickly
reinstall a machine then a complete system image backup should be used.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe good reasons for backing up data.
Details — It is a known fact that most companies that have not had a backup policy have
gone out of business after a computer “disaster”.
There are three basic ways to reduce the size of file system. When performing a file system
backup, all that needs to be done is to remove the file system, recreate it to make it smaller,
and restore it from the backup. If you have sufficient space in another file system or can
create a temporary filesystem, you can move the contents of the file system to the
temporary space, delete and redefine the file system with a smaller size and then move the
data back. If using an enhanced journal filesystem (JFS2), you can dynamically shrink the
size in place.
This procedure is fine if the file system was not part of the operating system, (for example
/usr).
When working with operating system file systems, the procedure involves a system image
backup (more on this in a few visuals time). The image backup can be adjusted to restore
into the smallest possible file systems. (see the /image.data file later).
Additional Information —
Transition Statement — Having listed the reasons for backing up, let's look at the different
types of backup.
Uempty
Types of Backup
Three types of backup:
• System
– Records image backup of the operating system
• Full
– Preserves all user data and configuration files
• Incremental
– Records changes since previous backups
– Must be used carefully
– Very quick
rootvg
© Copyright IBM Corporation 2005
Notes:
System backup
The system backup (system image backup) records and preserves all system data,
including logical volume inter/intra allocation policies, striping, file system setup (nbpi,
compression, fragment size) and paging setup.
Full backup
A full backup is similar to a system backup, but it is for user data.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Incremental backup
There are two types of incremental backups:
- The first method is to do a full backup. For example, do a full backup on Sunday,
and then for the rest of the week, only backup the changes from the previous day.
This method has the advantage of being quick, but there are a lot of tapes involved.
Should one of the tapes be missing, you will have problems restoring using the
remaining tapes.
- The second method again involves taking a full backup on Sunday. However, the
other days of the week backup only the changes made since the full backup; that is,
since Sunday. The backups take slightly longer than the previous method, and
towards the end of the week, if most of your system has changed, then the time
taken is similar to a full backup. The restoration procedure does not depend on the
tape from the previous day.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Backup Strategy
Backup all data that changes!
System backup
Full backup
Incremental backup
Incremental backup
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Drive
3 1/2-inch (1.44) 3 1/2-inch (2.88)
/dev/fdxl 720 KB 720 KB
/dev/fdxh 1.44 MB 2.88 MB
/dev/fdx.9 720 KB 720 KB
/dev/fdx.18 1.44 MB 1.44 MB
/dev/fdx.36 - 2.88 MB
Notes:
Introduction
Diskettes can be used to backup data. Of course, this media is only practical when
backing up small amounts of data.
The logical device name for a diskette drive is /dev/fdx. Your system most likely has
one diskette drive, fd0. When writing to a diskette, the highest density supported is the
default value. The chart shows there are multiple logical names associated with the
diskette drive that allow writing at different densities. To read the diskettes on a
low-density drive, you must write using the low-density settings.
Uempty Commands
To format a diskette, use the format command. There is a -l options if you want to
format at low density.
The flcopy command is used to copy diskettes (similar to the DOS diskcopy
command).
Diskettes can also be formatted using DOS formatting with the command dosformat.
AIX can read from and write to DOS diskettes using dosread and doswrite. There is
also a dosdir to view the content of the diskette. To use these tools, the fileset
bos.dosutil must be installed.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to use the diskette device.
Details — Diskettes are only useful for small amounts of data.
Don't spend a lot of time on the different names. Make sure everyone understands
/dev/fd0. This is the one they most likely will be using. Point out the device names from the
chart to show the same device can have multiple logical names that will effect how a device
is handled.
Explain that the AIX can read DOS diskettes. Make sure it is clear that AIX cannot run DOS
executables. dosread and doswrite both have a -a option that converts DOS ASCII to
UNIX ASCII.
Additional Information —
Transition Statement — Now, let's look tape backup devices.
Uempty
Backup Devices - Tape
• 4 mm DAT • 1/2 - inch • VXA
• 8 mm • DLT • QIC
/dev/rmtx no no yes
/dev/rmtx.1 no no no
/dev/rmtx.2 no yes yes
/dev/rmtx.3 no yes no
/dev/rmtx.4 yes no yes
/dev/rmtx.5 yes no no
/dev/rmtx.6 yes yes yes
/dev/rmtx.7 yes yes no
© Copyright IBM Corporation 2005
Notes:
Tape technologies
The most common device used for backups are tapes. AIX supports a variety of tape
devices, tape subsystems and tape libraries. Here are some highlights of some of the
tape technologies:
- 4 mm DAT (Digital Audio Tape)
Can hold up to 40 GB of data with a data transfer rate of 6 MB/sec.
- 8 mm Tape
Can hold up to 40 GB of data with a data transfer rate of 6 MB/sec.
- Quarter Inch Cartridge (QIC)
Can hold up to 4 GB with a data transfer rate of 380 KB/sec.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Device names
The tape devices use the logical device name of rmtx (raw magnetic tape). In the chart,
you see the seven additional logical names assigned to each tape device. These
names control tape device characteristics:
- Write at low capacity
- Retension the tape (fast forward and rewind before starting the operation)
- Rewind the tape at the finish of the operation
The most common devices that are used are rmtx and rmtx.1. For most tape
operations, high capacity and no retension are the norm. Whether or not you want to
rewind the tape, depends on your particular operation.
Tapes are formatted at the factory. Tape movement can be controlled using the tctl or
mt commands. If there two tape devices, tcopy allows tape to tape transfers. Details on
these commands are discussed later.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
AIX supports read/write optical drives as well as standard CD-ROM. The R/W Optical
drives support CD-ROM file systems and JFS file systems. If the optical drive is
mounted as a CD-ROM file system, it will be read only.
The optical drive volume group must be wholly contained on the single optical disk. It
cannot span beyond one optical drive.
CD burner
To burn a backup image onto a CD (IS09660), you must install an OEM drive and
software that is capable of CD writes.
To find out what CD writers are supported examine:
/usr/lpp/bos.sysmgt/README.oem_cdwriters.
Two of the CD burner software packages that have been tested with AIX and are
provided on the AIX Toolbox for Linux Applications CD are mkisofs and cdrecord. You
may alternatively download the software from:
http://www.ibm.com/servers/aix/products/aixos/linux/download.html
Whatever software package is installed you will need to link their executables to the AIX
standard command names of /usr/sbin/mkrr_fs and /usr/sbin/burn_cd. For more
details refer to: /usr/lpp/bos.sysmgt/mkcd.README.
Backing up to DVD is only supported with the IBM 7210 (see next visual) and there is
no need to install special software in order to write using the standard UDF format.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
In order to boot from a mksysb CD or DVD, you need to be sure that your hardware is at
the latest firmware level. Procedures for updating pSeries firmware is covered in the
Q1316 AIX System Administration II: Problem Determination course.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Backup Device –
7210 External DVD-RAM Drive
• Writes DVD-RAM media
• Reads DVD media in 2.6 GB, 4.7 GB, 5.2 GB and 9.4 GB
• Supports CD-ROM media in Modes 1 or 2, XA, and CDDA
and audio formats
• Reads multi-session disks, CD-R, CD-ROM, and CD-RW
disks
• Loading tray accommodates 8 cm and12 cm media
• SCSI attachable
Notes:
Description
The IBM 7210 External DVD-RAM Drive Model 025 is a DVD-RAM drive designed to
provide a high performance storage solution. This self-powered standalone drive is
designed for the open systems environment, which includes the IBM iSeries, pSeries,
AS/400, and RS/6000 servers.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Backup menus
The visual shows the SMIT menus that have backup options. Note that the menus in
the visual do not show all the options for a given menu, only those that pertain to
backups.
Backups can also be performed using the Web-based System Manager.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Uempty - Saves striped logical volume attributes in AIX V4.2 and later
- Allows the user to restore single or multiple files from a system image
The volume group image is saved in backup format. The rootvg is created as an
installable image.
Non-interactive installation
If a system backup is being made to install another system or to reinstall the existing
system, a customer can predefine installation information so questions at installation
time are already answered. This keeps user interaction at the target node to a
minimum. The system backup and BOS Install interact through several files. mksysb
saves the data used by the installation through taking a snapshot of the current system
and its customized state.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show what the mksysb command backs up and doesn't back up.
Details — Make sure the students understand that unmounted file systems are ignored.
If you need to clone a machine with different hardware, the machine must be booted from
an installation CD. Then, during the installation from the tape, the appropriate filesets will
automatically be installed using both the mksysb image and the CD. Since the mksysb
image does not contain a complete set of all AIX filesets (it only has the fileset contained on
the source machine), the CD is able to supplement the filesets contained on the mksysb
image.
Additional Information —
Transition Statement — Let's turn our attention to the restore process. There is a file that
allows us to customize restore process.
Uempty
/image.data File for rootvg
image data:
IMAGE_TYPE= bff
DATE_TIME= Fri Nov 29 10:23:36 NFT 2002
UNAME_INFO= AIX ibm150 2 5 00428DFB4C00
PRODUCT_TAPE= no
USERVG_LIST=
PLATFORM= chrp
OSLEVEL= 5.2.0.0
CPU_ID= 00428DFB4C00
logical_volume_policy:
SHRINK= no
EXACT_FIT= no
ils_data:
LANG= en_US
#Command used for vg_data, /usr/sbin/lsvg
vg_data:
VGNAME= rootvg
PPSIZE= 16
VARYON= yes
VG_SOURCE_DISK_LIST= hdisk0
BIGVG= no
TFACTOR= 1
#Command used for source_disk_data: /usr/sbin/bootinfo
source_disk_data: (stanza is repeated for each disk in rootvg)
PVID=(physical volume id)
LOCATION=(disk location)
SIZE_MB=(size of disk in megabytes)
HDISKNAME=(disk name)
#Command used for lv_data; /usr/sbin/lslv
lv_data: (stanza for each logical volume in rootvg)
.
fs_data: (stanza for each MOUNTED filesystem in rootvg)
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
logical_volume_policy stanza
The logical_volume_policy stanza contains information to be used at reinstallation
time. The SHRINK= field when set to YES, causes the system to create logical volumes
and file systems in the volume group based on the values set for each with the
LV_MIN_LPs and FS_MIN_SIZE fields. This option is always set to NO when created by
mkszfile.
The EXACT_FIT= field when set to YES, causes the system to place the logical volumes
on the disk according to the physical partition maps that were generated with the -m flag
of the mksysb or mkszfile command.
If the only thing you wish to change is the SHRINK or EXACT_FIT field, there is no need
to edit this file. Both of these settings can be controlled by the menus presented during
the installation of a mksysb.
vg_data stanza
The vg_data stanza contains information about the volume group. The
VG_SOURCE_DISK_LIST= field specifies the disks that BOS installation uses on a best
effort basis to place the volume group. If the EXACT_FIT= field is set to YES, the user is
warned before installation begins.
lv_data stanza
The lv_data stanza contains information about logical volumes. This type of data
stanza is also used to contain paging space information. Information about striped
logical volumes and large file enabled file systems are placed in this stanza in AIX V4.2
and later.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
/bosinst.data creation
This file allows the administrator to specify the requirements at the target system and
how the user interacts with the target system. It provides flexibility by allowing different
target hardware to use the same backup image. The system backup utilities simply
copy the /bosinst.data into the second file in the rootvg on the mksysb tape. If this file
is not in the root directory, the /usr/lpp/bosinst/bosinst.template is copied to the
/bosinst.data.
The sample file shown in the visual has been condensed to highlight key areas. The
actual file is well documented with comments contained within the file.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
target_disk_data stanza
The target_disk_data stanza contains variables for disks in the machine where the
program will install BOS. The default bosinst.data file has one target_disk_data
stanza, but you can add new stanzas to install BOS on multiple disks, one stanza for
each disk.
Multiple target_disk_data stanzas can exist. They define the disks that are to contain
the root volume group. Only one field (PVID, PHYSICAL_LOCATION, SAN_DISKID,
CONNECTION, LOCATION, SIZE_MB, HDISKNAME) must be non-null for BOS installation to
choose a disk. The order of precedence is PVID, PHYSICAL_LOCATION, SAN_DISKID,
then CONNECTION, then LOCATION, then SIZE_MB, and then HDISKNAME.
The field definitions are:
- LOCATION specifies a location code for the disk where the program will install BOS.
- SIZE_MB specifies the formatted size of the disk (in megabytes) where the program
will install BOS.
- HDISKNAME specifies the path name of the target disk.
- PVID specifies the physical volume identifier for the disk.
- PHYSICAL_ LOCATION provides a way to identify fibre channel disks during BOS
Install. The information in the PHYSICAL_LOCATION field supersedes the information
in the SAN_DISKID field.
- SAN_DISKID specifies the World Wide Port Name and a Logical Unit ID for fibre
channel-attached disks.
Uempty - CONNECTION specifies the combination of the parent attribute and the connwhere
attribute associated with a disk.
locale stanza
- The locale stanza contains variables for the primary language the installed
machine will use
- BOSINST_LANG specifies the language the installation program uses for prompts,
menus and error messages
- CULTURAL_CONVENTION specifies the primary locale to install
- MESSAGES specifies the locale for the messages catalogs to install
- KEYBOARD specifies the keyboard map to install
Unattended reinstallation
With both the /image.data and the /bosinst.data files created, the reinstallation of
AIX V4 and later can be made unattended.
The procedure to accomplish this is as follows:
1. Edit the bosinst.data file as follows:
a) Set CONSOLE=/dev/lft0 or CONSOLE=/dev/tty0 according to your system
b) Set PROMPT=no
c) Set EXISTING_SYSTEM_OVERWRITE=yes
d) Set RUN_STARTUP=no
2. Create the signature file:
echo "data" > signature
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The SMIT screen shown in the visual, Back Up the System, only backs up mounted
file systems in rootvg. Use one of the other backup commands to backup other volume
groups.
EXCLUDE files?
This option excludes the files and directories listed in the /etc/exclude.rootvg file from
the system image backup.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how SMIT performs a system image backup.
Details — Some older PCI machines cannot boot from a tape device. If you are using one
of these older machines, you will need to boot from an installation CD. During the
installation, you specify the location of the files to restore. In this case, specify the tape
device.
You can use the bootinfo -e command to determine if the machine is bootable from tape.
If a 1 is returned, the system is tape bootable. A 0 indicates it is not.
Some documentation indicates that the bootinfo command is not supported in AIX V4.2
and later. However, the command still exists and executes on the AIX V4.3 and later
systems.
Beginning with AIX V4.2 also has the option List files as they are backed up?. This
corresponds to the -v option of the mksysb command. Another option is -p, which can be
used to disable packing of files.
Additional Information — In order to create a bootable tape, sufficient space is required
in /tmp. Use the command bosboot -qad hdiskn to determine how much space will be
needed in the /tmp directory when creating the mksysb image.
A restriction on the mksysb utility is that only mounted file systems are backed up!
Transition Statement — We now look at how non-rootvg volume groups are backed up.
Let's see what the tape format looks like for a mksysb image.
Uempty
mksysb Image
Notes:
Introduction
This visual shows the tape layout of a mksysb image.
mkinsttape image
The mkinsttape image contains two files:
- ./image.data holds the information needed to recreate the root volume group and its
logical volumes and file systems.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Dummy TOC
The dummy TOC is used to make mksysb tapes have the same number of files as the
BOS installation tapes.
rootvg data
The rootvg data contains all the data from the backup. This data is saved using the
backup command which is discussed shortly.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To cover how to backup non-rootvg volume groups.
Details — The SMIT screens for Back Up a Volume Group to Tape/File and Back Up the
System are nearly identical since they both perform volume group backups. But, Back Up
the System, using mksysb, creates bootable backups.
Since you have just covered the Back Up the System screen, you only need to point out
the differences. Review the student notes for those differences.
The command that is run is savevg. The -i option calls the mkvgdata command to create
the vg_name.data file. The -m option creates map files.
Additional Information — This screen can backup rootvg but it will not be bootable.
Therefore, Back Up the System, using mksysb, is the tool of choice for rootvg.
Transition Statement — Once you have your backups, how do you recover? Let's take a
look.
Uempty
Restoring a mksysb (1 of 2)
• Boot the system in install/maintenance mode:
Welcome to Base Operating System
Installation and Maintenance
1 Start Install Now With Default Settings
2 Change/Show Installation Settings and Install
>> 3 Start Maintenance Mode for System Recovery
Maintenance
1 Access A Root Volume Group
2 Copy a System Dump to Removable Media
3 Access Advanced Maintenance Functions
>> 4 Install from a System Backup
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the correct procedure to recover the mksysb image.
Details — Explain how to boot the machine from tape. This should be a review from the
installation section, so ask the students how it is done.
Make sure they understand about boot lists and ensuring the device they are trying to boot
from precedes the hard disk.
Additional Information — Some older PCI machines could not boot from tape. They have
to boot from CD. The procedure is the same only you will need both the installation CD and
the mksysb image. Some PCI models will not support an AIX 5L V5.2 and later image.
The command bootinfo -e will display whether the machine can boot from tape (1=yes,
0=no). The man pages state that bootinfo is not a supported command in 4.2 and later, but
it still works.
When booting from a tape, there is a limit in the size of the boot image which can be
handled. If there are too many device drivers installed on the system being backed up, the
boot image size will exceed this limit and will not be bootable. In that situation, it may be
necessary to boot into maintenance mode from installation media and then specify the tape
as the source of the mksysb backup image.
Transition Statement — You will then see two more screens. Let's take a look.
Uempty
Restoring a mksysb (2 of 2)
Welcome to Base Operating System
Installation and Maintenance
Type the number of your choice and press Enter. Choice is indicated by >>.
1 Start Install Now With Default Settings
>> 2 Change/Show Installation Settings and Install
3 Start Maintenance Mode for System Recovery
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
- 3 Shrink Filesystems
The option Shrink Filesystems installs the file systems using the minimum required
space. The default is no. If yes, all file systems in rootvg are shrunk. So remember
after the restore, evaluate the current file system sizes. You might need to increase
their sizes.
- 0 Install with the settings listed above
At the end, select option 0 which will install using the settings selected. Your mksysb
image is restored.
The system then reboots.
Note: The total restore time varies from system to system. A good rule of thumb is twice
the amount of time it took to create the mksysb.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
* Restore DEVICE or FILE [/dev/rmt0] +/
SHRINK the filesystems? no +
Recreate logical volumes and filesystems only no +
PHYSICAL VOLUME names [] +
(Leave blank to use the PHYSICAL VOLUMES listed
in the vgname.data file in the backup image)
Use existing MAP files? yes +
Physical partition SIZE in megabytes [] +#
(Leave blank to have the SIZE determined
based on disk size)
Number of BLOCKS to read in a single input [] #
(Leave blank to use a system default)
Alternate vg.data file [] /
(Leave blank to use vg.data stored in
backup image)
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show how a non-rootvg volume group can be restored using SMIT.
Details — This utility can be used to shrink the size of file systems contained in an external
volume group. If yes is chosen for SHRINK the filesystems?, the file systems within the
volume group will be recreated to the minimum size required to contain the data. This
reduces wasted free space in a file system
Additional Information — Individual file systems can be shrunk by editing the
vg_name.data file. This is not covered in this class
The Recreate logical volumes and filesystems only option will use the image.data
information to recreate the logical volumes and file systems, but will not restore any of the
data to the file systems.
Transition Statement — We will now look at how to backup the a system to either CD or
DVD, but to fully understand the options we need to first discuss the differences between
using ISO9660 and UDF mechanisms.
Uempty
mksysb - ISO9660 Burn Image
mksysb image
packages
bundle file
cust script
bosinst.data
image.data
burn image
CD or DVD
Notes:
What is stored?
When creating a system backup on CD or DVD, it is actually creating a file system on
the disk. Within the file system, many things are stored.
The mksysb image file itself is stored (in backup format).
The files that would normally be placed in the second record of a mksysb tape also need
to be stored: bosinst.data and image.data.
If you want to be able to install additional software during the restore (such as device
drivers) you can place them in this file system as packages or additionally defined as
bundles.
Finally, you may want to run a customization script after the image restore to do
additional configuration.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
When burning the file system onto a CD or DVD, using the ISO9660 standard, you need
to first build a burn image on the hard drive. Then, you need to actually burn that to the
disk.
When using ISO9660, you need to identify:
- Where to store the mksysb image
- Where to build the file structure
- Where to build the burn image
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
mksysb image
packages
bundle file
cust script
bosinst.data
image.data
UDF DVD
File system
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
The smit fastpath for the panel shown in the visual is smit mkdvd. When prompted,
choose the ISO9660 option.
The types of information to write to media and the mechanisms are about the same for
CD or DVD when using ISO9660 to first build the image and then burn it to the media.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
DVD-RAM Device [] +
mkysyb creation options:
Create map files? no +
Exclude files? no +
Disable software packing of backup? no +
Backup extended attributes? yes +
File system to store mksysb image [] /
(If blank, the file system
will be created for you.)
If file system is being created:
Volume Group for created file system [rootvg] +
Notes:
The smit fastpath for the panel shown in the visual is: smit mkdvd. When prompted,
choose the UDF option.
Backup volume groups in UDF (Universal Disk Format) format on DVD-RAM requires
only the space for the backup image:
1. Create backup image
2. Burn to media
This allows modification of files such as bosinst.data, image.data, and vgname.data.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
You don’t have the multiple types of information backed up for a non-rootvg volume
group as you did for the system backups, but the mechanisms are very similar when
using ISO9660.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
Backing up a non-rootvg volume group to ISO9660 DVD is similar to backing up a
rootvg volume group.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Overview
Backing up a non-rootvg volume group to UDF DVD is similar to backing up a rootvg
volume group.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Figure 14-29. Exercise 14: Using backup and restore (Part 1) AU1411.0
Notes:
Introduction
In this exercise, you create a backup of datavg and save it to the a file in rootvg.
The exercise can be found in your Student Exercises Guide.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Back Up by Filename
backup -i [-q] [-p] [-v] [-f device]
-q Media is ready
-p Pack files which are less than 2 GB
-v Verbose - display filenames during backup
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To explain the syntax used with backup and explain the different between
backup by file systems and backup by inode.
Details — Make sure the difference between the two method is understood.
Additional Information — The -p option is not needed if the tape device itself is doing
compression. The 2 GB limit to file compression is a characteristic of the pack utility that is
used here.
Transition Statement — Standard input is used to determine what files are backed up with
a backup by name. This list of files can be supplied by a file or by a command. Let's take a
look at a few examples.
Uempty
Back Up by Filename Examples
• Example 1: Read input from a file
# cat listfile
/home/roy/file1
/home/roy/file2
/home/roy/file3
# backup -iqvf /dev/rmt0 < listfile
Notes:
Introduction
The list of files backup uses can be supplied by a file or by commands. The visual
provides a sample of each.
Example 1
In the first example, the file listfile contains the files you want to back up. That is fed
into the backup command by using a redirection (<).
Example 2
In the second example, there are two examples that can be used to back up the same
data using the find command to generate the file list. Both commands back up the files
stored in /home/roy. Even though both find examples save the same data, the
filenames will be stored differently.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Types of pathnames
There are two types of filenames:
- Relative
- Full (or absolute)
The difference is that a full pathname shows the location referenced from the root
directory. Basically, the name starts with a slash (/). The relative pathname shows the
location referenced by the current directory. This distinction is important when you try to
recover the data.
Full pathname backups restore to the same location in the directory structure since their
position is referenced from the root directory. But, a relative pathname file is restored
based upon the current directory when the restore command is issued. Full pathnames
provide certainty of location and relative pathnames provided flexibility.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Syntax:
backup [-u] [-level] [-f device] filesystem
Notes:
Uempty -u option
The -u option causes backup to update the /etc/dumpdates file to record the date and
level of the last inode backup for that file system. This file holds file system backup
information for the backup command. The information included in this file is the name of
the file system, the level number of the last backup, and the date of the incremental
backup.
-level option
The -level option allows you to perform incremental backups. The -0 level backs up
all files in the file system. The -1 level backs up all files changed since the last -0
backup, and so on. (If you do not specify a level, -9 is assumed.)
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show how the backup command can be used to backup entire file systems.
Details — This method is more commonly known as backup by inode. The advantage of
an incremental backup rather than a full backup is that incremental backups take less time
(in general). The disadvantage is there are many more tapes involved in the process. If one
of the tapes is misplaced, then you can only partially restore that data successfully.
The -u option is required if you are making an incremental backup.
The /etc/dumpdates file is appended to each time the backup command is run with the -u
option and thus it grows over time. It is recommended that old dumpdates entries prior to
the last level 0 backup be periodically removed.
Additional Information —
Transition Statement — Let's look at an example.
Uempty
Incremental Backup Example
1 2
level 0
3 4 5 6 7 8 9
level 6 level 6 level 6 level 6 level 3
10 11 12 13 14 15 16
level 6 level 6 level 6 level 6 level 0
17 18 19 20 21 22 23
level 6 level 6 level 6 level 6 level 3
24 25 26 27 28 29 30
level 6 level 6 level 6 level 6 level 0
31
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Calendar example
The visual shows a calendar that describes how different levels of backups can be
accomplished.
- A level 0 backup is performed on the first Friday, and thereafter every other Friday.
- A level 6 is performed on each day of the week except on the Fridays that a full
backup is not carried out, when a level 3 backup is performed.
- During the first full week, the level 6 backup on Monday backs up all files modified
since the level 0 backup on the previous Friday. Each level 6 backup Tuesday
through Thursday backs up all files that have been modified since the last n-1
backup or lower (in this case level 0).
- The first level 3 backup of the month backs up all files modified since the level 0
backup. The remaining level 3 backups backs up all those files modified since the
last level 0 backup.
- During the second full week, the level 6 backups on Monday through Thursday back
up all files that were modified since the last level 3 backup. The level 3 backups on
Fridays backs up everything since the last level 0.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
This option will perform a backup by inode.
* FILESYSTEM to backup [] +/
* Backup DEVICE [/dev/fd0] +/
Backup LEVEL (0 for a full backup) [0] #
RECORD backup in /etc/dumpdates? no +
Backup extended attributes? yes +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-93
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
restore Command (1 of 2)
• List files on media (verify the backup):
restore -T [-q] [-v] [-f device]
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-95
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to use the restore command.
Details — The restore command is used to extract data from backups.
The -T option allows you to verify the backup. This should be done after each backup to
ensure the data is really there. This will not actually restore anything.
The -x option can be used with both inode backups and backups by name. The -x
doesn't provide a restoresymtable file when restoring. If you are planning to restore the
entire file system, the -r option is preferred.
The -r option only works with inode backups. The -i only works with inode backs as well.
Additional Information — Make certain everyone understands that the file system must
exist and be mounted prior to restoring the data. The backup command, unlike mksysb and
savevg, doesn't save any structural information. It only has the filenames and data contain
in those files. Therefore when the recovery occurs, it expects the file system to be in place.
Transition Statement — The restore command had a few enhancements beginning with
AIX 5L V5.2, let’s take a look at those.
Uempty
restore Command (2 of 2)
• Restores the file attributes without restoring the file contents:
restore -Pstring [-q] [-v] [-f device] [file1 file2 ...]
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-97
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how to restore only the file attributes.
Details — If the file specified does not exist in the target directory path, the file is not
created.
Usage of -P flag will overwrite the attributes of files owned by another user when executed
by the superuser.
Additional Information —
Transition Statement — Recoveries can be performed from SMIT. Let's take a look at that
screen.
Uempty
Restore a File or a Directory
# smit restfile
Restore a File or Directory
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Restore DEVICE [/dev/fd0] +/
* Target DIRECTORY [.] /
FILE or DIRECTORY to restore []
(Leave blank to restore entire archive.)
VERBOSE output? no +
Number of BLOCKS to read in a single input [] #
operation
Restore Extended Attributes? yes +
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-99
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show how SMIT can be used to restore files or directories from a backup.
Details — Note that if the files were backed up using relative pathnames, you have to
change to the correct directory before the files are restored.
If the backup was of a file system, the path names are ALWAYS relative.
Additional Information —
Transition Statement — Let’s do an exercise using backup and restore.
Uempty
Exercise 14: Using backup and restore
(Parts 2, 3 and 4)
Figure 14-39. Exercise 14: Using backup and restore (Parts 2, 3, and 4) AU1411.0
Notes:
Introduction
This lab allows you to perform backups and recoveries using the AIX tools, backup and
restore. It gives you an opportunity to perform a backup by name and a backup by
inode.
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-101
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details — The students already did Part 1 of this exercise earlier in this unit.
Additional Information —
Transition Statement — The backup and restore commands are AIX-specific. To move
information between UNIX platforms, standard commands are provided.
Uempty
Other UNIX Backup Commands
•tar (tape archive)
– Widely available
– Good for transfer of data between platforms
– Had no support for extended inode (ACLs) until
AIX 5L V5.3
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-103
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The dd command
The dd command is used to copy and convert data byte-by-byte.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-105
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The tar command only works with mounted file systems.
Here is a list of the commonly use options:
-c create a tar backup
-x extract (restore) a file(s) from a tar file
-t reads the content of the tar file (verify the backup)
-v verbose output - displays files as they are backed up and restored
-f identify the file or device holding the tar image
Uempty example, /home is the starting point for the tar command. It backs up all of /home and
its subdirectories, and so on.
# echo $?
3
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-107
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the usage of the tar command.
Details — tar is a generic UNIX backup tool. You should be familiar with it to allow file
transfers to other systems.
The default backup device for tar is /dev/rmt0 but the -f option is used to specify a
different location.
tar is not enabled for files larger than 2 GB due to size limitation imposed by XPG/4 and
POSIX.2 standards.
Make sure everyone understands that the file named to be backed up is the starting point.
It is much like naming the starting point with the find command. It backups everything
recursively, unless you use the new -D flag to repress recursive processing.
Additional Information — If root restores a tar image, all files retain their original
ownership. If a non-root user attempts to restore a tar image, that user owns all of the
files. This prevents someone from restoring root files from a tar image by someone without
root authority.
While AIX 5L 5.3 supports the backup and restore of ACL extended attributes, if you’re
using it to copy between systems be sure that the target system and utility also support
extended ACLs.
Transition Statement — Let take a look at another widely used UNIX backup tool, cpio.
Uempty
The cpio Command
• Generate a cpio backup:
Notes:
Introduction
The cpio tool is another generic UNIX tool. cpio stands for copy input/output.
Some of the common options that are used with cpio:
-o Create a cpio image (output).
-i Read from a cpio image (input).
-t Read (verify) the content of a cpio image.
-v Verbose output - list files during backup and restore operations.
-d Create necessary directories when recovering an image.
-m Retain the original modification times associated with files contained in a
cpio image. Without the -m option, all files will have modification times
associated with the time they were restored.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-109
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-111
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The dd Command
• The dd command converts and copies files
Notes:
Introduction
The dd command reads in standard input or the specified input file, converts it, and then
writes to standard out or the named output.
The common options are:
if= specifies the input file
of= specifies the output file
conv= designate the conversion to be done
Uempty Examples
In the first example in the visual, the file /etc/inittab is copied to the floppy diskette.
In the second example in the visual, the file text.ascii is converted into EBCDIC and is
written to a file called ebcdic.text.
In the last example in the visual, no output or input file is specified so standard out and
standard in is used. The file containing lower case characters, lcase, is converted into
uppercase characters and displayed to standard out.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-113
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the dd command.
Details —
Additional Information —
Transition Statement — When working with tapes, you need to position it at times.
Uempty
Controlling the Tape
rewind Rewinds a tape
tctl fsf Fast forwards a tape
offline Ejects a tape
rewoffl Rewinds and ejects a tape
restore -s
# restore -s 4 -xvf /dev/rmt0.1 ./etc/inittab
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-115
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-117
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Good Practices
• Verify your backups
• Label tape
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-119
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To emphasize some good practices.
Details — Go through each bullet point. Planning and testing is always the best approach
to backup practices. Redundancy and documentation is also very important.
Additional Information —
Transition Statement — Now, let's answer a few checkpoint questions.
Uempty
Checkpoint
1. What is the difference between the following two commands?
a) find /home/fred | backup -ivf /dev/rmt0
b) cd /home/fred; find . | backup -ivf /dev/rmt0
___________________________________________________
___________________________________________________
___________________________________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-121
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Details — Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
1. What is the difference between the following two commands?
a) find /home/fred | backup -ivf /dev/rmt0
b) cd /home/fred; find . | backup -ivf /dev/rmt0
(a) will backup the files using the full path names, whereas
(b) will backup the file names using the relative path names.
So (b)’s files can be restored into any directory.
2. On a mksysb tape, if you entered tctl rewind and then
tctl -f/dev/rmt0.1 fsf 3, which element on the tape could
you look at? You would be at the start of the backed up images of
the files, having skipped over the boot portion of the tape.
3. Which command could you use to restore these files?
The files were backed up using the backup command so you would
have to use the restore command.
4. True or False? smit mksysb backs up all file systems, provided
they are mounted. mksysb only backs up rootvg file systems. To
back up other volume groups, you must use the savevg command.
Additional Information —
Transition Statement — If there is time and interest, have the students do the optional
exercise.
Uempty
Exercise 15: (Optional) Using tar and cpio
• Using tar
• Using cpio
Figure 14-47. Exercise 15: (Optional) Using tar and cpio . AU1411.0
Notes:
Introduction
This is an optional exercise. The instructor determines if there is time and interest to
complete this exercise. It gives an opportunity to try out the generic UNIX tools, tar and
cpio.
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-123
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details —
Additional Information —
Transition Statement — Summarize the unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 14. Backup and Restore 14-125
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit
Details —
Additional Information —
Transition Statement — Now, onto the next unit.
References
SC23-4910 AIX 5L Version 5.3 System Management Guide:
Operating System and Devices
SC23-4907 AIX 5L Version 5.3 Security Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Define the concepts of users and groups, and explain how
and when these should be allocated on the system
• Describe ways of controlling root access on the system
• Explain the uses of SUID, SGID and SVTX permission bits
• Administer user accounts and groups
• Identify the data files associated with users and security
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
User Accounts
• Each user has a unique name, numeric ID, and password
• File ownership is determined by a numeric user ID
• The owner is usually the user who created the file, but
ownership can be transferred by root
• Default users:
– root Superuser
– adm, sys, bin, ... IDs that own system files but
cannot be used for login
Notes:
File ownership
When a file is created, the UID associated with the process that created the file is
assigned ownership of the file. Only the owner or root can change the access
permissions.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Highlight some basic concepts concerning AIX security, particularly the role of
user accounts in setting up system security.
Details — AIX security can be defined by two basic principles:
1. Ownership of data controls access
2. Permissions or access to the data is granted by the owner to other users
Additional Information — In the event you are asked:
• AIX 5L V5.3 introduced several security-related features, including support for long (up
to 255 characters in length) user names.
• AIX 5L provides support for a variety of system-level security options including C2 and
optional B1 functions.
• AIX 5L provides support for International Computer Security Association (ICSA) Virtual
Private Network (VPN). Beginning with AIX 5L, enhancements were made to the
Internet Key Exchange (IKE) protocol to enable the use of Certificate Revocation Lists
(CRL) when authenticating remote users or devices. AIX V4.3 was the first server
operating system to receive Virtual Private Network (VPN) certification by the
International Computer Security Association (ICSA).
• AIX 5L includes Network Authentication Service, IBM's implementation of MIT's
Kerberos V5 Release 1.1 network authentication service. Network Authentication
Service negotiates authentication between two points on the Internet or between
components on a system.
• A new version of IBM SecureWay Directory was released with AIX 5L. SecureWay
Directory provides a common directory for you to address the proliferation of
application-specific directories, a major driver of high costs. IBM SecureWay Directory
is a Lightweight Directory Access Protocol (LDAP) cross-platform, highly scalable,
robust directory server.
• AIX 5L offers an implementation of the cryptographic API PKCS#11 version 2.01.
PKCS#11 is a de facto industry standard for accessing cryptographic hardware devices.
• AIX V4.3 was the first 64-bit operating system to achieve the high E3/F-C2 level
security rating by the Bundesamt Für Sicherheit in der Informationstechnik, a German
government certification authority.
• AIX V4.3 was also the first 64-bit UNIX environment to receive the TCSEC C2
certification from the US Government National Security Agency (NSA).
• AIX V4.3, along with Groupe Bull's B1/EST-X, received the Common Criteria 2.0 B1
certification recognized in many countries around the world.
• The TCSEC security levels can be researched at:
http://www.radium.ncsc.mil/tpep/library/rainbow/.
The European ITSEC levels can be researched at:
http://www.cesg.gov.uk/site/iacs/itsec/media/formal-docs/Itsec.pdf
Uempty • The newer Common Criteria for Information Technology Security Evaluation (CCITSE),
also referred to as simply the Common Criteria (CC), can be researched at
http://commoncriteriaportal.org. AIX 5L V5.2 and later provides the ability to enable
Controlled Access Protection Profile (CAPP) and Evaluation Assurance Level 4+
(EAL4+) technology based on CC standards.
Transition Statement — The effective use of groups is also important in promoting AIX
system security.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Groups
• A group is a set of users, all of whom need access to a
given set of files.
• Every user is a member of at least one group and can be a
member of several groups.
• The user has access to a file if any group in the user’s
groupset provides access. To list the groupset, use the
groups command.
• The user's real group ID is used for file ownership on
creation. To change the real group ID, use the newgrp
command.
• Default groups:
– System administrators: system
– Ordinary users: staff
Notes:
Function of groups
Users that require shared access to a set of files are placed in groups. Each group has
a unique name and Group ID (GID). The GID, like the UID, is assigned to a file when it
is created.
A user can belong to multiple groups.
Predefined groups
There are several groups predefined on an AIX system. For example, the system
group is root's group and the staff group is for all ordinary users.
Types of groups
There are three types of groups on the system:
- User Groups
User groups should be made for people who need to share files on the system, such
as people who work in the same department, or people who are working on the
same project.
- System Administrator Groups
System administrators are automatically members of the system group.
Membership of this group allows the administrators to perform some of the system
tasks without having to be the root user.
- System Defined Groups
Several system-defined groups exist. staff is the default group for all
non-administrative users created in the system. security is another system-defined
group having limited privileges for performing security administration. The
system-defined groups are used to control certain subsystems.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the concept of a group and to show how users can change their
group.
Details — A user’s groupset can contain up to 32 groups. The permissions of each group
in the groupset are available to the user.
When defining a user via SMIT or mkuser, you have the option of specifying a “primary
group ID”. This is stored as the “principal group ID” in the etc/passwd file. When the user
initially logs in, this “principal group ID” is used to establish the “real group ID” in the user's
environment. The current “real group ID” is recorded in the inode of any new file created in
that environment, unless overridden by a SGID on the parent directory. While the “real
group ID”, can be changed using the newgroup command, the “principle group ID” in
/etc/passwd is unaffected and will be used to set the “real group ID” the next time the user
logs in.
Additional Information — The entry for the newgrp command in the AIX 5L Version 5.3
Commands Reference has some helpful information.
Transition Statement — Several groups have been mentioned. Now, let’s look at the
group hierarchy.
Uempty
Group Hierarchy
system security
Rights to
printq administrative
adm functions
audit
shutdown
staff Ordinary
user
Notes:
Common groups
Common groups on the system (and their intended uses) are as follows:
system For most configuration and standard hardware and software
maintenance.
printq For managing queuing. Typical commands which can be run by
members of this group are: enable, disable, qadm, qpri, and so forth.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
security To handle most passwords and limits control. Typical commands which
can be run by members of this group are: mkuser, rmuser, pwdadm,
chuser, chgroup, and so forth.
adm Most monitoring functions such as performance, cron, accounting
staff Default group assigned to all new users. You may want to change this in
/usr/lib/security/mkuser.defaults.
audit For auditors.
shutdown Allows use of the shutdown command.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
User Hierarchy
• To protect important users and groups from members of the
security group, AIX has admin users and admin groups
• Only root can add, remove, or change an admin user or
admin group
• Any user on the system can be defined as an admin user
regardless of the group they are in
root
admin user
(admin flag set to true)
normal user
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss important concepts related to root security.
Details — Review the information on the visual.
Having different passwords on every machine may cause a problem if there are lots of
machines. This needs to be done sensibly. Administrators could create a password
scheme that makes each password slightly different but not impossible to remember.
Be sure to point out the dangers of having an unsecured directory in root's PATH. This
includes the dot (.) for the current directory. You might want to use an example like:
PATH=.:/usr/bin:/usr/sbin
Since the dot (.) represents the current directory, the root user might accidentally execute
something in that directory. A user on the system could creates a destructive file called “ls”
that contains the one line to delete all the files on the system “rm -r /”. If the root user is
in that user's home directory and tries to perform a file listing, instead of /usr/bin/ls
running, it will find ./ls first. When this file is run by the unsuspecting system administrator
with root authority, the system will be destroyed.
If the user normally logs in as a regular user and su's to root, the regular account's PATH
should also avoid using unsecured directories. Remember, with the su command, if the
dash (-) is not used, then the current environment is kept (that includes PATH).
Additional Information —
Transition Statement — Reference to the su audit trail is made in this visual. Let's take a
look at a number of files important for system security.
Uempty
Security Logs
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
File/Directory Permissions
Notes:
Permission bits
There are a number of permission bits associated with files and directories. The
standard r (read), w (write) and x (execute) permissions define three levels of access
for the user (owner), group and others. In addition there are three permission bits
known as SUID (set UID), SGID (set GID) and SVTX (sticky bit).
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Examine the effect that permissions have on files and directories.
Details — The effects of permissions are often forgotten or misunderstood. It is probably a
good idea to review all the permission bits.
Read permission on a file allows the contents to be examined. The cat, pg and more
commands will work successfully if r is set on the file. Read on the directory allows the
content of the directory to be seen (use the ls command). Keep in mind that a directory is
a file in UNIX; it is a file that contains a list of ordinary files. Therefore, r has the same effect
on both files and directories - it allows you to see the content.
Write permission allows the content to be changed. On a file, this mean modifying the
content with an editor (like vi) or with redirections (> or >>). On a directory, modifying the
content means adding or removing a file from the directory (rm, vi, touch).
The execute permission on a file allows the file to be executed by using the name of the file
as a command. A shell script without this permission can still be executed, however the
shell must be specified as part of the command. For example:
# ksh file1 or # . ./file1.
Execute on a directory gives permission to access the directory. This includes using cd to
enter the directory or accessing a file were the directory is in the path to the file. All the
parent directories must have execute permission as well to allow access to a subdirectory.
There are examples to explain the extra permission bits following this visual. Provide an
introduction here and fully explain using the visuals that follow.
Additional Information — The base permission (rwx) must give the user the appropriate
permission before SUID, SGID, or STVX are effective. For example, if a user is part of
“others” and “others” don't have execute permission on a file, it is irrelevant whether the
SUID bit is set for that user since they can't execute the file.
SUID and SGID bits will not be effective on shell scripts for security reasons. They can be
set but they will be ignore during execution.
Also, many people misuse the terminology related to these additional permission bits.
Many times all three are incorrectly referred to as the “sticky bits”. Only SVTX is the “sticky
bit”. SUID is “SUID” and SGID is “SGID”. Be sure to keep your students on track with the
proper terminology.
Historically, SVTX stood for “Save Text” and was meant to keep a binary executable in
memory. AIX does not support that use of the permission bit.
Transition Statement — Let's see how these permissions appear when listing a file.
Uempty
Reading Permissions
s s t
S S T
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Changing Permissions
4 2 1
SUID SGID SVTX
owner group other
r w x r w x r w x
4 2 1 4 2 1 4 2 1
Notes:
Uempty You normally use the numeric values of 4, 2, and 1 to set r, w and x. That remains the
same. To set the additional bits, you are affecting the x position in either the user, group
or other area. If you assign numeric values to user (4), group (2), and other (1), these
are the values that you insert into the fourth position to set the additional bit:
- SUID is indicated in the user's area; therefore use a 4 in the fourth position
- SGID is indicated in the group area; therefore use a 2 in the fourth position
- SVTX is indicated in the others area; therefore use a 1 in the fourth position
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Demonstrate how to set or change extended permissions on files or
directories.
Details — Explain the students notes to be sure the students understand how to set the
permission bits. This is sometimes a difficult concept for students to grasp.
Remind the students that when using the octal method, all permission are reset to the
indicated value. With symbolic notation, use of the “+” allows for permission to be added to
the existing permission set.
The symbolic notation can be viewed as having three parts.
- The first part identifies the target user category. It can be u for user (owner), g for
group, o for other, or a for all.
- The second part is the operator. It can be + to add, - to remove, or = to reset the
permissions.
- The third part is which permission bits to change. r is read, w is write, x is execute, s
is set (SUID or SGID), and t is SVTX.
The meaning of the s in the third part is determined by which user category is being
specified.
The first and third parts can be a combination of values. For example: ug+rw would add
read and write authority to both the owner and the group.
You can also have a list of operations separated by commas. For example: u=wrx,go=r.
Additional Information — If using Access Control Lists (ACLs), the octal notation will
disable them. This is not a topic for this course; this is for your information only.
The symbolic notation will not affect ACLs unless they were enabled with no ACLs
specified. In that case, the symbolic notation will set the ACL to disabled. This doesn't
really impact anything, since no ACLs were set anyway in this case.
Transition Statement — Let's see what determines the default permission on a file.
Uempty
umask
• The umask governs permissions on new files and
directories
• System default umask is 022
• A umask of 027 is recommended
• If the umask value is set to 022, then any ordinary files or
directories created will inherit the following permissions:
– Ordinary file: rw-r--r--
– Directory: rwxr-xr-x
• /etc/security/user specifies default and individual user
umask values
Notes:
Function of umask
The umask specifies what permission bits are set on a new file when it is created. It is
an octal number that specifies which of the permission bits will not be set.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Changing Ownership
The chown command:
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to change ownership and group ownership of a file.
Details — These are fairly easy commands to use. Explain the examples on the visual.
Only root can change the ownership of file. This is a security issue. For example, this
prevents a user from creating a destructive file and then transferring the ownership to a
co-worker he doesn't like.
Additional Information —
Transition Statement — Let's try an exercise.
Uempty
Exercise 16: Security Files
Notes:
Introduction
This lab gives you a chance to look at some of the security files and allows you an
opportunity to work with the SUID, SGID, and SVTX.
The exercise can be found in your Student Exercises Guide.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the Security Files exercise.
Details —
Additional Information —
Transition Statement — The next topic in this unit is user administration.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Login Sequence
getty Started by init
port settings in ODM
login
Settings in:
/etc/security/login.cfg
User enters login name
Valid
/etc/environment
Log entry in: /etc/security/environ
/etc/security/failedlogin Setup environment /etc/security/limits
/etc/security/user
Display /etc/motd?
$HOME/.hushlogin
shell
/etc/environment
/etc/profile
$HOME/.profile
Notes:
Introduction
When a user attempts to log in, AIX checks a number of files to determine if entry is
permitted to the system and, if permitted, what parts of the system the user can access.
This section provides an overview of the checks performed during the login process.
Validation
When the user enters the password, it is checked. If the password is incorrect or if an
invalid user name was given, then the login fails, and an entry is made in the file
/etc/security/failedlogin. (Use the command who /etc/security/failedlogin to
view this file.) The number of failed attempts is also tracked (by user account) in
/etc/security/lastlog. The Login: prompt is redisplayed for another attempt.
It is possible to set the characteristics for a user to prevent unlimited attempts on an
account. If the number of attempts exceeds the maximum allowable failed attempts, the
account is locked.
If a user successfully enters the user name and password, the usw stanza in
/etc/security/login.cfg is checked. This stanza sets the maximum number of
concurrent logins for a user account. If that number is exceeded, the login is denied and
a message is displayed to the user.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the 'big picture' of what happens when a user logs in.
Details — Explain the visual as per the student notes. The steps have been extensively
documented.
Additional Information — In the past, /etc/passwd and /etc/security/passwd were
searched sequentially to find the user's ID and password. This was adequate in the days
when there were just a few users per system. Now, there may be hundreds or thousands of
users on a system. If these files are read sequentially, and the user's entry is near the end
of the file, it is possible for the login attempt to timeout before completion. Also, the amount
of cpu time being consumed by the login process is becoming cause for concern.
In AIX, this can be addressed by creating indexes of these two login files. The files
themselves have not been changed. Students may notice the indexes in the system: For
example, the indexes for the /etc/passwd file are /etc/passwd.nm.idx and
/etc/passwd.id.idx.
The indexes are created when the mkpasswd -f command is executed. It deletes any
existing indexes and builds new indexes.
The /etc/security/lastlog file is also indexed in AIX.
/var/adm/wtmp also is updated during the login and logout process. This file keeps track of
times for a successful logins and logouts. It can be read using the command
who /var/adm/wtmp or the command last.
Transition Statement — Now that we've looked at the 'big picture' of what happens when
we log in, let's look further at three of the files listed on this visual - /etc/profile,
/etc/environment and $HOME/.profile.
Uempty
User Initialization Process
LOGIN
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Users
Groups
Passwords
Login Controls
Roles
PKI
LDAP
Notes:
Users
This option is used to add users to the system, delete existing users and change the
characteristics of existing users.
Groups
This option is used to add groups to the system, delete groups and change the
characteristics of existing groups.
Uempty Passwords
This option is used to change the password for a user. It is also required when setting
up a new user or when a user has forgotten their password.
Login Controls
This option provides functions to restrict access for a user account or on a particular
terminal.
Roles
This option sets up user roles. User roles allow root to give authority to an ordinary user
to perform a portion of root's functions.
PKI
PKI stands for X.509 Public Key Infrastructure certificates. This option is used to
authenticate users using certificates and to associate certificates with processes as
proof of a user’s identity.
LDAP
LDAP stands for Light Directory Access Protocol. It provides a way to centrally
administer common configuration information for many platforms in a networked
environment. A common use of LDAP is the central administration of user
authentication. The SMIT option here allows us to configure this platform as either an
LDAP client or an LDAP server.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the SMIT menu panel for security and users and explain each option.
Details — Point out that AIX 5L implemented login controls. This option will also update
fields in the /etc/security/user and /etc/security/login.cfg files.
In this unit, we will discuss the options Users, Groups, and Passwords. In the machine
exercise, students may choose to explore Login Controls on their own.
The Web-based System Manager fastpaths were made unavailable in AIX 5L. For more
information, see the Web-based System Manager Administration Guide.
The following “problem report” was included in a previous revision of this course. It has
been retained (without modification) in the current revision for completeness, but it has
been indented to distinguish it from the surrounding text.
For instructor use only: Prior to AIX 5L, based on testing and information from the IBM
Support Center, the Roles option did not appear to work as documented. For example,
if a user is added to the ManageShutdown role, they are still unable to shut down the
system - they must first be added to the shutdown group.
Some of the roles provide limited function. For example, if a user is added to the
ManageBasicPasswords or ManageAllPasswds roles, they will be able to execute
the pwdadm command to change the passwords of other users. Placing a user in the
ManageAllPasswds role allows them to change root's password as well! They are
able to do all this without being in the security group.
The ManageBackup and ManageBackupRestore roles allow the user to run the
backup command only, but not the backup command with the find command.
In other words, the roles did not work as documented. This issue was reported to the
Support Center. At the time this course was updated, we were not able to determine if
this issue was resolved in AIX 5L. As a result, it is suggested to not spend much time on
the concept of roles in this class. The instructor will need to handle this issue
accordingly.
Additional Information —
Transition Statement — We will next look at the SMIT menus used to manage users.
Uempty
SMIT Users
# smit users
Users
Add a User
Change a User's Password
Change / Show Characteristics of a User
Lock / Unlock a User's Account
Reset User's Failed Login Count
Remove a User
List All Users
Notes:
Add a User
Add user accounts.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Remove a User
Removes the user account, but not files owned by that user.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Example:
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Illustrate the result of using the SMIT list users option.
Details — This can be run from SMIT (smit lsuser) or by invoking the high-level
command lsuser.
SMIT does not provide much flexibility and responds in a fixed format, but with the lsuser
command, it is possible to extract more information from the system regarding a specific
user.
The keyword “ALL” represents all users on the system.
Additional Information — The lsuser command now has an additional flag (-R), which
can be use to specify an alternative Identification and Authentication mechanism. This flag
is not included in the simplified syntax shown on the visual.
Transition Statement — We shall now see how we can add a user to the system.
Uempty
Add a User to the System
# smit mkuser
Add a User
...
[Entry Fields]
* User NAME [ ]
User ID [ ] #
ADMINISTRATIVE USER? false +
Primary GROUP [ ] +
Group SET [ ] +
ADMINISTRATIVE GROUPS [ ] +
ROLES [ ] +
Another user can SU TO USER? true +
SU GROUPS [ALL] +
HOME directory [ ]
Initial PROGRAM [ ]
User INFORMATION [ ]
EXPIRATION date (MMDDhhmmyy) [0]
Is this user ACCOUNT LOCKED? false +
[MORE ...37]
...
Notes:
User name
The only value that must be specified is the user name. Traditionally, this name was
restricted to 8 characters in length. Beginning with AIX 5L V5.3, this limit can be
changed to allow names as long as 255 characters. The limit is modified in the
Change/Show Attributes of the Operating System panel (smit chsys).
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Setting a password
When a new user is created, the ID is disabled (an asterisk “*” is placed in the password
field of the /etc/passwd file). To enable the ID, a password must be set with the
Change a User's Password option or either the passwd or pwdadm command.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to add a user to the system and detail what information is required.
Details — There are many attributes that can be assigned to a user account, but the only
mandatory item of information is the user name.
There will be defaults for all the others.
Mention that what we are displaying is by no means the entire list of attributes that can be
set. As indicated there are more than 30 additional lines. The important attributes which
follow are the password restriction fields, such as password maximum age, minimum
length, minimum repeated characters and so forth.
The menu item ROLES is shown for AIX V4.2 and later.
The menu item EXPIRATION date is Year 2000 enabled, that is, it supports up to year
2037.
Additional Information — The new AIX 5L V5.3 ability to change the maximum length of
the user names should be used with caution. If you increase it and later change your mind,
you will have to replace all long names with shorter names within the limit, or those users
will not be able to log onto the system. You also need to be concerned with compatibility
between systems for any situations where the user name is matched. It should also be
noted that the change in maximum length does not take effect until reboot.
Transition Statement — What if you wish to change an attribute after you have set the
user up?
Uempty
Change / Show Characteristics of a User
# smit chuser
Change / Show Characteristics of a User
...
[Entry Fields]
* User NAME george
User ID [206] #
ADMINISTRATIVE USER? false +
Primary GROUP [staff ] +
Group SET [staff,security] +
ADMINISTRATIVE GROUPS [ ] +
ROLES [ ] +
Another user can SU TO USER? true +
SU GROUPS [ALL] +
HOME directory [/home/george ]
Initial PROGRAM [/usr/bin/ksh ]
User INFORMATION [ ]
EXPIRATION date (MMDDhhmmyy) [0]
Is this user ACCOUNT LOCKED? false +
[MORE ...37]
...
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# rm -r /home/team01
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to remove a user from the system.
Details — There are two ways to remove a user from the system:
• Temporarily, by locking the user's account
• Permanently, by removing all information about the user from the system
As always, these actions are best performed in SMIT.
Additional Information — Before the files that belonged to the ex-user can be used by
anyone, they have to be chown'ed to another user ID.
Transition Statement — Having seen how users are created, changed and removed, we
now will look at passwords.
Uempty
Passwords
• A new user ID cannot be used until a password is
assigned
• There are two commands available for making password
changes:
# passwd [username]
# pwdadm username
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
A series of steps that can be used to recover if you forget the root password are given
on this visual.
Step 1
First, you must boot your machine from media other than its normal hard drive. Either
an installation CD or a mksysb tape works just fine. Remember to invoke the service
boot list, usually by pressing F5 while your machine is booting.
Uempty Step 2
You will need to define your system console and select a language. Then the
Installation and Maintenance menu will be displayed. Be certain to select option 3,
Start Maintenance Mode for System Recovery. If you select option 1 or 2, you are
reinstalling your operating system.
Step 3
Select the options required to activate the root volume group and start a shell. This gets
you access to rootvg without any passwords.
Step 4
Once you get the # prompt, use the passwd command as you normally would to create
a new root password.
Step 5
Enter the command # sync ; sync. This ensures that the memory buffer is written to
disk. In other words, it ensures that the new root password is saved to disk.
Step 6
Reboot your system. The command shutdown -Fr is a good way to accomplish this.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to retrieve root's password if you have forgotten it.
Details — Students need to understand that in maintenance mode, an ID is not required.
Thus, we are able to execute the passwd command to change root's password.
Be sure to stress the importance of physically protecting the machine. Anyone with
physical access to the machine and bootable media can gain access to root. It is also
extremely important to run the sync commands before rebooting, otherwise your changes
will not be flushed out to disk, and you will probably have the same problem again.
Additional Information — On some systems it is possible that the passwd command does
not work in maintenance mode. If this is the case, while in maintenance mode, instead edit
the /etc/security/passwd file and delete the encrypted password.
Transition Statement — Let's see how groups can be set up.
Uempty
SMIT Groups
# smit groups
Groups
Notes:
Purpose of groups
The purpose of groups is to give a common set of users the ability to share files. The
access is controlled using the group set of permission bits.
Predefined groups
There are a number of predefined groups on AIX systems, like the system group
(which is root's group) and the staff group (which contains the ordinary users).
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the functions available under the Groups SMIT menu option.
Details — Before creating groups, you should carefully plan how you want to organize your
users. This will save you time and headaches rather than trying to create groups on the fly.
Additional Information —
Transition Statement — We will start by looking at the groups that already exist on a
system.
Uempty
List All Groups
The lsgroup command:
lsgroup [-c | -f] [-a attribute …] {ALL | groupname …}
Example:
# lsgroup ALL
system id=0 admin=true users=root,test2 registry=compat
staff id=1 admin=false users=ipsec,team01,team02,team03,
team04,team05,test1,daemon registry=compat
bin id=2 admin=true users=root,bin registry=compat
sys id=3 admin=true users=root,bin,sys registry=compat
adm id=4 admin=true users=bin,adm registry=compat
uucp id=5 admin=true users=uucp,nuucp registry=compat
...
ipsec id=200 admin=false users= registry=compat
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to find out about the groups on the system.
Details — Like the SMIT lsuser option, the SMIT lsgroup option provides output in a
fixed format. The lsgroup command is more flexible.
Additional Information — Like the lsuser command, lsgroup now has a flag (-R), which
can be use to specify an alternative Identification and Authentication mechanism. See the
entry for lsgroup in the AIX 5L Version 5.3 Commands Reference (or the corresponding
man page) for information regarding this and other lsgroup flags.
If users want to find out what groups they belong to, they can invoke the groups command.
Their current primary group will be the first one listed in the output.
A user can belong to up to 32 groups.
Transition Statement — We shall now see how a group can be added to the system.
Uempty
Add Groups
# smit mkgroup
Add a Group
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Group NAME [support]
ADMINISTRATIVE group? false +
Group ID [300] #
USER list [fred,barney] +
ADMINISTRATOR list [fred] +
Projects [ ] +
Notes:
The -a option
The mkgroup -a option is used to indicate that the new group is to be an administrative
group. Only the root user can add administrative groups to the system.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The -A option
The -A option makes the invoker of the mkgroup command the group administrator.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Group attributes
The group attributes are:
- Group ID (id=groupid). It is not advisable to change the group ID, but it is
occasionally done immediately after a group has been created to match the ID of a
previously deleted group, or a specific group ID needed for a particular software
package.
- ADMINISTRATIVE group? (admin=true|false). Only the root user can change a
group to be an administrative group or make changes to an existing administrative
group.
Uempty - USER list (users=usernames). This is a comma separated list of the names of all
the members of the group. The group may be their primary group or an additional
one.
- ADMINISTRATOR list (adms=adminnames). This is the list of group administrators.
- Projects (projects=projectnames). As previously mentioned, this attribute was
added to support the Advanced Accounting subsystem.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how groups can be changed or removed.
Details — Discussion Items - What conditions must be satisfied in order for the rmgroup
command to work?
Answer: There must not be any users whose primary group is the one being deleted.
Additional Information —
Transition Statement — After you have set up users and groups on the system, it is
sometimes necessary to communicate information to the user community.
Uempty
Message of the Day
• The file /etc/motd contains text that is displayed every time
a user logs in
• This file should only contain information necessary for the
users to see
• If the $HOME/.hushlogin file exists in a user's home
directory, then the contents of the /etc/motd file are not
displayed to that user
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show one of the ways that information about the system can reach the user.
Details — The motd file should not be used to display messages to deter intruders. (By the
time intruders read the message, they are already in the system!) These messages should
be written into the /etc/security/login.cfg file instead, in the herald for a port.
Additional Information — Even though users can add a .hushlogin file, administrator can
remove them very easily using the find command: find / -name '.hushlogin' -exec
rm {} \;
If you need to make sure every user sees your message, make sure you remove the
.hushlogin.
You may want to ask the students how they could handle removing the .hushlogin files
and see if they can come up with the find command.
Transition Statement — Let's work on an exercise next. We’ll do the first part of this
exercise now and the rest of the exercise later.
Uempty
Exercise 17: User Administration (Parts 1-5)
Notes:
Introduction
This lab gives you an opportunity to expand your knowledge of user administration. You
add users and groups and review many of the user characteristics.
The exercise can be found in your Student Exercise Guide.
Be sure to only do Parts 1-5. You will be doing Parts 6-7 at the end of this unit.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the User Administration exercise.
Details — Be sure to tell the students to only do Parts 1-5. They will be doing Parts 6-7 at
the end of this unit.
Additional Information —
Transition Statement — Let’s move on to Security Files, the next topic in this unit.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Security Files
• Files used to contain user attributes and control access:
– /etc/passwd Valid users (not passwords)
– /etc/group Valid groups
Notes:
Introduction
The security on the system is controlled by a number of ASCII files. Key files are listed
on the visual and briefly described below.
/etc/passwd
The /etc/passwd file lists the valid users, and the user ID, primary group, home
directory, and default login shell for each of these users.
/etc/group
The /etc/group file lists the valid groups, their group IDs, and members.
/etc/security/passwd
/etc/security/passwd contains the encrypted password and update information for
users.
/etc/security/user
/etc/security/user contains extended user attributes.
/etc/security/group
/etc/security/group contains extended group attributes.
/etc/security/limits
/etc/security/limits contains process resource limits for users.
/etc/security/environ
/etc/security/environ contains environment variables for users. This file is not often
used.
/etc/security/login.cfg
/etc/security/login.cfg is a configuration file for the login program. This file contains
security enhancements that limit the logins on a port, for example, the number of login
attempts and the valid login programs (shells).
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce some of the primary files used to hold user, group and security
information.
Details — This page provides an introduction to the primary files that hold user, group and
security information. This page is meant as an introduction. Details on most of the files
listed will be covered on the following pages.
Most UNIX systems have /etc/passwd and /etc/group. AIX uses the /etc/security
directory as a way to provide additional security for additional user and group information.
The /etc/security directory is not standard on all UNIX operating systems.
Additional Information —
Transition Statement — We will now take a look through some of the files that are
involved in the security of your system.
Uempty
/etc/passwd File
# cat /etc/passwd
root:!:0:0::/:/bin/ksh
daemon:!:1:1::/etc:
bin:!:2:2::/bin:
sys:!:3:3::/usr/sys:
adm:!:4:4::/var/adm:
uucp:!:5:5::/usr/lib/uucp:
guest:!:100:100::/home/guest:
nobody:!:4294967294:4294967294::/:
lpd:!:9:4294967294::/:
john:!:200:0:X7560 5th floor:/home/john:/usr/bin/ksh
bill:*:201:1::/home/bill:/usr/bin/ksh
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-93
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
/etc/security/passwd File
# cat /etc/security/passwd
root:
password = 92t.mzJBjlfbY
lastupdate = 885485990
flags =
daemon:
password = *
bin:
password = *
...
john:
password = q/gD6q.ss21x.
lastupdate = 884801337
flags = ADMCHG,ADMIN,NOCHECK
Notes:
Index files
As previously mentioned, in AIX, additional files can be created to be used as index files
for /etc/security/passwd and some related files. These index files provide for better
performance during the login process. These indexes are created using the mkpasswd
command.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-95
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the file containing the security attributes for users.
Details — This file contains the actual password for each user.
In AIX, it is recommended that this file not be updated directly.
Additional Information —
Transition Statement — The /etc/security/passwd file contains the actual password
string (encrypted). We will now look at where other user attributes are set.
Uempty
/etc/security/user File (1 of 2)
# cat /etc/security/user
default:
admin = false
login = true
su = true
daemon = true
rlogin = true
sugroups = ALL
admgroups =
ttys = ALL
auth1 = SYSTEM
auth2 = NONE
tpath = nosak
umask = 022
expires = 0
...
Notes:
admin
Defines the administrative status of the user. Possible value: true or false.
login
Defines whether a user can login. Possible values: true or false.
su
Defines whether other users can switch to this user account. The su command supports
this attribute. Possible values: true or false.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-97
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
daemon
Defines whether the user can execute programs using the system resource controller
(SRC). Possible values: true or false.
rlogin
Defines whether the user account can be accessed by remote logins. Commands
rlogin and telnet support this attribute. Possible values: true or false.
sugroups
Defines which groups can switch to this user account. Alternatively, you may explicitly
deny groups by preceding the group name with a ! character. Possible values: A list of
valid groups separated by commas, ALL or *
admgroups
Lists the groups that a user administers. The value is a comma-separated list of valid
group names.
ttys
Defines which terminals can access the user account. Alternatively you may explicitly
deny terminals by preceding the terminal name with the ! character. Possible values:
List of device paths separates by commas, ALL or *
auth1
Defines the primary authentication method for a user. The commands login, telnet,
rlogin and su support these authentication methods.
auth2
Defines the secondary authentication methods for a user. It is not a requirement to pass
this method to login.
tpath
Defines the user's trusted path characteristics. Possible values: nosak, notsh, always
or on. (For more information refer to the online documentation.)
umask
Defines the default umask for the user. Possible values: 3-digit octal value.
Uempty expires
Defines the expiration time for the user account. Possible values: a valid date in the
form MMDDHHMMYY or 0. If 0, the account does not expire. The 'YY' supports the last
two digits of the years 1939 to 2038. If 0101000070 then the account is disabled.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-99
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the location of most user attributes and demonstrate how the default can
be changed.
Details — This visual, and the following one, show the file containing the user attributes.
The default stanza contains values that all users will inherit unless their own stanza
overrides it.
There are also stanzas in this file for each configured user on the system.
The file /etc/security/user contains a lengthy comment section at the start of the file, which
amply documents what flags there are and the acceptable values for these. Refer to the file
and the student notes for further information.
You may also want to mention that the expires field supports up to the year 2038 (that is,
AIX 5L V5.1 and later versions are Year 2000 enabled).
Additional Information —
Transition Statement — We will now look at the second part of this file.
Uempty
/etc/security/user File (2 of 2)
default
...
SYSTEM = "compat"
logintimes =
pwdwarntime = 0
account_locked = false
loginretries = 0
histexpire = 0
histsize = 0
minage = 0
maxage = 0
maxexpired = -1
minalpha = 0
minother = 0
minlen = 0
mindiff = 0
maxrepeats = 8
dictionlist =
pwdchecks =
© Copyright IBM Corporation 2005
Notes:
SYSTEM
This attribute can be used to describe multiple or alternate authentication methods the
user must use successfully before gaining access to the system. Possible tokens are:
• files Allows only local users access to the system
• compat The normal login procedure and therefore allows local and NIS users
access to the system
• DCE The Distributed Computing Environment authentication
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-101
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
logintimes
Defines the times a user can login. The value is a comma separated list of items as
follows:
[!][MMdd[-MMdd]]:hhmm-hhmm
or
[!]MMdd[-MMdd][:hhmm-hhmm]
or
[!][w[-w]]:hhmm-hhmm
or
[!]w[-w][:hhmm-hhmm]
where MM is a month number (00=January, 11-December), dd is the day on the month,
hh is the hour of the day (00 - 23), mm is the minute of the hour, and w is the day of the
week (0=Sunday, 6=Saturday).
pwdwarntime
The number of days before a forced password change that a warning is given to the
user informing them of the impending password change. Possible values: a positive
integer or 0 to disable this feature.
account_locked
Defines whether the account is locked. Locked accounts cannot be used for login or su.
Possible values: true or false.
loginretries
The number of invalid login attempts before a user is not allowed to login. Possible
values: a positive integer or 0 to disable this feature.
histexpire
Defines the period of time in weeks that a user will not be able to reuse a password.
Possible values: an integer value between 0 and 260. 26 (approximately 6 months) is
the recommended value.
histsize
Defines the number of previous passwords which cannot be reused. Possible values:
an integer between 0 and 50.
Uempty minage
Defines the minimum number of weeks between password changes. Default is 0.
Range: 0 to 52.
maxage
Defines the maximum number of weeks a password is valid. The default is 0, which is
equivalent to unlimited. Range: 0 to 52.
maxexpired
Defines the maximum number of weeks after maxage that an expired password can be
changed by a user. The default is -1, which is equivalent to unlimited. Range: -1 to 52.
maxage must be greater than 0 for maxexpired to be enforced. (root is exempt from
maxexpired).
minalpha
Defines the minimum number of alphabetic characters in a password. The default is 0.
Range: 0 to 8.
minother
Defines the minimum number of non-alphabetic characters in a password. The default
is 0. Range: 0 to 8.
minlen
Defines the minimum length of a password. The default is 0. Range: 0 to 8. Note that
the minimum length of a password is determined by minlen and/or "minalpha +
minother", whichever is greater. "minalpha + minother" should never be greater than
8. If "minalpha + minother" is greater than 8, then minother is reduced to "8 -
minalpha".
mindiff
Defines the minimum number of characters in the new password that were not in the old
password. The default is 0. Range: 0 to 8.
maxrepeats
Defines the maximum number of times a given character can appear in a password.
The default is 8, which is equivalent to unlimited. Range: 0 to 8.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-103
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
dictionlist
Defines the password dictionaries used when checking new passwords. The format is a
comma separated list of absolute path names to dictionary files. A dictionary file
contains one word per line where each word has no leading or trailing white space.
Words should only contain 7 bit ASCII characters. All dictionary files and directories
should be write protected from everyone except root. The default is valueless which is
equivalent to no dictionary checking.
pwdchecks
Defines external password restriction methods used when checking new passwords.
The format is a comma separated list of absolute path names to methods or method
path names relative to /usr/lib. A password restriction method is a program module that
is loaded by the password restrictions code at run time. All password restriction
methods and directories should be write protected from everyone except root. The
default is valueless, which is equivalent to no external password restriction methods.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-105
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Group Files
# more /etc/group
system:!:0:root,john
staff:!:john
bin:!:2:root,bin
sys:!:3:root,bin,sys
...
usr:!:100:guest
accounts:!:200:john
...
# more /etc/security/group
system:
admin=true
staff:
admin=false
accounts:
admin=false
adms=john
projects=system
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-107
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Having seen the user security files, we will now look at the group files.
Details — The group files are divided, like the user files, into the world-readable
/etc/group and the “shadow” /etc/security/group files.
In the example, only a small portion of both files are shown. In the example, /etc/group
also shows a group called accounts. This is a group that was added to the system by the
system administrator. All other groups in this example come with the AIX operating system.
In the example, /etc/security/group shows system and staff. These groups come
standard with AIX. The accounts group has been added by the system administrator. john
has the ability to add and delete other system users from this group.
Ask a question here, as a follow-on from the password question, and that is: “Is there
anything special in these files?”
Answer: The user john is a member of both the system group and the accounts group
where he is an administrator.
Is this a good idea? Discuss.
You might be asked about the ! and whether groups also have passwords set. The
answer is no. Some other UNIX operating systems use this field, but in AIX, you will always
see the !.
Additional Information — Once again in AIX 5L V5.3, there is the new group attribute of
projects. This relates to the previous discussion on the Add a Group SMIT panel.
Transition Statement — Let's look at the /etc/security/login.cfg file.
Uempty
/etc/security/login.cfg File
default:
herald =“Authorized use only.\n\rlogin:"
logintimes =
logindisable = 0
logininterval = 0
loginreenable = 0
logindelay = 0
pwdprompt = "Password: "
usernameecho = false
Notes:
herald
Specifies the initial message to be printed out when getty or login prompts for a login
name. This value is a string that is written out to the login port. If the herald is not
specified, then the default herald is obtained from the message catalog associated with
the language set in /etc/environment.
logintimes
Defines the times a user can use this port to login.
logindisable
Number of unsuccessful login attempts before this port is locked. Use this in
conjunction with logininterval.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-109
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
logininterval
The number of seconds during which logindisable unsuccessful attempts must occur
for a port to be locked.
loginreenable
The number of minutes after a port is locked that it automatically unlocked.
logindelay
The delay in seconds between unsuccessful login attempts. This delay is multiplied by
the number of unsuccessful logins - that is, if the value is two, then the delay between
unsuccessful logins is two seconds, then four seconds, then six seconds and so forth.
pwdprompt
Defines the password prompt message printed when requesting password input. The
value is a character string.
usernameecho
Defines whether the user name should be echoed on a port. If true (this is the default)
the user name echo is enabled. If false, user name echo is disabled. The user name is
not echoed at the login prompt and is masked out of security-related messages.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-111
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-113
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how consistency in the security files can be maintained.
Details — With all the information that is spread over such a number of files, it becomes
necessary sometimes to perform sanity checks on these files.
In the normal run of things, this should be unnecessary since SMIT will maintain
consistency among the files. However, if “traditional” UNIX administration methods are
employed on AIX (or/and SYSV.4 UNIX), then these files can get out of sync.
In order to remedy this, there are several utilities provided to check and update or warn of
these inconsistencies.
Great care should be used when running these as they have options that fix problems but
do not warn the administrator that a problem existed.
The flags (also given in the student notes) are:
-n Reports errors but does not fix them
-p Fixes errors but does not report them!!!
-t Reports errors and asks if they should be fixed
-y Fixes errors and reports them!!!
Additional Information —
Transition Statement — Let's talk about a couple of security features available on the PCI
RS/6000.
Uempty
System Management Services
Utilities
PASSWORD
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-115
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to change the passwords on the RS/6000.
Details — Explain that, to get to the password screen, you must boot the SMS programs,
select Utilities and then select Password.
Additional Information — In order to set the privileged password, a jumper must be
removed from the system board. Once this is done, then the password can be set in SMS.
Transition Statement — Let's see the details of how to set the passwords.
Uempty
PCI RS/6000 Passwords
Power On
Privileged
Entry Remove
Exit
Notes:
Power-on password
You can use any combination of up to eight characters (A-Z, a-z, and 9-0). After you set
a power-on password, you are prompted to enter it each time you power on the system.
Before you can use the system, you must type the correct password and press the
Enter key.
When you enter the correct password, the system is unlocked and resumes normal
operations. If you enter the wrong password, you are prompted to enter the correct one.
After three incorrect entries, you must power off the system and start again.
A power-on password can be set only after system power has been turned off and then
on again. You cannot set a power-on password after doing a warm system startup.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-117
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-119
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Security
Security
Policy
Policyand
and
Setup
Setup
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-121
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint (1 of 2)
1. What are the benefits of using the su command to switch
user to root over logging in as root?
_____________________________________________________
_____________________________________________________
2. Why is a umask of 027 recommended?
_____________________________________________________
_____________________________________________________
3. As a member of the security group, which password
command would you use?
__________________________________________________
4. Which password change command does SMIT use?
__________________________________________________
5. True or False? When you delete a user from the system, all
the user's files and directories are also deleted.
Notes:
Checkpoint Solutions (1 of 2)
1. What are the benefits of using the su command to switch user to
root over logging in as root?
A log (which can be monitored) of all users executing the su
command is kept in the sulog.
2. Why is a umask of 027 recommended?
This value removes all permission bits for the “others” category,
which enhances security.
3. As a member of the security group, which password command
would you use?
pwdadm (This command does not prompt for the root password
or the old password of the user whose password is being
changed.)
4. Which password change command does SMIT use?
passwd
5. True or False? When you delete a user from the system, all the
user's files and directories are also deleted.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — This checkpoint has two parts.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-123
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint (2 of 2)
6. If an ordinary user forgets their password, can the system
administrator find out by querying the system as to what the user's
password was set to? _______ Why? ___________________
_________________________________________________
7. Password restrictions are set in which of the following files?
a. /etc/passwd
b. /etc/security/passwd
c. /etc/security/restrictions
d. /etc/security/user
8. Which of the following statements are true?
a. A user can only belong to one group
b. A member of the security group can administer user accounts
c. An admin user is a user whose account cannot be administered
by any member of the security group (except root)
d. The chmod g+s command sets the SUID permission of a file
e. The root user, commonly known as the superuser has UID=0
and GID=0
© Copyright IBM Corporation 2005
Notes:
Checkpoint Solutions (2 of 2)
6. If an ordinary user forgets their password, can the system
administrator find out by querying the system as to what the user's
password was set to? No, because the passwords are held in
encrypted format, so even the system administrator cannot tell what
the password was set to.
7. Password restrictions are set in which of the following files?
a. /etc/passwd
b. /etc/security/passwd
c. /etc/security/restrictions
d. /etc/security/user
8. Which of the following statements are true?
a. A user can only belong to one group
b. A member of the security group can administer user accounts
c. An admin user is a user whose account cannot be administered
by any member of the security group (except root)
d. The chmod g+s command sets the SUID permission of a file
e. The root user, commonly known as the superuser has UID=0
and GID=0
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Let’s complete the exercise we worked on earlier.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-125
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
This lab gives you an opportunity to expand your knowledge of user administration. You
will examine the security set up and customize the login herald.
The exercise can be found in your Student Exercises Guide.
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-127
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
• User and groups can be added and deleted from the system
by using SMIT or by using high level commands
• Passwords must be set for all users using either pwdadm
or passwd
• Administrative users and groups can only be administered
by root
• Every user must be in at least one group
• Certain groups give users additional privileges
• Security files are located in ASCII text files in the /etc and
/etc/security directories
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 15. Security and User Administration 15-129
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
References
SC23-4888 AIX 5L Version 5.3 Commands Reference,
Volume 1, a-c
SC23-4895 AIX 5L Version 5.3 Files Reference
Unit Objectives
Notes:
• Starts:
– crontab command events
(regularly scheduled jobs)
– at command events
(one time only execution at specified time)
– batch command events
(run when CPU load is low)
1 2:3 5
© Copyright IBM Corporation 2005
Notes:
Starting of cron
The cron process is usually started at system startup by /etc/inittab. It runs constantly
as a daemon. If killed, it is automatically restarted.
Instructor Notes:
Purpose — Explain what cron is, what it will do, and how it is configured.
Details — cron runs system tasks on the behalf of a user. The user can submit a task to
cron and then log out of the system, knowing that the task will still be run.
The output of these tasks handed over to cron must be handled in a special way.
(Redirection of output is sometimes used for such tasks. If no output redirection is used,
then cron will mail the output and the errors to the user.)
Additional Information —
Transition Statement — Let’s cover some key points regarding crontab files.
Uempty
crontab Files
• Used to start regularly occurring jobs
Notes:
Scheduling a job
The cron daemon starts processes at specified times. It can be used to run regularly
scheduled jobs using files in the /var/spool/cron/crontabs directory, or it can be used
to schedule a command for one-time-only execution using the at command.
...
#0 3 * * * /usr/sbin/skulker
#45 2 * * 0 /usr/lib/spell/compress
...
0 11 * * * /usr/bin/errclear -d S,O 30
0 12 * * * /usr/bin/errclear -d H 90
0 15 * * * /usr/lib/ras/dumpcheck >/dev/null 2>&1
...
Format of entries:
minute hour date-of-month month day-of-week command
Notes:
Instructor Notes:
Purpose — Explain the format of a crontab file.
Details — Cover that each field is separated by white space. Explain what each field
means. Each field can have multiple values separated by commas and ranges can be
specified with dashes.
All fields are compared using “and,” and all fields must be true before cron will execute the
line. There is an exception to this rule. If a numeric is specified in both the “date of the
month” field and the “day of the week” field, these two fields (and only these two fields) are
compared with an “or”. For example, if a user wanted to run a script on the first of the
month when the first falls on a Friday, the administrator may incorrectly set up the crontab
entry to look like this:
0 0 1 * 5 /usr/bin/newscript
The problem with this is although the first is specified correctly with the “1” and the day of
the week is specified correctly with the “5”, these two fields will be compared using “or”.
Therefore, it will run on the first of the month, AND it will run on Fridays because “the 1st”
OR Friday makes the condition true.
The crontab file does not provide the capability to accomplish the original goal. However,
you could achieve your objective by running a script every Friday and have the script check
to see if it is the first of the month before proceeding through the script. The logic needs to
be built into the script.
Additional Information — You should point out the skulker entry in the file since this was
discussed earlier in the course.
Transition Statement — Now that we know the format, let’s see how to change this file.
Uempty
Editing a crontab File
# crontab -e
• A safer method:
Notes:
# at now +2 mins
banner hello > /dev/tty3
<ctrl-d>
job user.time.a will be run at date
# batch
banner hello > /dev/tty3
<ctrl-d>
Notes:
Instructor Notes:
Purpose — Explain how to use the at and batch commands.
Details — Jobs entered using the at command are managed by the cron daemon.
Additional Information — The at command performs once-only tasks at a later time than
the present.
This can be used to schedule a task for a time when there will be no users on the system,
for example, at 3 am.
batch jobs are the same as running at -q b.
Transition Statement — We’ve discussed how to submit a task to at. We will now see
how these jobs can be cancelled.
Uempty
Controlling at Jobs
• To list at jobs:
at -l [user]
atq [user]
# at –l
root.1118077769.a Mon Jun 6 10:09:29 2005
root.1118078393.a Mon Jun 6 10:19:53 2005
test2.1118079063.a Mon Jun 6 10:31:03 2005
• To cancel an at job:
at -r job
atrm [job | user]
# at -r test2.1118079063.a
at file: test2.1118079063.a deleted
Notes:
Listing at jobs
To list at jobs use the at -l command or the atq command. The root user can look at
another user's at jobs by using the command atq <user>.
Removing at jobs
To cancel an at job use at -r or atrm followed by the job number. Use the command
atrm - (placing nothing after the - character) to cancel all of your jobs. The root user
can cancel all jobs for another user using atrm <user>.
Instructor Notes:
Purpose — Show how to view the at queue and to cancel jobs from it.
Details — The first portion of an at job number shows the user ID that entered the job.
Additional Information —
Transition Statement — Let's see what we should document.
Uempty
Documenting Scheduling
• Have a copy of each user's crontab file
• Have a copy of the /etc/inittab file
Scheduling Records
Notes:
Overview
It is important to have correct up to date information regarding your system, in case of
an unexpected system failure.
Maintain as much documentation as possible about all aspects of the system by
following the recommendations we have given throughout the course.
Instructor Notes:
Purpose — Describe two useful documentation ideas that can help maintain the
availability of a system.
Details — Explain the importance of having correct up to date information regarding the
system, in case of unexpected system failure.
Encourage the user to maintain as much documentation as possible about all aspects of
the system by following the recommendations we have given throughout the course.
Additional Information —
Transition Statement — Before we do the exercise for this unit, let's look at the
checkpoint questions.
Uempty
Checkpoint
1. True or False? The at.allow and at.deny files must be
used to specify which users are allowed and denied use
of the at command.
Notes:
Instructor Notes:
Purpose — Review and test understanding of what has been covered in this unit.
Details — A suggested approach is to give the students a few minutes to answer the
questions themselves and then go over the answers as a group. A suggested checkpoint
solution is given below:
Checkpoint Solutions
1. True or False? The at.allow and at.deny files must be
used to specify which users are allowed and denied use
of the at command.
False. Only one or the other of these files should be used.
Additional Information —
Transition Statement — Let’s move on to the exercise for this unit.
Uempty
Exercise 18: Scheduling
• Using at
• Using batch
• Using crontab files
Notes:
Introduction
This lab gives you the opportunity to schedule jobs using both at and crontab.
The exercise can be found in your Student Exercises Guide.
Instructor Notes:
Purpose — Introduce the exercise for this unit.
Details — Depending on the class, it might be a good idea to remind the students where
the instructions for the exercise are located.
Additional Information —
Transition Statement — Let’s summarize the key points we’ve covered in this unit.
Uempty
Unit Summary
Notes:
Instructor Notes:
Purpose — Summarize the key points covered in this unit.
Details —
Additional Information —
Transition Statement — We’ve reached the end of our scheduling unit.
References
GG24-3570 Printing for Fun and Profit Under AIX V5L
Online AIX 5L Version 5.3 System Management Guide:
Operating System and Devices
Online AIX 5L Version 5.3 Guide to Printers and Printing
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Describe the purpose and the benefits of a queuing system
• Identify the major components that are responsible for
processing a print request
• Add a printer queue and device
• Submit jobs for printing
• Manage jobs in the queue
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The visual gives an overview of the different approaches that can be taken to printing
under AIX 5L. In the next two visuals, System V printing will be compared to the
traditional AIX print subsystem. The remainder of this unit will focus on using the AIX
print subsystem.
Note: You can use either the AIX print subsystem or the System V print subsystem.
They will not run concurrently.
Uempty In this approach, you lose the ability to serialize (spool) print requests. Only one user
may print at a time. On the other hand, if a printer is being dedicated to one use, this
may be a good solution. Examples might be logging to a printer or printing checks.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — The purpose is to give an overview of printing under AIX 5L, putting System V
and AIX in context. We also give a little advertisement for Infoprint Manager.
Details — More detail is provided in the System V print subsystem appendix. If a student is
interested in this print subsystem, the appendix has all the details and an exercise if they
wish to test out the features.
Additional Information — There are several places later in this unit that mention a few
System V print commands that are in AIX V4.3.3. These notes have not been changed as
they are still true. AIX 5L now provides full support for the print subsystem.
Transition Statement — Now, lets look at the strengths of the AIX print subsystem.
Uempty
AIX Print Subsystem: Advantages
• Powerful and flexible printer drivers
• System management tools:
– Limits fields and options validation
– Easy printer customization
– Single step print device and queue creation
• Customizable spooling subsystem
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Compatibility
System administrators with experience in other UNIX variants that use System V
printing will find it easy to manage printing under AIX’s System V print subsystem.
Uempty Security
Controlling user access to printers can be an important issue. For example, you might
need to limit access to the printer used to print checks. System V printing includes
built-in capabilities for restricting user access to certain printers. Using the AIX print
subsystem, the backend program must be customized to restrict user access.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List advantages of System V print subsystem.
Details — In summary, the main advantages of System V has to do with compatibility. This
makes it easy for system administrators from other UNIX variants to transition to AIX and it
drives availability of support for a larger number of printers on AIX.
System V also adds forms support and better security.
Additional Information — Directory-enabled printing is supported beginning with
AIX 5L V5.2. System V printing on AIX uses LDAP (Lightweight Directory Access Protocol)
as the directory service.
A directory is an ordered list of objects, including details about each object. Obvious
examples are phone books or library card catalogs. Directories are a type of database.
They differ from other databases in that accesses are mostly reads, with only occasional
writes. Directory protocols are optimized to facilitate a high read environment.
Computer directories can be searched in many ways, making them a very powerful way to
store and manage information.
In the case of a printer directory, this might include searching for the name of a printer to
get its characteristics, searching for printers in a particular location, searching for printers
with particular features, and so forth. Directory enabled printing provides an easy way for
users to search for a printer that is close and has the features they require. If security or
other control features are made part of the directory, directory enabled printing facilitates
easier management by system administrators.
Transition Statement — Now, let’s look at traditional AIX printing and queues.
Uempty
Concepts of Queues
file1
Queue1
file1
file2
.
file2 .
file3
/dev/lp0
Queue2
file3
file4
file4
/dev/lp1
Notes:
Benefits of queues
The queues also give control to the system administrator over the queuing mechanism.
Therefore, the system administrator can perform tasks like cancelling jobs on queues,
changing priorities of jobs, and so forth.
A queue enables the sharing of resources in an ordered fashion.
The diagram above illustrates three important issues:
- One print queue can point to a number of printers (and it is the job of the qdaemon to
determine the next available printer to print on), for example, Queue1.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
lp lpr qprt
enq
copy of file (if requested)
Queue
Spool
monitors directory
qdaemon uses spool file
(if it exists)
starts
Backend Virtual Printer
(piobe) Definition
submits file to
printer
/dev/lp0
© Copyright IBM Corporation 2005
Notes:
Print request
Local printing is implemented through a queuing mechanism. The user can issue one of
the printer commands qprt, lp, lpr, or enq to submit a print job. Although a user can
use any one of these four commands, the true entry point to the spooler is the enq
command which is responsible for processing the job request, creating a job description
file (JDF) and notifying the qdaemon of the new job.
The qdaemon
The qdaemon process is running all of the time. The qdaemon maintains a list of all of the
defined queues and monitors the queues for newly submitted jobs. qdaemon tries to
process the job if the destination device is available, otherwise the job remains in the
queue and qdaemon tries again later.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain the flow of a print job using the queuing system.
Details — Review the flow of the queuing system as it is shown in the visual. The student
notes provide detailed information on what happens when a print request is made.
The student notes also refer to virtual printer definitions. This file pairs the attributes or
characteristics of a specific printer with the attributes of a specific data stream. For
example, if a printer supports both ASCII and PostScript data streams, you must create two
virtual printer definitions for the printer. These can be created using SMIT and are stored in
the /var/spool/lpd/pio/@local directory. A subdirectory called custom must hold an entry
for each virtual printer. SMIT will automatically place an entry in this directory for each
queue defined. The mkvirprt command can also be used to create a virtual printer.
Additional Information —
Transition Statement — Now that we have seen the major components, let's take a closer
look at the corresponding files and structures that are directly associated with the queuing
system.
Uempty
System Files Associated with Printing
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
qdaemon
• Manages queues
• Started in the /etc/inittab file
• Invokes the backend programs
• Optionally records accounting data
Notes:
qdaemon introduction
The qdaemon program schedules jobs that have been enqueued. It is a background
process that is usually started at system IPL via the startsrc command run from
/etc/inittab.
qdaemon is controlled by the /etc/qconfig file. /etc/qconfig contains a stanza for each
queue. The stanza identifies any queue management options and points to a queue
device stanza which identifies the destination printer, the formatting options, and the
backend program.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the functions of the qdaemon.
Details — qdaemon is a process that starts when you start your system and runs until you
shut your system down. It keeps track of print job requests and the printer. It is also the
parent to the backend process. It maintains queues of outstanding requests and sends
them to the proper device at the proper time. It is managed under the control of the SRC.
The proper way to start and stop it is through the SRC.
Additional Information —
Transition Statement — The queue-to-device relationships are held in the /etc/qconfig
file. Let's look at the format of this file.
Uempty
The /etc/qconfig File
lp0: * 1 queue pointing to 1 device
device = lp0dev
up = TRUE
discipline = fcfs
lp0dev:
file = /dev/lp0
backend = /usr/lib/lpd/piobe
header = group
trailer = never
feed = never
lpq: * 1 queue pointing to 2 devices
device = lpqdev1,lpqdev2
lpqdev1:
file = /dev/lp1
backend = /usr/lib/lpd/piobe
lpqdev2:
file = /dev/lp2
backend = /usr/lib/lpd/piobe
ps: * 2 queues pointing to 1 device
device = psdev
psdev:
file = /dev/lp3
backend = /usr/lib/lpd/piobe
asc:
device = ascdev
ascdev:
file = /dev/lp3
backend = /usr/lib/lpd/piobe
© Copyright IBM Corporation 2005
Notes:
Introduction
The /etc/qconfig file is an attribute file. Some stanzas in this file describe queues, and
other stanzas describe devices. Every queue stanza requires that one or more device
stanzas immediately follow it in the file.
This file is the key to customizing the queues. Although the file can be edited directly, it
is recommended that it be changed through high-level commands or via SMIT.
Queue stanza
This starts with the queue name, which can be up to 20 characters, followed by a colon.
The queue name is used by the person submitting a job to indicate the desired queue.
The first queue in the /etc/qconfig file is the default queue, which receives any job
requests submitted without a specific queue name.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Some of the attributes that can be found in the queue stanza include:
Attribute Definition Default Other
Identifies the symbolic name that refers to
device
the device stanza
discipline Defines the queue serving algorithm fcfs sjn
Identifies the file used to save print
acctfile false filename
accounting information
up Defines the state of the queue TRUE FALSE
Device stanza
The name of a device stanza is arbitrary and can be from 1 to 20 characters long. The
name is followed by a colon.
The attributes that can be found in the device stanza include:
Attribute Description Default Other
Identifies the special file where the output of
backend is to be redirected. FALSE
file FALSE
indicates no redirection and that the file
name is /dev/null.
Specifies the full path name of the backend,
backend optionally followed by the flags and
parameters to be passed to it.
both (used
Specifies the type of access the backend for modems
has to the file specified by the file field. or backends
access write
This field is ignored if the file field has the needing
value FALSE. read
capability)
Specifies whether a header page prints always
header never
before each job or group of jobs. group
Specifies whether a trailer page prints after always
trailer never
each job or group of jobs. group
Specifies either the number of separator
pages to print when the device becomes idle
feed never integer
or the value never, which indicates that the
backend is not to print separator pages.
Specifies whether the backend sends a
align form-feed control before starting the job if FALSE TRUE
the printer was idle.
Uempty The device stanza must contain an attribute that designates the backend program. The
function of the backend is to manage the printing of the actual job. It also produces the
final data stream that goes to the printer. The most common backend program for local
printing is piobe.
If different users desire different default printers, then the PRINTER variable can be set
up on a per user basis. The PRINTER variable should be set to the queue that the user
wishes to be their own default queue for example:
# PRINTER=ps ; export PRINTER
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Cover all the different relationships that queues and devices can have.
Details — The reason that it is recommended to use SMIT rather than editing the file
directly is mainly to keep the contents of /etc/qconfig consistent with the contents of the
ODM. For example if you use vi to remove an entire stanza of information from the file, the
ODM still has an entry for that printer and you will not be able to redefine that printer until
the ODM is in sync with the /etc/qconfig file.
A queue can have a one to one relationship, where there is one queue to one printer. Or, a
queue can have a one to many relationship, where there are lots of printers in the same
room and the job goes to the first available printer. There may be times when there are
multiple queues that support one printer giving each queue its own characteristics of
printing a job, which is referred to as the many-to-one relationship. This occurs when a
printer is capable of printing different types of output such as ASCII, PostScript and
graphics.
The discipline attribute defines the queue serving algorithm. The default value, fcfs,
means first-come-first-served. sjn means shortest job next.
Additional Information — How can you tell what the default queue is based on the
/etc/qconfig file? Answer: The first queue name specified is the default queue.
The LPDEST variable can also be set to define a user default queue. If both PRINTER and
LPDEST are set, LPDEST's value will be the value that is used.
Transition Statement — Let's look at how to define printers and print queues.
Uempty
Printer Menu
# smit spooler_choice
Print Spooling
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the main SMIT menu to manage print spooling.
Details —
Additional Information —
Transition Statement — Let’s configure a local print queue through SMIT.
Uempty
AIX Printer Menu
# smit spooler
AIX Print Spooling
Move cursor to desired item and press Enter.
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Other commands
To show current print subsystem: # switch.prt -d
To change current print subsystem, you can use either:
- # switch.prt -s AIX
- # switch.prt -d SystemV
To check if binaries are correct linked, you can use either:
- /usr/bin/lpstat --> /usr/aix/bin/lpstat
- /usr/bin/lpstat --> /usr/sysv/bin/lpstat
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Move cursor to desired item and press Enter.Use arrow keys to scroll.
#ATTACHMENT TYPE DESCRIPTION
local Printer Attached to Local Host
remote Printer Attached to Remote Host
xstation Printer Attached to Xstation
ascii Printer Attached to ASCII Terminal
hpJetDirect Network Printer (HP JetDirect)
file File (in /dev directory)
ibmNetPrinter IBM Network Printer
ibmNetColor IBM Network Color Printer
other User Defined Backend
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Printer Type
Move cursor to desired item and press Enter.
Bull
Canon
Dataproducts
Hewlett-Packard
IBM
Lexmark
OKI
Printronix
QMS
Texas Instruments
Other (select this if your printer is not listed above)
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Printer Type
[MORE...8]
ibm2391-2 IBM 2391 Plus printer (Model 2)
ibm3112 IBM 3112 Page Printer
ibm3116 IBM 3116 Page Printer
ibm3130 IBM 3130 LaserPrinter
ibm3812-2 IBM 3812 Model 2 Page Printer
ibm3816 IBM 3816 Page Printer
ibm4019 IBM 4019 LaserPrinter
ibm4029 IBM 4029 LaserPrinter
ibm4037 IBM 4037 LP printer
ibm4039 IBM 4039 LaserPrinter
[MORE...49]
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Printer Attachment
Printer Interface
Move cursor to desired item and press Enter.
parallel
rs232
rs422
Parent Adapter
Move cursor to desired item and press Enter.
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Remote Printing
host1 client1
lp1
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Client Authorization
# smit mkhostslpd
Add Print Access for a Remote Client
[Entry Fields]
* Name of REMOTE CLIENT [client1]
(Hostname or dotted decimal address)
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Start lpd
# smit mkitab_lpd
Start the Print Server Subsystem
[Entry Fields]
Start subsystem now, on system restart, or both [both] +
TRACE lpd daemon activity to syslog? [no] +
EXPORT directory containing print attributes? [no] +
Note:
Exporting this print server's directory
containing its print attributes will allow
print clients to mount the directory. The
clients can use this server's print attributes
to display and validate print job attributes
when starting print jobs destined for this
print server. Note that the Network File
System (NFS) program product must be installed
and running
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Move cursor to desired item and press Enter.Use arrow keys to scroll.
#ATTACHMENT TYPE DESCRIPTION
local Printer Attached to Local Host
remote Printer Attached to Remote Host
xstation Printer Attached to Xstation
ascii Printer Attached to ASCII Terminal
hpJetDirect Network Printer (HP JetDirect)
file File (in /dev directory)
ibmNetPrinter IBM Network Printer
ibmNetColor IBM Network Color Printer
other User Defined Backend
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
*Name of QUEUE to add [rq1]
*HOSTNAME of remote server [host1]
*Name of QUEUE on remote server [lp1]
Type of print spooler on remote server AIX Version 3 or 4 +
Backend TIME OUT period (minutes) [] #
Send control file first? no +
TO turn on debugging, specify output []
file pathname
DESCRIPTION of printer on remote server []
Notes:
Required input
Only three lines are required to complete the queue set up. You must name your local
(to the client) queue name. Then, provide the name of the printer server. Lastly, name
the queue on the print server.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Let's Review
1. True or false? The qdaemon is responsible for printing jobs.
________________________________________________
________________________________________________
________________________________________________
2. To set up remote printing, what daemons are needed and do
they run on the server, the client or both?
________________________________________________
________________________________________________
3. What does the up = TRUE indicate in the /etc/qconfig file?
________________________________________________
________________________________________________
4. What does discipline mean in reference to the
/etc/qconfig file? What are its possible values?
________________________________________________
________________________________________________
________________________________________________
© Copyright IBM Corporation 2005
Notes:
Additional Information —
Transition Statement — Let’s now look at how to submit print jobs.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
$ lp -d queuename filename
- OR-
Notes:
Introduction
There are three sets of commands for submitting, listing and cancelling print jobs. They
come from either System V, BSD or IBM versions of UNIX and are all available in AIX.
The commands have slightly different options.
Uempty Spooling
The commands lp and qprt both queue without spooling by default. Specify the -c
option if spooling is desired. The command lpr spools and queues by default. The -c
option will turn off spooling with lpr.
Multiple copies
To print multiple copies, with qprt use the -N # option, with lp use -n # option, and
with lpr use just a dash followed by the number of copies ( - # ).
The lp, lpr and qprt commands create a queue entry in /var/spool/lpd/qdir and
(depending upon the options specified) copy the file to be printed to the
/var/spool/qdaemon directory.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how to submit jobs to the printer.
Details — Explain the visual using the student notes. Do not explain every single option for
every command. Concentrate on the AIX command.
Note that qprt was chosen to be on the visual because it is the AIX command. lp was also
included because it illustrates that these commands use different options. lp is the most
popular printing command in UNIX. The student notes include a discussion on all the
available commands. Students should choose what will work best for them.
You may also want to mention the -j option which can be used with the enq and lpr
commands so that the job number will be displayed once the job has been submitted to
print. The lp command displays the job number by default. The qprt command uses the -j
option for another purpose.
Additional Information —
Transition Statement — Once you have submitted a job, you probably want to view where
in the queue your job is. Let's see how you can do this.
Uempty
Listing Jobs in a Queue
• To list jobs in a queue:
For example:
$ qchk
Queue Dev Status Job Files User PP % Blks Cp Rnk
ps lp0 DOWN
QUEUE 569 /etc/motd root 1 1 1
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
1. Printer Setup
2. Default Print Job Attributes
3. Accounting File
4. Queuing Discipline
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how the characteristics of the queue can be customized.
Details — You must select the queue name to which you wish to make the changes. Then,
select one of the options (the one that holds the attribute that you are trying to change).
Refer to the student notes in order to obtain a list of what is contained in each option.
The actual contents of each option will vary depending on the type of queue being
customized (for example, an ASCII queue vs. a PostScript queue).
Under Default Print Job Attributes => Job Processing Options..., some queues allow
you to specify the page number where printing should begin. This can be helpful if there is
a paper jam in the middle of printing a job. Bring the queue down and fix the jam. Then,
alter this value to indicate the page at which you want the print job to resume. Then,
change the value back to 1 for printing future jobs.
The queueing discipline will be covered in more detail shortly. If a student asks, the two
disciplines that can be chosen are either First Come First Serve or Shortest Job Next.
Additional Information —
Transition Statement — Let's see how we can remove a queue.
Uempty
Removing a Queue
# smit rmpq
Remove a Print Queue
[Entry Fields]
Print queue to remove ps:lp0
Local printer device /dev/lp0
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how queues can be deleted from the system.
Details — The last option on the screen asks whether the printer device definition should
be kept. This option will only appear if the queue being removed is the only queue defined
for a printer. Note that by default, it will be removed. (You may wish to keep the definition if
in the future you wish to add a new queue which uses the same printer.) If there were other
queues which were using the printer, the last option would not be present on the SMIT
screen. This option will remove the print queue from the system configuration.
Additional Information—
Transition Statement — Other management tasks can be carried out on queues. Let's
see what they are.
Uempty
Managing Queues
# smit pqmanage
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List the supported management tasks for queues through SMIT.
Details — The visual is fairly self explanatory. Point out that if a print queue is stopped,
print jobs can still be submitted to the queue. However, they will not be processed until the
queue is enabled.
If the system wide default printer is changed, this will have an effect for everyone other than
those who have set the PRINTER or LPDEST variable to their own personal choice.
We will look at the first three items on this menu. The last item is self-explanatory, so there
is no need to spend more time on it.
Be sure to point out that the last three tasks on this menu can only be performed by the
root user or a member of the printq group.
Additional Information —
Transition Statement — Let's see what the different queue statuses mean.
Uempty
Understanding Queue Status
Queue Dev Status Job Files User PP % Bks Cp Rnk
ps lp0 DOWN
QUEUED 1569 /etc/motd root 1 1 1
State Description
DEV_BUSY Printer is busy servicing other print requests
DEV_WAIT Queue is waiting for the printer
DOWN Queue is down and no jobs will be serviced
from this queue until it is brought up
OPR_WAIT The queue is waiting for operator intervention
QUEUED Job is queued and waiting
READY Everything is ready to receive a print request
RUNNING Print file is printing
UNKNOWN Problem with the queue - need to investigate
further to determine cause
© Copyright IBM Corporation 2005
Notes:
Introduction
The status of the queues and jobs can be displayed with qchk, lpstat or lpq. There are
a number of different status states that may be seen.
DEV_BUSY
This status can occur when more than one queue is defined to a print device and
another queue is currently using the print device. It could result when the qdaemon
attempts to use the printer port device and another application is currently using that
print device. Normal recovery: You have to wait until the queue or application has
released the print device, or kill the job or process that is using the printer port.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
DEV_WAIT
This status means that the queue is waiting on the printer because the printer is offline,
out of paper, jammed, or the cable is loose, bad or wired incorrectly. Normal recovery:
Check to see if the printer is offline, out of paper, jammed or loosely cabled. Sometimes
the jobs have to be removed from the queue before the problem can be corrected.
DOWN
This status is set when the device driver cannot communicate with the printer after
TIME OUT seconds (which can be set through SMIT). This variable indicates the
amount of time, in seconds, that the queuing system waits for a printer operation. If the
printer is off, the queue will go down. Also, the operator can bring down the queue
intentionally, which might be necessary for system maintenance. Normal recovery:
Correct the problem that has brought the queue down and then bring the queue up
again.
OPR_WAIT
This status is set when the backend program is waiting on the operator to change the
paper, change forms and so on. This is usually software related. Normal recovery:
Respond appropriately to the request that is made by the queuing system.
QUEUED
This status is set when a print file is queued and is waiting in line to be printed.
READY
This is the status of a queue when everything involved with the queue is ready to queue
and print a job.
RUNNING
This status occurs when a print file is printing.
UNKNOWN
This status occurs when a user creates a queue on a device file that another queue is
using and its status is DEV_WAIT. The queue cannot get a status from the printer
device when it is on hold. Normal recovery: Bring down the other queue or fix the
problem with the printer (paper out, jammed, offline and so on). Bring the new queue
down and then back up so that the queue will register as READY.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Enabling a queue
Occasionally, problems with printers can bring a queue down. Once the problem has
been fixed it can be brought back up with:
# enable <queuename>
Disabling a queue
Sometimes, you may wish to bring a queue down. This is recommended if any
maintenance is going to be performed on the printer. You can do this with either of the
commands:
- # disable <queuename>
- # enq -D -P <queuename>
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
[Entry Fields]
PRINT QUEUE containing job [ ] +
(required for remote jobs)
* Print JOB NUMBER [ ] +#
Notes:
Introduction
The qcan command cancels either a particular job number or all jobs in a print queue.
Normal users can only cancel their own jobs, whereas root can cancel any job.
Uempty Examples
To cancel job number 127 on whatever queue the job is on, you can use either of the
following two commands:
- # qcan -x 127
- # cancel 127
To cancel all jobs queued on printer lp0, you can use either of the following two
commands:
- # qcan -X -Plp0
- # cancel lp0
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — How to cancel a job in a queue.
Details — Point out that there are restrictions. As an ordinary user, you can only cancel
your own requests (which is a desirable thing!). However, root or a member of the printq
group can cancel any job from any queue.
Note the two examples in the student notes. The use of the -x option allows you to cancel
a specific job by its job number. An equivalent command to that shown in the student notes
is cancel 127. The use of the -X option allows you to cancel all jobs queued on a specific
printer. If a normal user uses this option, only the jobs that they submitted will be cancelled.
The qcan command can be used to cancel both local and remote jobs.
This command can also be used to cancel HELD jobs.
Additional Information — You may want to mention that a running job can only be
cancelled if all of it hasn't been sent to the printer. Today's printers all have buffers. Once
the print job has left the system it is outside the control of printer commands. The status
may show running but there won't be any way to cancel it. On some printers, it is possible
to power-off the printer as a way to clear the buffer. A large job that is bigger than the
printer buffer can be cancelled before it completes. Keep in mind that whatever is in the
printer buffer will still be printed.
Transition Statement — Let's see how the priority of print requests can be changed.
Uempty
Job Priority Example
# qchk -L
Queue Dev Status Job Name From To
______ ___ _______ Submitted Rnk Pri Blks Cp PP %
ps lp0 DOWN
QUEUED 569 /etc/qconfig root root
1/07/03 09:39:25
1 15 2 1
/etc/qconfig
# qpri -#570 -a 25
# qchk -L
Queue Dev Status Job Name From To
______ ___ ______ Submitted Rnk Pri Blks Cp PP %
ps lp0 DOWN
QUEUED 570 /etc/motd root root
1/07/03 09:40:15 1 25 1 1
/etc/motd
Notes:
Processing order
The discipline line in the /etc/qconfig file determines the order in which the printer
serves the requests in the queue. In the queue stanza, the discipline field can either
be set to fcfs (first-come-first-serve) or sjn (shortest-job-next). If there is no
discipline in the queue stanza, requests are serviced in fcfs order.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Example
The example in the visual shows that when print jobs are submitted they receive the
default priority of 15. The example shows how the qpri command can be used to
change the priority of job number 570 to 25. Use the qchk -L command to show the
new job priorities.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# qhld -#1493
# qchk
Queue Dev Status Job Files User PP% Blks Cp Rnk
ps lp0 DEV_BUSY
HELD 1493 /etc/qconfig root 1 1 1
# qhld -r -#1493
# qchk
Queue Dev Status Job Files User PP% Blks Cp Rnk
ps lp0 DEV_BUSY
QUEUED 1493 /etc/qconfig root 1 1 1
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# qchk -A
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
var
spool
lpd
qdaemon
qdir
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
NO YES
Check hardware Check software
Notes:
First step
If you experience problems trying to print, start by checking the simple things first.
The easiest test to perform is to cat a file and redirect standard output to the printer
device file. This by-passes the queuing system and helps to narrow the problem.
Check hardware
After redirecting a file to the print device, if it does not print, the problem is usually
hardware-related. Check to make sure the cables are attached securely. Make sure the
printer is ready to print (online). Make sure there is paper in the printer and there are no
paper jams.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how to troubleshoot printing problems.
Details — Cover the visual in detail.
Make sure the students understand why performing a cat to direct a file to the printer helps
to pinpoint the problem area.
When checking cables, if using serial connection, be sure the pins have not been bent or
broken.
Ask the students if /tmp or /var is full, what commands would be useful in determining what
is filling the file system?
Answer:
# df
# du -ax /tmp
# du -ax /var
Additional Information — When checking to see if qdaemon is running, make sure there is
only one qdaemon running. Having multiple qdaemons running is not a likely problem, but it
would cause a problem if it happened. If qdaemon is being used properly under SRC, it is
not likely that this problem would ever occur.
Transition Statement — Let's take a look at some checkpoint questions.
Uempty
Checkpoint (1 of 2)
1. True or False? One of the advantages of queues is that
each user can have a different default queue set up for them.
________________________________________________
2. True or False? The /etc/qconfig file is read by the backend
program to determine what the queue discipline is.
________________________________________________
3. True or False? All printer software is automatically installed
when you install the base operating system.
________________________________________________
4. What is the difference between these two commands?
# qprt -Pasc file1
# qprt -c -Pasc file1
________________________________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions (1 of 2)
1. True or False? One of the advantages of queues is that each
user can have a different default queue set up for them.
True. This can be accomplished using the PRINTER
environment variable.
2. True or False? The /etc/qconfig file is read by the backend
program to determine what the queue discipline is.
False. It is read by qdaemon.
3. True or False? All printer software is automatically installed
when you install the base operating system.
False. Only a handful of printer software is installed by default.
4. What is the difference between these two commands?
# qprt -Pasc file1
# qprt -c -Pasc file1
The -c flag produces a spool file.
Additional Information —
Transition Statement — Continue with more checkpoint questions.
Uempty
Checkpoint (2 of 2)
5. What three methods can be used to find out what the system
default queue is?
í
í
í
6. What users can bring print queues down?
_______________________________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-93
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions (2 of 2)
5. What three methods can be used to find out what the system
default queue is?
í First entry in /etc/qconfig file
í The output from the qchk command with no options
í The first queue listing from the lpstat command
6. What users can bring print queues down?
The root user or members of the printq group.
7. True or False? Once the queue is down, no more jobs can
be submitted to the printer.
False. Jobs can be submitted to the queue. However, they
will not be printed until the queue is brought up again.
8. Can users hold all their print jobs in a specific queue?
If so, how?
Yes, they can by only specifying a queue name and not
individual job numbers.
Additional Information —
Transition Statement — Now, let’s do an exercise.
Uempty
Exercise 19: Printers and Queues
Notes:
Introduction
This exercise gives you an opportunity to work with the AIX queuing system. If your
classroom does not have locally attached printers, your instructor needs to supply you
with local modification for this lab.
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-95
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details —
Additional Information —
Transition Statement — Summarize the unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 17. Printers and Queues 17-97
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — This is the end of this unit.
References
Online System Management Guide: Communications and
Networks
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• Define the basic TCP/IP terminology
• Configure TCP/IP for an Ethernet or Token-Ring
connection
• Use some of the standard TCP/IP facilities to:
– Log in to another system
– Transfer files
– Run commands
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
What Is TCP/IP?
• Transmission Control Protocol/Internet Protocol
• Software to enable different systems to exchange data over
a variety of types of network
• The way in which systems are connected and how data is
passed between them is transparent to the user
• TCP/IP is vendor-independent; development is overseen by
the Internet Architecture Board
Notes:
Networking architecture
TCP/IP is a networking architecture which defines a mechanism for cooperating
computers connected by some sort of network to exchange data. TCP/IP software has
been implemented across many platforms from mainframes to personal computers,
although it is most commonly associated with UNIX environments.
Protocols
TCP/IP is a set of protocols which define various aspects of how two computers on a
network may communicate with each other. A protocol is a set of rules which describe
the mechanisms and data structures involved. Using these definitions, vendors can
write software to implement the protocols for particular systems.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce TCP/IP.
Details — TCP/IP is another protocol stack.
As well-known alternatives, there are OSI and SNA. These also achieve communication
between computers.
The difference between these and TCP/IP is that TCP/IP is now the de facto standard
protocol for network communications across all platforms.
TCP/IP is available from many vendors on many platforms. Whatever the vendor or the
platform, the same level of functionality is provided.
TCP/IP has undergone some changes. The IP protocol that has typically been used is
IPV4. However, a new version of IP has been introduced, IPV6, (also known as IPng - next
generation). IPV6 is supported by AIX V4.3 and later. This version of IP will address the
current shortage of network and host addresses.
Additional Information — In spring of 1995, US Federal funding for the IAB was
discontinued.
Transition Statement — We have mentioned that most systems either already use
TCP/IP or could at least communicate with those that do use it. This is the so-called
Internet.
Uempty
An Internet
• A TCP/IP network is often called an internet.
A
gateway Serial gateway
Token
Ring modem modem
B C
D
FDDI
E
gateway gateway
X.25
F
Ethernet
Notes:
Introduction
TCP/IP works with many different types of networks from slow-speed serial type
connections to fast local area networks like Token-Ring or Ethernet or even faster
networks like FDDI (using fiber optics).
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Internet
An Internet is a term given to a number of TCP/IP networks connected together. An
Internet can be a combination of similar networks or heterogeneous networks. In an
Internet, data can be transferred transparently from one host to another without the
sending host needing to know the route taken or the type or number of connections
involved.
There are a number of public Internets worldwide, the largest of which is called The
Internet (or the connected Internet). The Internet consists of millions of connected
systems.
Host
A host is any computer attached to the network which has a TCP/IP address. This
includes machines of any size or functionality. For example, an X-Terminal is a host as
far as TCP/IP is concerned. Each host is given a unique name (for users) and address
(for software) so that it can be uniquely identified in the interconnection of networks.
Gateway
A host which has interfaces on multiple networks and the ability to route traffic from one
to another is called an IP Gateway or an IP Router. The ability to route between the
attached networks is an important factor. A server which has interfaces on multiple
networks for the purpose of improved availability or performance, is called a
multihomed host or multihomed server. It is not recommended to configure a
multihomed server to be router because the extra load of the routing will impact the
server performance.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Uempty Some network utilities will work with both the notations, while others (rsh, rlogin, rcp)
must know of the textual form in order to work.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Explain how computer systems are identified in an Internet.
Details — The TCP/IP address used in the visual is an example of an IPV4 address. This
is the address format used by most companies at this time. IPV6 supports a 128-bit
address, which looks much different. For example, FE80::1:23e7:f5db
Additional Information — All machines within a common networking environment
(whether public or private) must have unique IP addresses. Within a private network, this
can be coordinated just within the owning organization. But, when you want to
communicate on the international Internet, the addresses have to be coordinated through
an international Internet Registry organization. For example, the American Registry for
Internet Numbers (ARIN) coordinates IP address assignment for the Americas. For
practical purposes, the Internet Registries have been delegating this job to the Internet
Service Providers (ISPs). It is also important to have unique symbolic names. This is
insured by the hierarchical naming embodied in the fully qualified names we discussed.
In a LAN, all the names and addresses can be held on each system in an ASCII file or can
be centralized in a network Domain Name Server.
Only small isolated networks tend to depend on ASCII files to handle name resolution.
Transition Statement — So why use networks?
Uempty
TCP/IP Network Facilities
Server Clients
Disk storage Network File Transfer PC
Printers Management
Programs
Login Mail
Sessions Network
RS/6000
Other Systems RS/6000
• Standard TCP/IP facilities include: mail, file transfer, remote login,
remote execution, and remote printing
• A number of AIX Applications use TCP/IP:
– Network File System (NFS)
– Network Information Services (NIS)
– Domain Name Service (DNS)
– Dynamic Host Configuration Protocol (DHCP)
– Network Computing System (NCS)
– Distributed Computing Environment (DCE)
– X Windows and AIXWindows
– Tivoli Netview for AIX
© Copyright IBM Corporation 2005
Notes:
Network applications
There are many applications that require or can take advantage of TCP/IP. The ones
listed are available from IBM either as standard or as licensed program products. There
are many third-party applications (for example databases) that can also use TCP/IP for
distributed work.
- Network File System (NFS) allows access of remote files as if they were local.
- Network Information Services (NIS) provides a distributed database of system
information.
- Domain Name Service (DNS) provides server support to keep track of host names
and addresses in the network.
- Dynamic Host Configuration Protocol (DHCP) allows a host to dynamically obtain a
TCP/IP address from a server in the network.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Each system in a TCP/IP network must have a unique TCP/IP address and hostname.
Your network administrator centrally manages tables of names and addresses, and
assigns these for your system. On some networks a subnet mask is also required which
is used to determine which network your machine belongs to for routing purposes.
Address
AIX V4.3 and later provides support for both IPV4 and IPV6 addresses. The IPV6
addresses are 128 bits in length, represented as eight 16-bit fields separated by colons.
A technique called tunneling is used to allow systems with IPV4 and IPV6 to coexist.
SMIT and the Web-based System Manager provide separate support for configuring
IPV6.
Gateway
If your network is just part of a larger network then you need to know about the gateway
machines which link your network to others. Most network designs only have one
gateway, called the default gateway. You need to know the address of the default
gateway to allow your system to communicate with other systems through the gateway.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the information needed to configure TCP/IP.
Details — This information will be provided by the network administrator, and it may not be
the responsibility of the system administrator to configure TCP/IP.
In this unit, only flat networks are considered. Do not explain in any detail domain networks.
The student notes mention the IPV6 addresses. These are supported at AIX V4.3 and later.
These addresses are 128 bits in length. The contents of these addresses is way beyond
the scope of this class. The point here is to let the students know that AIX supports these
128-bit addresses. The advantage of this address format is to provide many more
addresses for hosts and networks than were previously available.
AIX RS/6000 systems with network interfaces configured with IPV4 and IPV6 can coexist
using a technique called tunneling. This technique basically puts an IPV6 packet inside an
IPV4 packet. This then provides for gradual transition to IPV6.
IPV6 also provides support for the Neighbor Discovery Protocol (NDP), auto-configuration
of IP addresses and additional routing enhancements. AIX also supports additional IP
security for both IPV4 and IPV6.
SMIT provides support to configure IPV6 and tunneling.
Transition Statement — Having gathered the network address/hostname, the next step
can be done through SMIT.
Uempty
Configuring TCP/IP
# smit mktcpip
Minimum Configuration & Startup
Notes:
Minimum configuration
The SMIT Minimum Configuration & Startup option (fastpath: mktcpip) or the
mktcpip command can be used to quickly configure TCP/IP on AIX systems. This
initializes TCP/IP (for client services) but further customization will be required.
The minimum information that is required to start TCP/IP is the hostname, and one
interface and its Internet address. If subnetting is used, then the subnet mask should be
specified. A static route can be specified to a default gateway. Also, the domain name
and name server for a client in a domain network can be specified.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
You can decide whether to start the TCP/IP daemons when initializing TCP/IP through
this option.
Further configuration
The Further Configuration menu (fastpath: configtcp) contains a series of menus for
customizing TCP/IP options. For example, hostnames, routes, interfaces, name
resolution, server and client services.
Dead gateway detection is a mechanism for hosts to detect a dead gateway or a
gateway that is not responding. The cost is used with dead gateway detection to
prioritize routes.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
# more /etc/hosts
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
• host command:
í Examples:
# host sys3
sys3 is 10.0.0.3, Aliases: sys3.washington.ibm.com
# host 10.0.0.3
sys3 is 10.0.0.3, Aliases: sys3.washington.ibm.com
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
The ARPA commands for testing connectivity, remote execution, file transfer, and
remote login are ping, rexec, ftp, and telnet respectively.
These commands can be used between any TCP/IP system that supports the
appropriate protocols, not just UNIX/AIX systems.
In order to ensure security across the network, these commands always require a user
name and password to be supplied when you establish a connection.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Uempty can terminate the telnet client by using the quit subcommand. Many of the
subcommands are for managing an existing connection.
When in a telnet session with a remote host, you can obtain the telnet> prompt by
issuing the escape sequence <ctrl+]> (press the ] key while holding down the Ctrl
key). The telnet client will maintain the connection while allowing you to use telnet
subcommands. If you then wish to obtain a shell prompt from your local client host, the
telnet subcommand z will place the telnet client in a suspended state and return you
to the parent shell. It will tell you the job number of the suspended telnet process.
From here, you can run other commands. If you wish to return to your telnet session,
simply resume the suspended job with the fg command. The telnet process will be
resumed. If you just hit Enter, then you will be back in your interactive session with the
remote host.
An example:
sys1$ telnet sys2
Trying . . .
Connected to sys2.
Escape character is '^]'.
login: tom
password: tom's password
sys2$ ^]
telnet> ?
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List several user utilities that depend on TCP/IP.
Details — All of the listed utilities are used but of them all, the ping utility is probably the
most useful at this stage, since it allows test data to be exchanged between two systems.
These utilities are also known as the authenticated TCP/IP commands as they expect a
user id and password on the remote system.
The syntax of the ftp command is: ftp [options] host
There are a number of options, the most notable are:
• -g enables wildcards in file names
• -i disable interactive prompting during multiple transfers
• -n prevent automatic login
To execute a shell on the local system use ! To execute a command on the local system
use ! command.
The illustrated example of ftp in the student notes does the following:
- The user runs ftp and asks to be connected to sys2
- The connection is established and the user is asked for a remote username
- The username is validated and the user is prompted for the password
- The remote login sequence is confirmed
- The user wishes to transfer a binary data file so he sets the file type to binary/image
- The user transfers a file to the remote system using the put command
- Statistics for the transfer are displayed
- The quit command will logout and disconnect from the remote system, then exit
ftp
The numbers displayed are messages defined by file transfer protocol which are
exchanged between the local and remote systems.
Note: The remote user must exist and must have a password defined at the remote host. If
no password is assigned, ftp will not allow you to establish a connection.
The tn and tn3270 commands are alternative names for telnet. The tn3270 command
runs telnet in 3270 terminal emulation mode when connecting to a System/370™host.
Additional Information — Beginning with AIX 5L V5.2, the AIX ftp server can restrict
which clients are allowed access and what directories users on those clients can read or
write into. Provision is made for defining restrictions for anonymous ftp users. The
configuration file that defines these restrictions is /etc/ftpaccess.ctl.
Transition Statement — Before we summarize, let's look at a few checkpoint questions.
Uempty
Checkpoint
1. What are the following commands used for?
• ftp ______________________________________
• rexec ______________________________________
• telnet ______________________________________
4. Which file holds the name and the TCP/IP address of each
host in a flat network? _________________________
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review and test the students understanding of this unit.
Details — A suggested approach is to give the students about five minutes to answer the
questions on this page. Then, go over the questions and answers with the class.
Checkpoint Solutions
1. What are the following commands used for?
• ftp transfers files from one machine to another
• rexec executes a command on a remote system
• telnet logins to another system
4. Which file holds the name and the TCP/IP address of each
host in a flat network? /etc/hosts
Additional Information —
Transition Statement — Now, let’s do an exercise with networking.
Uempty
Exercise 20: Networking
• Deconfigure TCP/IP
• Configure TCP/IP
• Testing the configuration
• Using telnet
• Using ftp
Notes:
Introduction
This lab gives you an opportunity to configure an AIX system on a TCP/IP network. This
gives you practical application of the concepts presented in this unit.
This exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Do the networking exercise
Details —
Additional Information —
Transition Statement — Now, let’s summarize the unit.
Uempty
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Unit 18. Networking Overview 18-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement — This is the last unit for the course.
Checkpoint Solutions
1. What type of adapter are you likely to require for a single-
user graphics workstation?
a. Asynchronous
b. Communications
c. Graphics
Checkpoint Solutions
1. AIX 5L can be installed from which of the following:
(select all that are correct)
a. 8 mm tape
b. CD-ROM
c. Diskette
d. 4 mm tape
2. True or False? A Preservation Install preserves all data
on the disks.
Preserves SOME of the existing data on the disk selected for
installation. Warning: This method overwrites the user (/usr),
variable (/var), temporary (/tmp), and root (/) file systems. Other
product (application) files and configuration data are destroyed.
3. What is the console used for during the installation process?
The console is used to display all the system messages and
interact with the installation.
© Copyright IBM Corporation 2005
Checkpoint Solutions
1. Specify the SMIT function keys that can be used for the
following:
a) List the command that will be run: F6
b) List the screen name which can be used for the
fastpath: F8
c) Take a screen image: F8
d) Break out into a shell: F9
e) Return to the previous menu: F3
2. Specify two ways you can request the ASCII character
version of SMIT from an X-windows environment
command prompt:
• smitty
• smit -C
Checkpoint Solutions
1. Which of the following states can your software be in, in order for you
to be able to use it? (select all that apply)
a. Applied state
b. Removed state
c. Install state
d. Commit state
2. What command is used to list all installed software on your system?
lslpp -l
3. Which of the following can you install as an entity? (select all
that apply)
a. Fileset
b. LPP
c. Package
d. Bundle
4. What is the difference between the SMIT menus: Install Software and
Update Installed Software to Latest Level (Update All)?
Install Software by default installs everything from the installation
media (except printer and devices) onto the system.
Update Installed Software to Latest Level (Update All) installs only
updates to filesets already installed on your system.
© Copyright IBM Corporation 2005
Checkpoint Solutions
Checkpoint Solutions
1. True or False? The Web-based System Manager is available
for client access automatically after the BOS is installed.
False. The Web-based System Manager server must be
configured and enabled for client access.
2. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode, use the wsm command to access the
Web-based system manager.
c) It is possible to manage an AIX 5L system from a remote
AIX 5L system using an ASCII terminal.
C is false. However, with a graphics terminal it is possible
to manage different systems simultaneously by adding
the remote systems in the Navigation window of Web-
based System Manager.
© Copyright IBM Corporation 2005
Checkpoint Solutions
1. What is the first process that is created on the system
and which file does it reference to initiate all the other
processes that have to be started?
The initial process is init, which checks /etc/inittab
for information regarding other processes that have to
be started.
Unit 8: Devices
Checkpoint Solutions
1. Is it possible to use SCSI ID 7 for a new tape drive?
No. The SCSI adapter itself uses ID 7. So, it cannot be used
for other devices.
2. Use the output on the next visual (lsdev -C -H) to answer the
following four questions.
a) What will happen if we attempt to add another device with
the SCSI address set to 4?
The operation will fail as there is already a device
(SCSI Disk Drive) configured at this location.
b) Can the 8 mm tape drive be currently used? Why?
No, because it is in the defined state. You have to first make
it available by either using SMIT or the mkdev command.
c) Where is the printer connected? The parallel port
d) The Ethernet adapter is installed in what slot?
It is an integrated adapter which does not occupy a slot on
the PCI bus.
© Copyright IBM Corporation 2005
5. Volume Group
1. Volume Group___
Descriptor Area__
VGDA 6. Physical Volume
2. Physical Partition
3. Logical Partition
4. Logical Volume
© Copyright IBM Corporation 2005
Checkpoint Solutions (1 of 3)
Checkpoint Solutions (2 of 3)
Use the following output to answer the questions below:
# lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs 8192 -- yes no
/dev/hd1 -- /home jfs 90112 -- yes no
/dev/hd2 -- /usr jfs 507904 -- yes no
/dev/hd9var -- /var jfs 8192 -- yes no
/dev/hd3 -- /tmp jfs 16384 -- yes no
/dev/hd10opt -- /opt jfs 65536 -- yes no
/dev/cd0 -- /infocd cdrfs ro yes no
/dev/lv00 -- /home/john jfs 8192 rw yes no
5. With which logical volume is the /home file system associated? /dev/hd1
6. What type of file systems are being displayed? Journaled file systems (JFS),
enhanced journaled file systems (JFS2), and CD-ROM (CDRFS)
7. What is the mount point for the file system located on the /dev/lv00 logical
volume? /home/john
8. Which are the system supplied logical volumes and their associated file
systems? /dev/hd4 (/), /dev/hd1 (/home), /dev/hd2 (/usr), /dev/hd9var (/var),
/dev/hd3 (/tmp), /dev/hd10opt (/opt)
9. Which file system is used primarily to hold user data and home directories?
/home
© Copyright IBM Corporation 2005
Checkpoint Solutions (3 of 3)
Use the following output to answer the question below:
# lsvg -l rootvg
Checkpoint Solutions
1. True or False? A logical volume can span more than one
physical volume.
2. True or False? A logical volume can span more than one
volume group.
3. True or False? The contents of a physical volume can be
divided between two volume groups.
4. True or False? If mirroring logical volumes, it is not necessary
to perform a backup. False. You still need to back up to
external media.
5. True or False? SMIT can be used to easily increase or
decrease the size of a logical volume. False. SMIT can only be
used to increase a file system. Decreasing one requires backing
up the file system, removing it, re-creating it, and then restoring.
6. True or False? Striping is done at a logical partition level.
False. It is done at a stripe unit level.
Checkpoint Solutions
1. Will the size of the file system change when the size of
the logical volume it is on is increased? No
Checkpoint Solutions
1. What command can you use to determine if a file
system is full? df
Checkpoint Solutions
1. What conclusions regarding potential paging space problems can
you reach based on the following listing?
Page Physical Volume Size %Used Active Auto Type
Space Volume Group
Checkpoint Solutions
1. What is the difference between the following two commands?
a) find /home/fred | backup -ivf /dev/rmt0
b) cd /home/fred; find . | backup -ivf /dev/rmt0
(a) will backup the files using the full path names, whereas
(b) will backup the file names using the relative path names.
So (b)’s files can be restored into any directory.
2. On a mksysb tape, if you entered tctl rewind and then
tctl -f/dev/rmt0.1 fsf 3, which element on the tape could
you look at? You would be at the start of the backed up images of
the files, having skipped over the boot portion of the tape.
3. Which command could you use to restore these files?
The files were backed up using the backup command so you would
have to use the restore command.
4. True or False? smit mksysb backs up all file systems, provided
they are mounted. mksysb only backs up rootvg file systems. To
back up other volume groups, you must use the savevg command.
Checkpoint Solutions (1 of 2)
1. What are the benefits of using the su command to switch user to
root over logging in as root?
A log (which can be monitored) of all users executing the su
command is kept in the sulog.
2. Why is a umask of 027 recommended?
This value removes all permission bits for the “others” category,
which enhances security.
3. As a member of the security group, which password command
would you use?
pwdadm (This command does not prompt for the root password
or the old password of the user whose password is being
changed.)
4. Which password change command does SMIT use?
passwd
5. True or False? When you delete a user from the system, all the
user's files and directories are also deleted.
© Copyright IBM Corporation 2005
Checkpoint Solutions (2 of 2)
6. If an ordinary user forgets their password, can the system
administrator find out by querying the system as to what the user's
password was set to? No, because the passwords are held in
encrypted format, so even the system administrator cannot tell what
the password was set to.
7. Password restrictions are set in which of the following files?
a. /etc/passwd
b. /etc/security/passwd
c. /etc/security/restrictions
d. /etc/security/user
8. Which of the following statements are true?
a. A user can only belong to one group
b. A member of the security group can administer user accounts
c. An admin user is a user whose account cannot be administered
by any member of the security group (except root)
d. The chmod g+s command sets the SUID permission of a file
e. The root user, commonly known as the superuser has UID=0
and GID=0
© Copyright IBM Corporation 2005
Checkpoint Solutions
1. True or False? The at.allow and at.deny files must be
used to specify which users are allowed and denied use
of the at command.
False. Only one or the other of these files should be used.
Checkpoint Solutions (1 of 2)
1. True or False? One of the advantages of queues is that each
user can have a different default queue set up for them.
True. This can be accomplished using the PRINTER
environment variable.
2. True or False? The /etc/qconfig file is read by the backend
program to determine what the queue discipline is.
False. It is read by qdaemon.
3. True or False? All printer software is automatically installed
when you install the base operating system.
False. Only a handful of printer software is installed by default.
4. What is the difference between these two commands?
# qprt -Pasc file1
# qprt -c -Pasc file1
The -c flag produces a spool file.
Checkpoint Solutions (2 of 2)
5. What three methods can be used to find out what the system
default queue is?
í First entry in /etc/qconfig file
í The output from the qchk command with no options
í The first queue listing from the lpstat command
6. What users can bring print queues down?
The root user or members of the printq group.
7. True or False? Once the queue is down, no more jobs can
be submitted to the printer.
False. Jobs can be submitted to the queue. However, they
will not be printed until the queue is brought up again.
8. Can users hold all their print jobs in a specific queue?
If so, how?
Yes, they can by only specifying a queue name and not
individual job numbers.
Checkpoint Solutions
1. What are the following commands used for?
• ftp transfers files from one machine to another
• rexec executes a command on a remote system
• telnet logins to another system
4. Which file holds the name and the TCP/IP address of each
host in a flat network? /etc/hosts
Checkpoint Solutions (1 of 2)
1. True or false? AIX Web-based documentation can be
used to reference information in different ways, such as
searching for a command, searching for a task or viewing
information in a book like manner.
Checkpoint Solutions (2 of 2)
4. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L V5.2 system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode use the wsm command to access the
Web-based System Manager.
c) It is possible to manage an AIX 5L V5.2 system from a
remote AIX 5L V5.2 system using an ASCII terminal.
d) The Web-based System Manager includes TaskGuides that
direct the user through complex tasks.
a, b, d are true.
c is false. However, it is possible with a graphics terminal, to
manage different systems simultaneously by adding the
remote systems in the Navigation window of Web-based
System Manager.
© Copyright IBM Corporation 2005
Checkpoint Solutions
1. True or false? If a device, like a TTY, is left for cfgmgr to
configure automatically, it picks up the default values which
might not be desirable. TTYs and other serial devices are not self-
configurable and so are not detected by cfgmgr.
Checkpoint Solutions
1. List two advantages of the System V print subsystem.
Compatibility, Availability of interface programs, Security, Support for
Forms, Standard PostScript filters, Long term direction
2. List two advantages of the AIX print subsystem.
Powerful and flexible printer drivers, mature system management tools,
Customizable spooling subsystem
3. What command is used to switch from AIX to System V printing?
switch.prt -s SystemV
4. lpsched uses information in the printer configuration file and terminfo
to screen print jobs.
5. The interface program uses commands in terminfo to initialize the
printer.
6. Filters are used to convert file content.
7. Use the lpfilter command to manage filters.
8. lpadmin is used to create or modify a System V printer.
9. mkdev is used to create a printer device.
References
Online AIX 5L Version 5.2 Web-based System Manager
Administration Guide
SG24-5765 AIX 5L Differences Guide Version 5.2 Edition
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• In AIX 5L V5.2:
– Set up and use AIX Web-based documentation
– Define the use of the Web-based System Manager
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Documentation Server
AIX 5L V5.2 softcopy Documentation Client
documentation Web browser software
Documentation Library Service
Web server software
Web browser software
Documentation Client
Web browser software
Notes:
Overview
In addition to providing SMIT to make system administration tasks easy, beginning with
AIX V4.3, softcopy documentation is loaded on a documentation server. Any other
computer in the network with appropriate Web-browser software (for example, the
Netscape Navigator) can then become a documentation client.
When users on a client computer request an AIX document, the request is sent to the
Web server on a documentation server which then sends back the requested item.
When searches are performed, they are done on the server computer and the results
are then sent back to the user on the client computer.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Configuration steps
The steps outlined above are used to configure an AIX 5L V5.2 documentation server or
online documentation for a standalone RS/6000 system.
1. Configure TCP/IP on the AIX system.
2. Install the Web server software. AIX 5L V5.2 includes two products that can be
used: the Lite NetQuestion server software and the IBM HTTP Server Web server.
Any other Web server software that supports CGI (Common Gateway Interface) can
also be used. The Lite NetQuestion server can only be used for local users, not
remote users.
3. Configure and start the Web server software. Use IBM HTTP Server Web server for
easy set up.
Uempty 4. Install Web browser software. This is necessary if users on the server wish to
access documents. The Netscape Communicator is included with AIX 5L V5.2.
Actually, any browser can be used, provided it supports Java 1.3.
5. The AIX 5L V5.2 Documentation includes User Guides, System Management
Guides, Application Programmer Guides, Commands Reference Volumes, Files
References, and Technical Reference Volumes. This documentation can be
installed to disk or mounted as a CD-ROM file system.
6. Configure the Documentation Library Service (bos.docsearch). This is installed by
default with the base operating system. To configure it use the smit web_configure
fastpath or the Web-based System Manager.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the steps necessary to install the AIX 5L V5.2 online documentation.
Details — The student notes provide details on the steps necessary to install the AIX 5L
V5.2 online documentation. Remind the students that TCP/IP configuration will be covered
in a later unit.
IBM HTTP Server Web server is included in the AIX 5L V5.2 Expansion Pack and, it is the
easiest to configure on AIX 5L V5.2. When installing the AIX documentation, it is possible
to select specific manuals to install. For example, the CD contains manuals on 3D
graphics, which may not be necessary to install. The documentation CD can be either
installed or mounted. If you mount the CD, the entire CD is mounted. You cannot install part
of the CD and mount the remainder.
During the machine exercise, students will configure the Documentation Library Service.
At this time, also mention the steps necessary to set up the documentation client:
1. Install and configure TCP/IP.
2. Install the Web browser software.
3. Configure the Documentation Library Service. Only the bos.docsearch client filesets
need to be installed on the clients.
Transition Statement — Let's assume that all the steps have been completed except for
the configuration of the Documentation Library Service. We will use SMIT to complete this
step next.
Uempty
Internet and Documentation Services
# smit web_configure
Notes:
Begin configuration
Use the SMIT fastpath smit web_configure to access this menu. This menu is also
accessed via the System Environments option on the main SMIT menu.
Choose the first option, Change/Show Default Browser to begin configuration of
either a documentation server or client.
The Web-based System Manager can also be used to configure the AIX 5L V5.2 online
documentation.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the SMIT screen necessary to configure a documentation server.
Details — We will walk through the steps necessary to configure the documentation
server. Mention that the first and third options must also be chosen if configuring a
documentation client.
Additional Information — The SMIT menu item Web-based System Manager will be used
to configure Web-based SMIT for remote administration.
Transition Statement — Choose Change/Show Default Browser.
Uempty
Change/Show Default Browser
[Entry Fields]
* Default browser LAUNCH COMMAND [netscape]
Notes:
What browser?
Select Change/Show Default Browser from the SMIT Web-configure screen.
On this screen, type in the command that launches the browser that will be the default
browser for users on this system. Indicate the full path name if necessary and any
applicable options/flags. Netscape does not require any options/flags.
Use this SMIT screen also on the documentation clients to indicate the default browser.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show students how they indicate the default browser on either the
documentation server or client.
Transition Statement — After this step completes successfully, on the server it will be
necessary to return to the previous menu and then choose Change Documentation and
Search Server.
Uempty
Change Documentation and Search Server
Change Documentation and Search Server
[Entry Fields]
Documentation search server LOCATION None - disabled +
None - disabled
Remote computer
Local - this computer
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show how SMIT is used to indicate the location of the documentation server.
Details — Choose Local if configuring the server. Choose Remote if configuring the client.
Choose None to deactivate the documentation functions.
Transition Statement — Assume we are configuring the server. So, on this menu, we will
choose Local. Press Enter to continue with the configuration.
Uempty
Change Local
Documentation and Search Server (1 of 2)
Change Local Documentation and Search Server
[Entry Fields]
Web server SOFTWARE IBM HTTP Server Web se> +
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the SMIT menu used to indicate which Web server software is being
used.
Details — If the Web server software is something other than the ones shown on the
menu, choose Other. Press the Enter key to view the SMIT menu on the next page.
Transition Statement — Press Enter on this screen to view the next page.
Uempty
Change Local
Documentation and Search Server (2 of 2)
Change Local Documentation and Search Server
[Entry Fields]
Web server SOFTWARE IBM HTTP Server Web se>
* Local web server PORT number [80] #
* Local web server cgi-bin DIRECTORY [/usr/HTTPServer/cgi-bi>
* Local web server HTML document directory [/usr/HTTPServer/htdocs>
* For versions prior to 1.3.6.0, Auto-start Yes
server if not already running
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
ServerName YourSystemName
(Take out the comment (#) and insert the system’s host name for new.host.name)
3. Reboot the system or run the command: /usr/HTTPServer/bin/httpd
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Uempty On the library home page, near the top, you are given different methods to look at the
documentation. You can view the documents by books, look at command
documentation or view it by a topics and task list.
Moving down the screen, the next area allows you to perform a search. This is probably
the quickest and easiest way to locate information on a specific item. Just type in a key
word and let it find the documents for you.
The last part of the screen shows icons representing the books and category of books
that are available. You can click the icons to expand their information.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the students how to access the online documentation once it has been
configured.
Details — The URLs needed are listed in the student notes. Students learned how to use
the AIX 5L V5.2 online documentation in the AIX 5L Basics course, Q1313/AU13.
The Documentation Library is also available using CDE. It can be accessed using the CDE
Help Manager or the Application Manager.
Additional Information — The documentation is designed to work in a graphical
environment. You must have a browser and graphic monitor to see it.
ASCII users will have to rely on man pages.
Point out the Search area and the Print button. These will be discussed in the next couple
visuals.
Transition Statement — Now let's look at how to download or print the documentation.
Uempty
Print AIX 5L V5.2 Documentation
Notes:
Printing documentation
The Documentation Library Service contains a Print Tool button. When you click this
button, you see a list of books that can be downloaded in a single printable file. You
have the option of customizing this list to include your own book for printing.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Present the AIX 5L V5.2 documentation print page.
Details —
Additional Information —
Transition Statement — Let's take a look at the result of a search.
Uempty
Search AIX 5L V5.2 Documentation
Notes:
Searching documentation
Probably the easiest way to find an answer is to search the documentation using the
Search window on the Documentation Library screen.
Above are the results of a search. A star system is used to indicate the documents that
best match your keywords. Five stars is the best. Clicking the item takes you to that
document.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — To show the output of a search.
Details — Explain the star systems. Also point out that each item is a link to that document.
Transition Statement —
Uempty
IBM pSeries Information Center
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose —
Details —
Additional Information —
Transition Statement —
Uempty
Activity: Configuring Web-based
Documentation
Activity:
Configuring
Web-based
Documentation
Activity Instructions
Configure the Documentation
1. Log in to AIX as teamxx and su to root.
2. Use SMIT to configure the Documentation. This allows you to access the AIX 5L V5.2
online documentation. All the necessary software has been installed; all you have to do
is perform the configuration so that you can access the online documentation. Use IBM
HTTP Server Web server.
Verify the AIX online documentation
3. Since you are accessing the online documentation from a Web server, it is necessary to
know your system's TCP/IP host name and IP address. Display this at the command
line and record the results.____________________
4. Access the AIX 5L V5.2 online documentation.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
5. Congratulations! You have configured the AIX online documentation. Be sure to add a
bookmark with your browser so you don't need to remember the long URL. When you
are done, exit from the browser.
• On the Netscape toolbar, click Bookmarks -> Add Bookmarks.
• On the Netscape toolbar, click File -> Exit.
6. A quick way to locate information in the documentation is to do a search. Use the
command (from the command line) that starts the Documentation Library Service. As
time permits, get familiar with the Web-based documentation by trying a few searches
and looking at some of the documentation. When you are done, log out.
END OF ACTIVITY
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Uempty
Web-based System Manager
Notes:
Introduction
AIX V4.3 introduced the Web-based System Manager, which is the next step in the
evolution of AIX system administration tools. There have been many enhancements to
the Web-based System Manager since AIX 5L V5.1 it is called the default system
administration tool for AIX.
The Web-based System Manager can be run in standalone mode, that is, you can use
this tool to perform system administration functions on the AIX system you are currently
running on.
The Web-based System Manager also supports a client-server environment. In this
environment, it is possible to administer an AIX system from a remote PC or from
another AIX system using a graphics terminal. In this environment, the AIX system
being administered is the server and the system you are performing the administration
functions from is the client.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The client can operate in either application mode on AIX with Java 1.3 or in applet mode
on platforms that support Java 1.3. Thus, the AIX system can be managed from another
AIX system or from a PC running Microsoft Windows NT/2000/XP.
Client requirements
To download Web-based System Manager Client code from an AIX host use the
address http://<hostname>/remote_client.html.
Supported clients are Microsoft Windows NT/2000/XP and RedHat Linux 7.2 and 7.3.
To download Windows Web-based System Manager Client code from an AIX host and
start Install Shield use the address: http://<hostname>/wsmship/pc_client/setup.html.
The Windows Web-based System Manager Client installation needs around 64 MB disk
space.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Standalone
# wsm
Client-Server
With browser, URL:
http://<hostname>/wsm.html
As Standalone Java application
Double-click on the Web-based SystemManager
Remote Client icon
From AIX client:
# wsm -host <hostname>
© Copyright IBM Corporation 2005
Notes:
Standalone mode
In standalone mode, to access the Web-based System Manager use the command wsm.
- From the CDE Application Manager, you can also access by icons if you are using
CDE. Open the System Admin folder and double-click on Management Console
to view icons for each of the Web-based System Manager applications.
Client-server mode
If using the Web-based System Manager in client-server mode:
- If the Web-based System Manager client is running as a Java applet in a browser
use the appropriate URL to access the tool. The default URL is
http://<hostname>/wsm.html. Be aware that AIX 5L V5.1 is using Java 1.3.0 and AIX
5L V5.2 is using Java 1.3.1 and that your browser plug-in-version must be
compatible to the Java version on the AIX server.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Discuss the various methods to invoke the Web-based System Manager.
Details — The visual shows how to access the Web-based System Manager from both the
standalone and client-server environments.
Accessing the Web-based System Manager from standalone mode implies that you are
performing the system administration tasks directly on the AIX system. Access the
Web-based System Manager from either the command line or from the CDE Application
Manager.
Accessing the Web-based System Manager from a client system allows for AIX to be
remotely administered through a graphical interface. There are two ways this can be done.
If the client is an AIX system, you can use the command
wsm -host <hostname> -or- you can use your Web browser. If the client machine is a
non-AIX machine, you will need to use a browser. The URL to access the Web-based
System Manager is http://<hostname>/wsm.htm.
The hostname used in the URL must be resolvable. If it is not, an IP address may be used
in place of the hostname.
Additional Information — Some set up is needed on the server before remote access to
the Web-based System Manager can be made. This is discussed shortly.
Transition Statement — Let's assume you use one of the listed methods to access the
Web-based System Manager. Let's take a look at what you will see.
Uempty
Using the Web-based System Manager (1 of 3)
Notes:
Console window
This visual shows the Web-based System Manager Console Window containing two
primary panels. The panel on the left displays the machines that you can manage from
the Console Window. This panel is referred to as the Navigation Area. The panel on
the right (the Contents Area) displays results based on the item selected in the
Navigation Area. You select the machine to perform management operations from the
Navigation Area. As you navigate to the desired operation in the Navigation Area, the
Contents Area is updated to show the allowable choices.
Session log
There is a session log that is a facility of the console. It keeps track of changes made on
managed hosts during a Web-based System Manager session.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the Web-based System Manager console.
Details — The visual shows the Web-based System Manager console.
Point out that this application is intuitive, object-oriented and easy-to-use.
Also point out the different icons (also referred to as plug-ins) displayed on the screen.
These icons provide support for most of the functions that are currently supported by SMIT.
The student notes also mention that the Web-based System Manager provides
TaskGuides. These TaskGuides are similar to what the user sees when using the AIX
Configuration Manager. The user is asked questions and is led through the steps to
perform a task.
There is a session log that is a facility of the console. It keeps track of changes made on
managed hosts during a Web-based System Manager session. Entries in the log include:
- Time and date of change
- Who made the change
- Host where the change was made
- Short message
- If generated by an application, intermediate results, warnings or error conditions
To view the session log, select Console -> Session Log.
Transition Statement — Suppose we wanted to change the system date and time. In the
Content area, double-click the System Environment icon, then the Settings icon. Or, in
the Navigation area you can expand the System Environment label, then double-click
the Settings label. We will use this as an example of how to use the Web-based System
Manager.
Uempty
Using the Web-based System Manager (2 of 3)
Notes:
Toolbar functions
The visual shows a Web-based System Manager window with the System
Environment: Settings plug-in running in the Contents area. Above the Navigation
Area and Contents Area, there is a toolbar with symbols for managing the window.
From left to right, the symbols support the following functions: Back to previous screen,
Forward to next screen, Up one level, Stop reloading, Reload now, Shutdown,
Broadcast message, Find, Show properties of highlighted object, Icon (to return to icon
mode if currently viewing details), Details (which lists each icon and provides an
explanation of each). Most of these functions can also be accessed via the View option
on the menu bar.
Date/Time icon
If you select the Date/Time icon, this allows you to set the date and time on the system.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — In our example, we have chosen System Environment, then Settings. This is
the window that will be displayed.
Details — Explain some of the options in the tool bar and in the menu bar as outlined in the
student notes. These options will vary depending on the window being used.
In our example, double-click Date and Time.
Transition Statement — The next page shows us what we will see if we double-click Date
and Time
Uempty
Using the Web-based System Manager (3 of 3)
Notes:
Overview
Note that the Web-based System Manager supports an easy-to-use point-and-click
environment where information can be entered. Use this window to set the system date
and time (only the root user can perform this function). When finished, click OK to apply
your change.
Additional information on the Web-based System Manager can be accessed through
the Internet using the URL: http://www-1.ibm.com/servers/aix/wsm/ .
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Show the window used to change the system date and time.
Details — Be sure to point out that most of the Web-based System Manager applications
are similar to this, providing point-and-click support to perform various system
management functions.
Note that in this application there is a second option, Time Zone. Click this option to
change the system's time zone.
Daylight Savings Time Dates can vary from country to country. Click this button to change
the dates from the U.S. defaults of the first Sunday in April and the last Sunday in October.
Transition Statement — Now, we will look at how to configure the Client/Server
Web-based System Manager.
Uempty
Configuring the Client/Server Web-based
System Manager
• Install the Web server
• Test the Web server
• Install the Web-based System Manager
(usually done by default with the base)
• Define the Web server document directory
# /usr/websm/bin/wsmserver -enable
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
sysmgt.websm.rte
sysmgt.websm.Webaccess
To set up the documentation directory, you need to know the location of the document
directory for the Web server you are using. We are using the IBM HTTP Server Web
server in the classroom. The path needed is /usr/HTTPServer/htdocs.
Run the following command:
/usr/websm/bin/wsmappletcfg -docdir directory
For example, for IBM HTTP Server Web server, the command would be:
/usr/websm/bin/wsmappletcfg -docdir /usr/HTTPServer/htdocs
Next, enable the Web-based System Manager server
/usr/websm/bin/wsmserver -enable
This can also be done through smit using the fastpath
smit web_based_system_manager .
Which automatically runs
/usr/websm/bin/wsmserver -enable
To access the Web-based System Manager from the client machine, use the URL:
http://<hostname>/wsm.html
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint (1 of 2)
1. True or false? AIX Web-based documentation can be
used to reference information in different ways, such as
searching for a command, searching for a task or viewing
information in a book like manner.
Notes:
Checkpoint Solutions (1 of 2)
1. True or false? AIX Web-based documentation can be
used to reference information in different ways, such as
searching for a command, searching for a task or viewing
information in a book like manner.
Additional Information —
Transition Statement — Continue with checkpoint questions.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Checkpoint (2 of 2)
4. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L V5.2 system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode use the wsm command to access the
Web-based System Manager.
c) It is possible to manage an AIX 5L V5.2 system from a
remote AIX 5L V5.2 system using an ASCII terminal.
d) The Web-based System Manager includes TaskGuides that
direct the user through complex tasks.
Notes:
Checkpoint Solutions (2 of 2)
4. Which of the statements are true regarding the Web-based
System Manager?
a) An AIX 5L V5.2 system can be managed from a remote PC
with appropriate JAVA and Web-browser code installed.
b) In standalone mode use the wsm command to access the
Web-based System Manager.
c) It is possible to manage an AIX 5L V5.2 system from a
remote AIX 5L V5.2 system using an ASCII terminal.
d) The Web-based System Manager includes TaskGuides that
direct the user through complex tasks.
a, b, d are true.
c is false. However, it is possible with a graphics terminal, to
manage different systems simultaneously by adding the
remote systems in the Navigation window of Web-based
System Manager.
© Copyright IBM Corporation 2005
Additional Information —
Transition Statement — Summarize the unit.
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix B. Configuring AIX 5L V5.2 Documentation B-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Directories
mkdir Make directory
cd Change directory. Default is $HOME directory.
rmdir Remove a directory (beware of files starting with “.”)
rm Remove file; -r option removes directory and all files and
subdirectories recursively.
pwd Print working directory: shows name of current directory
ls List files
-a (all)
-l (long)
-d (directory information)
-r (reverse alphabetic)
-t (time changed)
-C (multi-column format)
-R (recursively)
-F (places / after each directory name and * after each exec
file)
Files - Basic
cat List files contents (concatenate). Can open a new file with
redirection, for example, cat > newfile. Use <Ctrl>d to end
input.
chmod Change permission mode for files or directories.
• chmod =+- files or directories
• (r,w,x = permissions and u, g, o, a = who)
• Can use + or - to grant or revoke specific permissions.
• Can also use numerics, 4 = read, 2 = write, 1 = execute.
AP Files - Advanced
awk Programmable text editor / report write
banner Display banner (can redirect to another terminal nn with
> /dev/ttynn)
cal Calendar (cal month year)
cut Cut out specific fields from each line of a file
diff Differences between two files
find Find files anywhere on disks. Specify location by path (will
search all subdirectories under specified directory).
• -name fl (file names matching fl criteria)
• -user ul (files owned by user ul)
• -size +n (or -n) (files larger (or smaller) than n blocks)
• -mtime +x (-x) (files modified more (less) than x days ago)
• -perm num (files whose access permissions match num)
• -exec (execute a command with results of find command)
• -ok (execute a command interactively with results of find
command)
• -o (logical or)
• -print (display results. Usually included.)
find syntax: find path expression action
For example:
• find / -name "*.txt" -print
• find / -name "*.txt" -exec li -l {} \;
(Executes li -l where names found are substituted for {})
; indicates end of command to be executed and \ removes
usual interpretation as command continuation character)
grep Search for pattern, for example, grep pattern files.
pattern can include regular expressions.
• -c (count lines with matches, but don't list)
• -l (list files with matches, but don't list)
• -n (list line numbers with lines)
• -v (find files without pattern)
Expression metacharacters:
• [ ] matches any one character inside.
• with a - in [ ] will match a range of characters.
• ^ matches BOL when ^ begins the pattern.
• $ matches EOL when $ ends the pattern.
• . matches any single character. (same as ? in shell).
Editors
ed Line editor
vi Screen editor
INed LPP editor
emacs Screen editor +
AP Metacharacters
* Any number of characters (0 or more)
? Any single character
[abc] [ ] any character from the list
[a-c] [ ] match any character from the list range
! Not any of the following characters (for example, leftbox !abc
right box)
; Command terminator used to string commands on a single line
& Command preceding and to be run in background mode
# Comment character
\ Removes special meaning (no interpretation) of the following
character
Removes special meaning (no interpretation) of character in
quotes
" Interprets only $, backquote, and \ characters between the
quotes.
' Used to set variable to results of a command
for example, now='date' sets the value of now to current
results of the date command.
$ Preceding variable name indicates the value of the variable.
AP Variables
= Set a variable (for example, d="day" sets the value of d to
"day"). Can also set the variable to the results of a command
by the ` character, for example, now=`date` sets the value of
now to the current result of the date command.
HOME Home directory
PATH Path to be checked
SHELL Shell to be used
TERM Terminal being used
PS1 Primary prompt characters, usually $ or #
PS2 Secondary prompt characters, usually >
$? Return code of the last command executed
set Displays current local variable settings
export Exports variable so that they are inherited by child processes
env Displays inherited variables
echo Echo a message (for example, echo HI or echo $d).
Can turn off carriage returns with \c at the end of the message.
Can print a blank line with \n at the end of the message.
Transmitting
mail Send and receive mail. With userid sends mail to userid.
Without userid, displays your mail. When processing your mail,
at the ? prompt for each mail item, you can:
• d - delete
• s - append
• q - quit
• enter - skip
• m - forward
mailx Upgrade of mail
uucp Copy file to other UNIX systems (UNIX to UNIX copy)
System Administration
df Display file system usage
installp Install program
kill (pid) Kill batch process with ID or (PID) (find using ps);
kill -9 PID will absolutely kill process
mount Associate logical volume to a directory;
for example, mount device directory
ps -ef Shows process status (ps -ef)
umount Disassociate file system from directory
smit System management interface tool
Miscellaneous
banner Displays banner
date Displays current date and time
newgrp Change active groups
nice Assigns lower priority to following command (for example,
nice ps -f)
passwd Modifies current password
sleep n Sleep for n seconds
stty Show and or set terminal settings
touch Create a zero length files
xinit Initiate X-Windows
wall Sends message to all logged in users.
who List users currently logged in (who am i identifies this user)
man,info Displays manual pages
System Files
/etc/group List of groups
/etc/motd Message of the day, displayed at login.
/etc/passwd List of users and signon information. Password shown as !.
Can prevent password checking by editing to remove !.
/etc/profile System wide user profile executed at login. Can override
variables by resetting in the user's .profile file.
/etc/security Directory not accessible to normal users
/etc/security/environ User environment settings
/etc/security/group Group attributes
/etc/security/limits User limits
/etc/security/login.cfg Login settings
/etc/security/passwd User passwords
/etc/security/user User attributes, password restrictions
Variables
var=string Set variable to equal string. (NO SPACES). Spaces must be
enclosed by double quotes. Special characters in string must
be enclosed by single quotes to prevent substitution. Piping (|),
redirection (<, >, >>), and & symbols are not interpreted.
$var Gives value of var in a compound
echo Displays value of var, for example, echo $var
HOME = Home directory of user
MAIL = Mail file name
PS1 = Primary prompt characters, usually "$" or "#"
PS2 = Secondary prompt characters, usually ">"
PATH = Search path
TERM = Terminal type being used
export Exports variables to the environment
env Displays environment variables settings
Commands
# Comment designator
&& Logical-and. Run command following && only if command
Preceding && succeeds (return code = 0).
|| Logical-or. Run command following || only if command
preceding || fails (return code < > 0).
exit n Used to pass return code nl from shell script. Passed as
variable $? to parent shell
expr Arithmetic expressions
Syntax: "expr expression1 operator expression2"
operators: + - \* (multiply) / (divide) % (remainder)
for loop for n (or: for variable in $*); for example,:
do
command
done
if-then-else if test expression
then command
elif test expression
then command
else
then command
fi
read Read from standard input
shift Shifts arguments 1-9 one position to the left and decrements
number of arguments
test Used for conditional test, has two formats.
if test expression (for example, if test $# -eq 2)
if [ expression ]
(for example, if [ $# -eq 2 ]) (spaces required)
Integer operators:
-eq (=) -lt (<) -le (=<)
-ne (<>) -gt (>) -ge (=>)
String operators:
= != (not eq.) -z (zero length)
File status (for example, -opt file1)
• -f (ordinary file)
• -r (readable by this process)
• -w (writable by this process)
• -x (executable by this process)
• -s (non-zero length)
while loop while test expression
do
command
done
Miscellaneous
sh Execute shell script in the sh shell
-x (execute step by step - used for debugging shell scripts)
vi Editor
Entering vi
vi file Edits the file named file
vi file file2 Edit files consecutively (via :n)
.exrc File that contains the vi profile
wm=nn Sets wrap margin to nn. Can enter a file other than at first line
by adding + (last line), +n (line n), or +/pattern (first occurrence
of pattern).
vi -r Lists saved files
vi -r file Recover file named file from crash
:n Next file in stack
:set all Show all options
:set nu Display line numbers (off when set nonu)
:set list Display control characters in file
Units of Measure
h, l Character left, character right
k or <Ctrl>p Move cursor to character above cursor
j or <Ctrl>n Move cursor to character below cursor
w, b Word right, word left
^, $ Beginning, end of current line
<CR> or + Beginning of next line
- Beginning of previous line
G Last line of buffer
Cursor Movements
Can precede cursor movement commands (including cursor arrow) with number of times to
repeat, for example, 9--> moves right nine characters.
0 Move to first character in line
$ Move to last character in line
^ Move to first nonblank character in line
fx Move right to character x
Fx Move left to character x
AP Adding Text
a Add text after the cursor (end with <esc>)
A Add text at end of current line (end with <esc>)
i Add text before the cursor (end with <esc>)
I Add text before first nonblank character in current line
o Add line following current line
O Add line before current line
<esc> Return to command mode
Deleting Text
<Ctrl>w Undo entry of current word
@ Kill the insert on this line
x Delete current character
dw Delete to end of current word (observe punctuation)
dW Delete to end of current word (ignore punctuation)
dd Delete current line
d Erase to end of line (same as d$)
d) Delete current sentence
d} Delete current paragraph
dG Delete current line thru end-of buffer
d^ Delete to the beginning of line
u Undo last change command
U Restore current line to original state before modification
Replacing Text
ra Replace current character with a
R Replace all characters overtyped until <esc> is entered
s Delete current character and append test until <esc>.
s/s1/s2 Replace s1 with s2 (in the same line only)
S Delete all characters in the line and append text
cc Replace all characters in the line (same as S)
Moving Text
p Paste last text deleted after cursor (xp will transpose 2
characters)
P Paste last text deleted before cursor
nYx Yank n text objects of type x (w, b = words,) = sentences, } =
paragraphs, $ = end-of-line, and no "x" indicates lines. Can
then paste them with p command. Yank does not delete the
original.
"ayy" Can use named registers for moving, copying, cut/paste with
"ayy" for register a (use registers a-z). Can then paste them
with ap command.
Miscellaneous
. Repeat last command
J Join current line with next line
© Copyright IBM Corp. 1997, 2005 Appendix D. Sample Shell Scripts Used in Class D-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The following shell script, lab 6, was used in the Optional Exercises section in the Printers
Exercise:
#!/usr/bin/ksh
echo "Working, please wait .\c"
stopsrc -s qdaemon 2> /dev/null 1>/dev/null
echo ".\c"
echo "\n\n: \n" >> /etc/qconfig 2>/dev/null
echo ".\c"
AP The following shell script, lockvi, is first used in the Managing File Systems Exercise:
while true # always perform loop unless see a break statement
do
filename='basename $1' # retrieve just the filename, not the directory
if [ -f /tmp/lock${filename} ]
then echo "Someone else is editing $1. Please wait in the queue."
sleep 2
continue # to top of while loop until lock is removed
else
trap "rm /tmp/lock${filename}" 1 2 3 15 # If they try to cut out
# early, clean up the lock
touch /tmp/lock${filename}
echo "now editing $1"
sleep 1
/usr/bin/vi $1
rm /tmp/lock${filename}
break # only when you're done can you break out of while loop
fi
done
© Copyright IBM Corp. 1997, 2005 Appendix D. Sample Shell Scripts Used in Class D-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The following shell script, mkfile, is used in the Managing File Systems Exercise:
#!/usr/bin/ksh
# mkfile filesize
usage()
{
clear
echo " "
echo " "
echo " "
echo " "
echo "Usage: mkfile filesize"
echo " filesize should be in multiples of 512 bytes"
echo " "
echo " "
echo " "
echo " "
exit
}
# Main...
if [ $# != 1 ]
then
usage
fi
filesize=$1
filename="$1"bytefile
integer mod='expr $filesize % 512'
integer div='expr $filesize / 512'
if [ $mod != 0 ]
then
usage
fi
integer i=0;
integer j='expr $div \* 128'
> $filename
echo " "
echo "Creating file \"$filename\". Please wait ... "
while true
do
echo "yes" >> $filename
i=i+1
if ’ $i = $j ’
then
break
fi
AP done
© Copyright IBM Corp. 1997, 2005 Appendix D. Sample Shell Scripts Used in Class D-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
The following shell script, fragcopy, is used in the Managing File Systems Exercise:
#!/usr/bin/ksh
# fragcopy
usage ()
{
clear
echo " "
echo " "
echo " "
echo " "
echo "Usage: fragcopy numfiles dir/sourcefilename dir/targetfilename"
echo " "
echo " "
echo " "
echo " "
exit
}
# Main...
integer i=0
integer cnt=$1
source=$2
target=$3
if [ $# != 3 ]
then
usage
fi
while true
do
cp $source $target.$i
if [ $? != 0 ]
then
echo " "
exit
fi
i=i+1
echo " Files copied: \c"
echo "$i\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\c"
if [ $i = $cnt ]
then
echo " "
break
fi
done
© Copyright IBM Corp. 1997, 2005 Appendix E. AIX Control Book Creation E-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Directories to monitor
/var/adm/sulog Switch user log file (ASCII file). Use cat, pg or
more to view it and rm to clean it out.
/etc/security/failedlogin Failed logins from users. Use the who command
to view the information. Use
cat /dev/null > /etc/failedlogin to empty it.
/var/adm/wtmp All login accounting activity. Use the who
command to view it. Use
cat /dev/null > /var/adm/wtmp to empty it.
/etc/utmp Who has logged in to the system. Use the who
command to view it.
Use cat /dev/null > /etc/utmp to empty it.
/var/spool/lpd/qdir/* Left over queue requests
/var/spool/qdaemon/* Temporary copy of spooled files
/var/spool/* Spooling directory
smit.log SMIT log file of activity
smit.script SMIT log of commands and scripts
Unit Objectives
After completing this unit, you should be able to:
• Define a serial device to the system
• Set terminal characteristics
• Describe the purpose of the terminfo database
• Diagnose and solve common problems with terminals
Notes:
AP Instructor Notes:
Purpose — Go over the objectives with the students.
Details —
Additional Information —
Transition Statement — Let’s start by defining self-configuring devices and list those that
do not fall under this category.
Non-Self-Configuring Devices
• Devices not configured automatically at boot up by the
configuration manager (cfgmgr):
– ASCII (dumb) terminals
– Printers
– Modems
Notes:
AP Instructor Notes:
Purpose — To remind the audience about self-configuring devices and to list those that do
not fall under this category.
Details — All devices directly connected to the system via the system bus or the SCSI bus
can be recognized and have device support automatically installed for them.
The exceptions are devices attached to the serial and parallel ports. Another exception are
those non-integrated devices attached to the ISA bus on PCI RS/6000 systems.
Additional Information —
Transition Statement — We shall now look at what we need to know before we can add a
serial device to the system.
Adding a Terminal
• Questions to be answered before adding TTYs:
– Server Configuration:
• TTY interface
• Adapter
• Port number
Notes:
AP Instructor Notes:
Purpose — List the information required before a serial terminal can be added.
Details — The information required:
TTY Interface: Communications protocol, RS232, RS422, or vcon
Adapter: Where the TTY port is connected.
Port: Connection on that adapter
Line Characteristics: Line control, and so forth
Terminal Type: Setting for the TERM variable
Keyboard Attributes: Control key settings, and so forth
This information is obtained from the device itself (setup menus, manuals) as well as from
the SMIT menu panels.
Additional Information —
Transition Statement — We will now look at how a terminal line can be used for various
purposes.
Enable/Disable
• Enable login attribute:
login=disable Available for dial-out line
login=enable Login prompt on terminal
login=delay User must press key first
login=share Bi-directional port
Notes:
Login attributes
Appropriate values for the login attribute are:
disable The port is still defined, but it is only available as a dial-out port for an
asynchronous connection to another machine
enable The port is enabled for login, a getty process runs on the port when
not in use
delay The port is enabled for login, but the login prompt is not displayed until
the user presses a key
share The port can be used in either direction upon demand
AP Instructor Notes:
Purpose — Explain the purpose of the login attribute for a serial device.
Details — A serial port can be used for directly connected terminals, a modem, or a serial
printer. Typical interfaces include RS-232C for lower speeds, and RS422 for higher speeds.
When or if the login attributes are not coordinated with the use or intent of the line,
interesting communication problems occur. For example, data blocks sent to the terminal
must be kept relatively small. A delay time between data block transmissions must also be
established to minimize data reception errors.
This is not a great concern when data transmission is slow and irregular, as with keyboard
input. It becomes a problem with raw-mode applications, where massive chunks of input
are transmitted by other computers and by devices such as fax machines.
Depending on its use, the flow of data will be initiated by either the device on the port or by
the system.
If the device is a terminal, then the communications are usually started by the terminal
itself.
This requires the login attribute to be set to enable or delay.
If the device is an outbound modem, then the login attribute should be set to disable.
If the device is a dial-in modem, then the attribute should be set to enable.
If the device is a bi-directional modem, then the attribute should be set to share.
A delayed port can be used for both dial-in and dial-out but the user dialing into a delayed
port will need to send a character (or two) before a login herald will be issued to the port.
Additional Information —
Transition Statement — We shall now look at some of the attributes that control
communications between the computer and the serial device.
Port Attributes
• Various attributes play an important role during
communication between the computer and the serial device.
These include:
– bps/baud rate:
The speed of the line in bits per second
– Number of stop bits:
A signal to a receiving mechanism to wait for the next
signal
– Bits per character:
The number of bits per character to be transmitted
– Parity:
A simple error detection mechanism
Notes:
Baud Rate
The speed of an asynchronous communications line is usually expressed in bits per
second (bps). Sometimes, the term baud rate is used to mean the same thing although
the baud rate actually means the number of possible voltage changes on the line per
second.
Stop bit
During communication, the voltage on one of the lines (the receive/transmit line) is
normally set to high. When a system starts to send a byte, the voltage is set to low for
1.5 clock pulses. This is called a start bit. Similarly, at the end of the transmission of the
byte, (that is, after the last bit), the voltage is set high for a further clock pulse. This is
called a stop bit.
AP Using two stop bits on low-speed lines or poor quality lines will improve
communications.
Parity
Parity is a method of detecting transmission errors. If enabled, a parity bit is appended
to each character transmitted. Types of parity checking are:
EVEN If there are an odd number of ones in the binary representation of the
character sent, the parity bit is set to one so that an EVEN number of
ones is always transmitted
ODD The parity bit ensures that the number of ones transmitted is always odd
MARK The parity bit is always set to 1
SPACE The parity bit is always set to 0
NONE No parity
Instructor Notes:
Purpose — To show some of the attributes that control the communications between the
computer and the serial devices.
Details — There are many more attributes assigned to serial devices. For example, if you
wish to see the default settings for an rs232 serial terminal, enter the following.
# lsattr -Dc tty -s rs232
Additional Information — Additional information on 'Stop Bit': During communications,
when gaps appear between the character transmission, the line is said to be in 'mark state'.
A mark is a binary 1 (or negative voltage) that is set during periods of inactivity on the line.
When the mark state is interrupted by a positive voltage (binary 0), the receiving system
knows that data characters will follow. It is for this reason that the start bit (which precedes
the data character) is always a space bit (binary 0) and the stop bit (which signals the end
of a character) is always a 'mark bit' (binary 1).
Transition Statement — We will now work with SMIT to add a serial terminal to the
system.
AP
SMIT TTY Menu
# smit tty
TTY
Notes:
Instructor Notes:
Purpose — To show the SMIT menu for the serial terminal devices.
Details — TTY devices include both terminals and modems. It is not recommended to
attach printers to the serial port due to poor performance when attached in this fashion.
Additional Information —
Transition Statement — We will now work with the SMIT screens that you would see
when adding a serial terminal.
AP
Attachment
TTY Type
Parent Adapter
Notes:
Instructor Notes:
Purpose — To show how a serial terminal is added to the system. We start by defining the
attachment for the device.
Details — The choices presented in the first panel are for the serial protocol that will be
used to communicate with that device. In the second panel, a list of all devices that use the
selected serial protocol is displayed.
Additional Information —
Transition Statement — Let’s take a look at the device nomenclature for the example
we’re talking about before we continue with the Add a TTY screen.
AP
Device Nomenclature
For the built-in serial connection, the nomenclature looks like this:
sa0 sa1
Built-in adapters
on system planar
Serial ports s1 s2
For the 128-port adapter, the nomenclature looks like this:
Notes:
Pictorial view
This visual shows a picture and the associated nomenclature for the scenario we’re
discussing on adding a TTY.
Instructor Notes:
Purpose — Show a picture of the scenario for the TTY we’re adding.
Details — Point out the naming conventions.
Additional Information —
Transition Statement — The final step is to enter the information about the device.
AP
Add a TTY
Add a TTY
Notes:
Port number
There is only one mandatory field on this screen and that is the PORT number. The F4
key provides a list of possible port numbers. For the first built-in serial port it is s1, for
the second it is s2. On a 16-port RAN, the choices are 0-15. Select the one to which the
terminal is connected. The combination of the appropriate RAN selected on the Parent
Adapter selector screen and the port number shown here provides the system with the
correct location code.
You must supply the port number to uniquely locate the device. The value required
depends upon the adapter specified. For example:
Built-in serial port S1 s1
Built-in serial port S2 s2
8-Port Adapter 0-7
16-Port Adapter 0-15
Each 16-PORT RAN 0-15
Enable LOGIN
The Enable LOGIN attribute is set to disable by default. If you are adding a terminal
that should have a login prompt, you should change this to enable.
TERMINAL type
The TERMINAL type attribute is used to assign the TERM environment variable when
a user logs in on the device. There is no list available for this entry. The easiest way to
find out the required values is to refer to the terminfo database, which is discussed
shortly.
AP Instructor Notes:
Purpose — Show the options for adding a serial terminal.
Details — There are many settings that can be used for a serial terminal. There is only one
mandatory setting and that is the port number for the device.
The combination of parent adapter and port number provide the system with the
information to build the correct location code. In the case of the 128 port adapter, if the
device is attached to port 5 of the first RAN, the parent adapter would have been sa2
(based on our example) selected on the Parent Adapter screen and PORT number 05
selected on the Add a TTY screen. Thus, from this information, the location code
00-03-11-05 would be derived.
Other settings that should be changed are:
• Enable LOGIN = enable
• TERMINAL type = the default terminal type is 'dumb', which has a very limited set of
available features and is not fully functional with ibm3151's and vt100's
• BAUD rate = if the BAUD rate desired is not listed, such as 14400, it can be entered
directly into the field
Additional Information —
Transition Statement — The other item that should be configured for a serial terminal is
the terminal type. We shall see how this works.
terminfo
• Database of terminal capabilities
Notes:
Instructor Notes:
Purpose — Show how the TERM variable can be preset and what it does.
Details — The only thing not mentioned in the student notes is that SMIT can configure a
port to contain the terminal type. This is achieved by setting an attribute for the terminal in
the ODM database.
The /etc/profile contains the lines
# If termdef command returns terminal type (that is, a non NULL value),
# set TERM to the returned value, else set TERM to default lft.
TERM_DEFAULT=lft
TERM=‘termdef‘
TERM=${TERM:-$TERM_DEFAULT}
That ensures that the terminal type is set at login.
Additional Information — The student notes mention the termcap database.
Experienced UNIX users may be familiar with this. The termcap database is not loaded on
the systems in the classroom. The termcap database is delivered with the base AIX
operating system, but is optionally installed. It is found in the bos.compat fileset.
Transition Statement — Sometimes the setup may not be quite right. It is then that we
need to coordinate the attributes set for the terminal in SMIT with the actual terminal
settings.
AP
Change the Characteristics of a TTY
Change/Show Characteristics of a TTY
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[TOP] [Entry Fields]
TTY tty3
TTY type tty
TTY interface rs232
Description Asynchronous Terminal
Status Available
Location 01-G0-00-00
Parent adapter sa0
PORT number [s1] +
Enable LOGIN enable +
BAUD rate [19200] +
PARITY [none] +
BITS per character [8] +
Number of STOP BITS [1] +
[MORE...35]
Notes:
Changing characteristics
TTY characteristics cannot be adjusted or changed while the port or the device is busy.
The device has to be temporarily disabled (for example, pdisable command) before
proceeding and subsequently enabled again (using the penable command) before use.
Instructor Notes:
Purpose — Show how a terminal device can be changed.
Details — This is normally done to modify the settings of a terminal so that it works better
(or at all) or to change some attributes, for example to enable the terminal for login. The
graphic shows the characteristics of tty3, which is attached to serial adapter 0 (serial port
1) on a PCI RS/6000 system. This visual is not meant to show the TTY just added but
rather view the characteristics of a TTY on a PCI RS/6000 system.
Before a terminal can be changed, it must be disabled (see the pdisable command later in
this unit).
Additional Information —
Transition Statement — Having set up the terminal in the operating system, we will now
look at how to set up the terminal device itself.
AP
IBM 3151 Setup Menus (1 of 2)
Notes:
Example
The example shows the settings for the UK-English AIX Multiuser Enhancement
Cartridge to work with AIX 5L. The menus appear different depending on the cartridge.
A cartridge is not necessary to operate in US-English mode.
To access the setup menus on an IBM 3151 press <Ctrl+Setup>. Use the cursor keys
to move between fields and the space bar to toggle values. To go to the next menu
press the <Send> key.
Instructor Notes:
Purpose — Show the terminal setup menus for the IBM 3151 terminal.
Details — Every ASCII terminal has setup menus. They are all different depending on the
cartridge that is installed in the TTY, or the lack of one. To have the IBM 3151 operating in
the native US mode you wouldn't need a cartridge. The menus are invoked in different
ways depending on the above factor. The example shown is for an IBM 3151 with a UK
3151 cartridge at the back of the terminal.
Whatever the terminal, it has to be “told” what the port on the computer is trying to do. For
example, at what speed is the data expected to arrive/depart the computer?
On the ibm315x terminals, the pcmcia-type cartridge provides some setup. Remember to
tell the students to power-off the terminal BEFORE inserting or removing the cartridge. If
this is not done, there is a risk of damaging the contents of the cartridge.
One of the common reasons for terminals to suddenly cease working correctly is because
the user of the terminal just discovered the setup menus!
Someone may ask about attaching a printer to the auxiliary port and doing transparent
printing. This is supported on all systems except the 40P at this time.
Additional Information —
Transition Statement — The next page has the rest of the setup menus.
AP
IBM 3151 Setup Menus (2 of 2)
General Communication Keyboard/Printer Function
KEYBOARD PRINTER
General Code set ASCII Line Speed (bps) 19200
Enter RETURN Word Length (bits) 8
Return NEW LINE Parity NO
New Line CR Stop Bit 1
Send PAGE DTR Pacing OFF
Insert Character SPACE
NUM Message ON
Reset Terminal
[EMBKB]
Notes:
Function menu
Most modern ASCII terminals store their characteristics in non-volatile memory and
provide some setup menus to modify these characteristics.
The IBM 3151 ASCII terminal has different capabilities depending upon a cartridge
which is plugged in the back. This will provide different emulation modes and national
language support.
The FUNCTION menu provides options to Recall the previous values, Save the current
values, reset to the Default values, or Reset Terminal. To exit without updating the
values press <Ctrl+Setup> again.
Instructor Notes:
Purpose — Show the terminal setup menus for the IBM 3151 terminal.
Details —
Additional Information —
Transition Statement — Removing terminals can be problematic if you forget to disable
the device first. The next page illustrates how to properly disable and remove a terminal.
AP
Deleting TTYs
# smit rmvtty
Remove a TTY
[Entry Fields]
TTY tty0
KEEP definition in database yes +
Notes:
Instructor Notes:
Purpose — Show the students how terminals can be removed from the system.
Details — If you select to keep the definition, then the device will be put in the 'defined'
state. When you are ready to use the TTY again you would go back and Configure a
Defined TTY.
Additional Information —
Transition Statement — Before a terminal can be changed or deleted, it must be disabled.
AP
penable/pdisable
• To enable terminals, run the penable command:
penable [-a] [device_name]
Notes:
by init. If this respawning takes place too often, the message TTY respawning too
rapidly is displayed on the console. Temporarily disable the TTY while you check and
repair the cabling.
AP Instructor Notes:
Purpose — Show how a terminal can be enabled or disabled.
Details — In AIX 5L, unless the terminal is disabled by pdisable, it cannot be removed or
permanently changed.
Additional Information —
Transition Statement — Let's look at some common TTY problems.
TTY Problems
• Incorrect terminal type/settings:
– Change attributes (SMIT)
– Terminal setup menu
– TERM variable/terminfo database
• Hung terminal (crashed program or cat binary file):
– From terminal:
• Try start key <ctrl-q>
• Reset terminal from setup menu
• Try interrupt, quit keys
• <ctrl-j> stty sane <ctrl-j> then log off/on again
– From another terminal:
• stty -a < /dev/ttyn
• Then, stty sane </dev/ttyn
or
• kill -9 pid_of_login_shell
© Copyright IBM Corporation 2005
Notes:
Questions to ask
When approaching a terminal problem, there are several issues to investigate:
- Can the system communicate with the terminal? Try the command
echo hello > /dev/ttyn and check if any output is sent to the TTY.
- Are cabling, power, brightness, contrast correct?
- Are there any processes running on the terminal? Verify this using the
fuser -u /dev/ttyn command.
These questions normally produce a resolution to the problem.
AP Things to try
Other things to try:
- <Ctrl+q> (release screen)
- <Ctrl+c> (kill current process)
- Power off, then power on the terminal
- Check the NVRAM setup
- Is there a getty process running on the device? If so, pdisable the TTY, then
penable it.
If the backspace key does not work correctly, it needs to be remapped. Use the stty
command to do this:
stty erase (press backspace key)
Instructor Notes:
Purpose — List some of the problems that you may face when working with serial devices.
Details — When approaching a terminal problem, there are a number of questions that
must be asked. Both the graphic and the student notes provide some things to try in the
event of a 'non-working' TTY.
The student notes briefly mention the stty command. This command is used to set or
display TTY settings. To list the settings for a TTY, enter stty -a. This command is
covered in more detail in Q1316/AU16.
Additional Information —
Transition Statement — Documentation of TTYs in your environment is very important.
Let's look at this next.
AP
Documenting TTY Setup
• Always have a map of the concentrator boxes to the
physical terminals, so that port numbers can be easily
identified
• Run lscfg (if you have not already done so previously) and
keep a hardcopy of the output
Notes:
Documentation
Since the setup of serial devices is relatively complex and involves an amount of
manual labor, it is recommended that at least a map of where the devices exist, their
port numbers, and the specific settings (stty, etc) be drawn up.
This will make life a lot easier for the system administrator who looks after the system.
Instructor Notes:
Purpose — Highlight the value of documenting the terminal or serial line setup.
Details —
Additional Information —
Transition Statement — Let's review the topic.
AP
Checkpoint
1. True or false? If a device, like a TTY, is left for cfgmgr
to configure automatically, it picks up the default values
which might not be desirable.
2. True or false? If TTYs are connected via concentrator
boxes, they must all be connected in sequence on the
concentrator box otherwise they are not configured.
3. True or false? /dev/tty0 indicates that the TTY is
connected to port 0, /dev/tty1 to port 1 and so on.
4. What environment variable holds the terminal type for a
terminal?
Notes:
Checkpoint Solutions
1. True or false? If a device, like a TTY, is left for cfgmgr to
configure automatically, it picks up the default values which
might not be desirable. TTYs and other serial devices are not self-
configurable and so are not detected by cfgmgr.
Additional Information —
Transition Statement — Now, let’s do an exercise.
AP
Exercise Appendix B: Serial Devices
• Verify a terminal
• Remove a terminal
• Add a terminal
• Check terminal communication settings
• Change terminal characteristics
Notes:
Introduction
This exercise can be found in your Student Exercise Guide.
Instructor Notes:
Purpose — Optionally, do the exercise.
Details —
Additional Information —
Transition Statement — Now, let’s summarize the unit.
AP
Unit Summary
Notes:
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement —
References
Online AIX 5L V5.3 Guide to Printers and Printing,
Chapter 6. System V Printer Configuration
SG24-6018 Printing for Fun and Profit under AIX 5L
(http://www.redbooks.ibm.com)
Online AIX Commands Reference
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-1
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Unit Objectives
After completing this unit, you should be able to:
• List two advantages of the System V print subsystem
• List two advantages of the AIX print subsystem
• Switch between the AIX and System V print subsystems
• Describe the process of printing a file using the System V print
subsystem, including the following components:
– Print service daemon
– Printer configuration file
– Terminfo database
– Interface programs
– Slow and fast filters
• Configure a local printer using the System V print subsystem and
print to it
• Describe the process of configuring a remote System V printer
Notes:
AP Instructor Notes:
Purpose — Review unit objectives with students.
Details —
Additional Information —
Transition Statement — Let’s start by taking a high-level look at what’s changed with
printing in AIX 5L.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-3
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Administration
A new user (lp) and group (lp) have been added to support System V printing.
System V print administrators need to belong to the lp group.
AIX print administrators need to belong to the printq group.
Users who belong to the printq group can add printer devices which can be used by
either print subsystem.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-5
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — The purpose of this first visual is to give an overview of how the print
environment has changed with the addition of System V.
Details — Introduce students to the reasons for going to System V printing.
Additional Information —
Transition Statement — In order to choose which print subsystem to use, system
administrators need to evaluate their overall printing requirements. In the next visual, we’ll
take a brief look at the printing environments available under AIX 5L. Then, we’ll look more
specifically at the advantages and disadvantages of AIX and System V printing.
AP
AIX 5L Printing Environments
• Print directly to local printer device
• Print directly to a remote printer via a socket program
• System V print subsystem
• AIX print subsystem
• Infoprint Manager (or similar advanced print management
system)
Notes:
Introduction
The visual gives an overview of the different approaches that can be taken to printing
under AIX 5L. In the next two visuals, System V printing will be compared to the
traditional AIX print subsystem. The remainder of this unit focuses on using the System
V print subsystem.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-7
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
In this approach, you lose the ability to serialize (spool) print requests. Only one user
may print at a time. On the other hand, if a printer is being dedicated to one use, this
may be a good solution. Examples might be logging to a printer or printing checks.
AP Instructor Notes:
Purpose — The purpose is to give an overview of printing under AIX 5L, putting System V
and AIX in context. We also give a little advertisement for Infoprint Manger.
Details — More detail is provided in later visuals.
Additional Information —
Transition Statement — Now, let’s compare the advantages and disadvantages of
System V and AIX printing.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-9
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Compatibility
System administrators with experience in other UNIX variants that use System V
printing find it easy to manage printing under AIX’s System V print subsystem.
AP Security
Controlling user access to printers can be an important issue. For example, you might
need to limit access to the printer used to print checks. System V printing includes
built-in capabilities for restricting user access to certain printers. Using the AIX print
subsystem, the backend program must be customized to restrict user access.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-11
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — List two advantages of System V print subsystem.
Details — In summary, the main advantages of System V have to do with compatibility.
This makes it easy for system administrators from other UNIX variants to transition to AIX
and it drives availability of support for a larger number of printers on AIX.
System V also adds forms support and better security.
Additional Information — Directory-enabled printing is supported beginning with AIX 5L
V5.2. System V printing on AIX uses LDAP (Lightweight Directory Access Protocol) as the
directory service.
A directory is an ordered list of objects, including details about each object. Obvious
examples are phone books or library card catalogs. Directories are a type of database.
They differ from other databases in that accesses are mostly reads, with only occasional
writes. Directory protocols are optimized to facilitate a high-read environment.
Computer directories can be searched in many ways, making them a very powerful way to
store and manage information.
In the case of a printer directory, this might include searching for the name of a printer to
get its characteristics, searching for printers in a particular location, searching for printers
with particular features, and so forth. Directory enabled printing provides an easy way for
users to search for a printer that is close and has the features they require. If security or
other control features are made part of the directory, directory enabled printing facilitates
easier management by system administrators.
Transition Statement — Now, lets look at the strengths of the AIX print subsystem.
AP
AIX Print Subsystem: Advantages
• Powerful and flexible printer drivers
• System management tools:
– Limits fields and options validation
– Easy printer customization
– Single step print device and queue creation
• Customizable spooling subsystem
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-13
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
AP Instructor Notes:
Purpose — List advantages of AIX print subsystem.
Details — In summary, the main advantages of AIX printing have to do with flexibility and
ease of use. AIX printing is tightly integrated into SMIT and the Web-based System
Manager. Also, System V is not yet mature on AIX, although system management features
will be enhanced in future releases.
Additional Information —
Transition Statement — Now let’s look at how the two print subsystems are packaged
and installed.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-15
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Software Packaging
• Both print subsystems are installed as part of BOS
installation
• AIX print subsystem is enabled by default
• System V print subsystem filesets:
– bos.svprint.rte
– bos.svprint.fonts
– bos.svprint.hpnp
– bos.svprint.ps
– bos.terminfo.svprint.data
– bos.msg.en_US.svprint
• AIX print subsystem filesets:
– bos.rte.printers
– printers.*
© Copyright IBM Corporation 2005
Notes:
AP Instructor Notes:
Purpose — Describe how the two print subsystems are installed.
Details —
Additional Information —
Transition Statement — You can switch between System V and AIX printing.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-17
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Either the AIX print subsystem or the System V subsystem can be active, but not both
at once.
Status
Use SMIT, the Web-based System Manager, or the switch.prt -d command to
display the active print subsystem.
Switching
Use SMIT, the Web-based System Manager, or the switch.prt -s subsystem-type
command to switch subsystems.
Step Action
Checks for active print jobs. If there are, exits with error message:
1.
All print jobs must be terminated.
2. Stops the qdaemon, writesrv, and lpd daemons.
Modifies /etc/inittab so that the AIX daemons will not be started on the
3.
next boot and the System V daemon will be started on next boot.
Disables AIX printing SMIT menus as much as possible (some AIX
4. printing menus are removed; others give an error message if you try to
use them).
5. Switches Web-based System Manager plug-ins.
6. Changes lock files from AIX to System V.
7. Removes AIX links and adds System V links for the common commands.
8. Launches the System V print daemon (/usr/lib/lp/lpsched).
Step Action
Checks for active print jobs. If there are, exits with error message:
1.
All print jobs must be terminated.
2. Stops lpsched using the lpshut command.
Modifies /etc/inittab so that lpsched will not be started on the next boot
3.
and the AIX daemons will be started on next boot.
4. Enables AIX printing SMIT menus.
5. Switches Web-based System Manager plug-ins.
6. Changes lock files from System V to AIX.
7. Removes System V links and add AIX links for the common commands.
8. Launches the AIX print daemons.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-19
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
User submits job using enq or qprt when System V printing is active
If a user submits a job using the AIX print commands when the System V print
subsystem is active, the user will receive this error message:
Cannot awaken qdaemon (request accepted anyway).
If the AIX print subsystem is reactivated, the jobs are queued and print.
AP Instructor Notes:
Purpose — Provide details about how to switch between print subsystems.
Details — It is not expected that system administrators will be switching between print
subsystems on a regular basis, but it is good to understand how to do it and what happens.
You do not need to lecture through each step of switching, but you should discuss what
happens to disabled queues or printers when switching and what happens to jobs
submitted via enq when the System V subsystem is active.
Additional Information —
Transition Statement — The AIX print subsystem and the System V print subsystem
share a number of commands, but the functionality and option flags are somewhat
different. In the next visual, we’ll look at how AIX switches between the different versions of
these commands.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-21
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Both print subsystems share a number of commands, but command behavior and
option flags differ for the same command, depending on which subsystem is active. AIX
handles this by linking commands from /usr/bin to either /usr/aix/bin or /usr/sysv/bin.
AP man pages
The man page for each common command includes information about both versions of
the command. You need to make sure you are reading the correct part of the man page
for the print subsystem you are using.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-23
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how the two versions of common print commands are managed and
how to locate the correct version in the man pages. Emphasize this point: it’s very easy to
forget and just start reading the man page, however there are some important differences
between how these commands works in the two different systems.
Details —
Additional Information —
Transition Statement — Now, we’re ready to take a close look at how the System V print
subsystem operates.
AP
System V Printing Overview
lp or lpr
command
prin
ter
terminfo init
ial iza
database tion interface
program spool directory
fast filters
default optional
fast filter fast filter
printer device
Notes:
Introduction
This visual provides an overview of the System V printing process. In the following
pages, we provide additional details.
lpsched
lpsched is the print service daemon. It is started at boot time from the /etc/inittab file if
the System V print subsystem is active.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-25
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
terminfo database
The terminfo database contains data describing characteristics of different printer
types. This data is used in two ways. lpsched uses the data to determine if the job can
be printed. Later in the process, the interface program uses this same information to
initialize the printer.
AP Filters
Filters are used by the System V print subsystem to perform three functions:
- Converting file content
This could include tasks such as adding carriage returns to line feeds, mapping one
set of control characters to another set, and so forth. For example, converting a
simple text file to PostScript so that it can be printed by a PostScript printer.
- Interpreting special print modes requested by the user
This could include print modes such as landscape page orientation, reverse page
order, and so forth.
- Detecting printer faults.
There are two types of filters:
- Slow filters are filters that incur a lot of overhead and do not need to be connected to
the printer while they run. lpsched runs slow filters in the background so that the
printer is not tied up while they perform file conversion.
- Fast filters interact directly with the printer. They can control the printer and receive
status back from the printer. Some fast filters also perform file conversion tasks like
slow filters.
Filtering
lpsched determines which filters must be used, based on:
- Printer type
- Content of the file to be printed (as specified by the user)
- Types of content the printer will accept (from the printer configuration file)
- Any special mode options requested by the user
- Capabilities of the available filters (registered using the lpfilter command)
lpsched may decide to use a combination of several filters. Slow filters are run directly
by lpsched. Fast filters are run by the interface program, as directed by lpsched.
Several filters may be piped together to achieve the desired file format.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-27
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Interface program
The interface program is a shell script that manages the printer. When you create a
System V printer, you specify which interface script you wish to use. Two interface
scripts are provided with the System V print subsystem or you can write your own
interface scripts. In addition, some printer manufacturers provide interface scripts
specifically for their printers.
The interface script performs the following tasks:
- Initializes the printer port, if necessary, and printer hardware using terminfo data
- Invokes the fast filter to print a banner page, if required
- Invokes the fast filter to print requested number of copies of the file to be printed
Logging
lpsched is responsible for monitoring job status and updating files in the log directory.
AP Instructor Notes:
Purpose — This visual gives an overview of the entire printing process.
Details — Walk students through the process. Let them know that this is an overview.
We’re going to provide more details for most of this process.
Additional Information —
Transition Statement — In the next visual, we’ll define some terms.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-29
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
System V Terminology
Term Description Examples
Printer device The device driver this printer queue /dev/lp01
uses
System V printer The printer queue myprinter
Notes:
Introduction
One of the most confusing things about System V printing is the terminology. For
example, many different things are referred to as types. The table in the visual
describes some System V terms. The lpadmin command at the bottom of the visual
shows how these terms are used when defining a System V printer.
Printer device
The term printer device usually refers to the actual printer device driver. Printer devices
are created using mkdev and associated with a System V printer using the
-v device_name flag to the lpadmin command.
In the example, the printer myprinter is configured to use printer device /dev/lp01.
AP System V printer
The term System V printer, or even just printer by itself, usually refers to the printer
queue, which is defined using the -p printer_name flag to the lpadmin command.
In the example, the System V printer is named myprinter.
Printer type
The printer type associates a printer to an entry in the terminfo database. Use the
-T printer_type flag to lpadmin to specify the printer type. The information in the
terminfo database is used by the interface program to initialize the printer.
In the example, the printer type is PS, which is one of several terminfo entries for
PostScript printers.
Content type
The content type identifies what kind of content the printer can handle. This can be a list
of content types. For example, some laser printers can accept both PostScript and
Printer Command Language (PCL). Use the -I content_type flag to lpadmin to
specify printer content types.
In the example, the content type is postscript.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-31
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Flag Description
Copy the script specified by interface_path (full
-i interface_path path name) and use it as the interface script for this
printer.
Copy the interface script already defined for
-e printer_name
printer_name and use it for this printer.
Copy the file model in /usr/lib/lp/model and use it
-m model
as the interface script for this printer.
In the example, lpadmin copy the /usr/lib/lp/model/PS interface script to be used for
myprinter.
Class
Printers can be grouped into classes. A class is an arbitrary group of printers. If a user
submits a job to a class of printers, the print service prints it on the first available printer
that can handle the job. Printers are added to a class using the
-c class_name flag to lpadmin. If the class does not exist, it is created.
In the example, myprinter is added to class bldg5.
AP Instructor Notes:
Purpose — Explain the following System V printer terms: printer device, printer, printer
type, content type, interface, and class.
Details —
Additional Information —
Transition Statement — Let’s take a minute to review what we’ve covered so far.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-33
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Let's Review 1
Notes:
AP Instructor Notes:
Purpose — Provide students with a chance to review and consolidate what’s been
covered so far.
Details —
Additional Information —
Transition Statement — Next, let’s cover how to add a System V printer to the print
service.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-35
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Creating a System V printer is done in two steps:
- Creating the printer device
- Creating the System V printer
AP Instructor Notes:
Purpose — Identify the basic steps in adding a printer.
Details — No need to spend much time here.
Additional Information —
Transition Statement — The first step is creating the device.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-37
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Printer devices can be used by either print subsystem. Printer devices may be added
using SMIT, the Web-based System Manager, or the command line using mkdev.
Connecting printers
Local printers may be connected in one of two ways: serial or parallel.
Network-attached printers may be connected directly to the network, or they may be
connected to a remote print server host that is accessed over the network.
AP between your printer and the printer device driver software. You should chose a printer
device that is:
- A similar kind of printer, for example: laser, ink jet, and so forth
- Similar in speed to your actual printer
In the example in the visual, lp0 has been configured using the parallel port and the
Lexmark Optra Color 1200 printer device driver; however, the physical printer is actually
a Canon Bubble Jet. These printers are similar enough that the printer device operates
correctly for the Canon printer.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-39
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review some basics on printer devices
Details — Creating devices should be a review for this audience. They will get a chance to
create a printer device in the exercise.
Students should be aware that an exact match between physical printer and printer device
is usually not necessary.
Also, most of the attributes shown using lsattr or splp are not used when printing from
the AIX or System V print subsystem. Further, if you are printing directly to the device, you
can override these attributes by putting the printer device in pass though mode using splp.
Additional Information —
Transition Statement — The next step in creating a System V printer is using lpadmin,
which creates the printer configuration file.
AP
Creating a Local System V Printer
# lpadmin -p myprinter -v /dev/lp0 -T bj-300
Print server
Printer configuration file daemon
(lpsched)
Notes:
Introduction
System V printers are added, or modified, using lpadmin, SMIT or the Web-based
System Manager. This visual shows a printer created using lpadmin.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-41
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the contents of the printer configuration file.
Details —
Additional Information —
Transition Statement — In this example, we set the printer type to bj-300. Let’s take a
closer look at what the printer type is.
AP
Printer Types
• terminfo source for printers:
/usr/share/lib/terminfo/svprint.ti
• Compiled terminfo file for a Canon Bubble Jet
(printer type bj-300):
/usr/share/lib/terminfo/b/bj-300
• To compile terminfo source:
# tic svprint.ti
• To view bj-300 terminfo entry:
# infocmp bj-300 Print server
daemon
ing
s creen (lpsched)
J ob
Printe
r initiali
terminfo zation Interface
database program
Notes:
Introduction
System V printer types are defined in the terminfo database. Printer types are similar in
function to the virtual printer definition files used by the AIX print subsystem. Unlike AIX
virtual printer definitions, one terminfo entry may be used for a number of different
System V printers.
Purpose
Printer type information is used by lpsched to perform job screening and by the
interface program to initialize the printer.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-43
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Organization
Terminfo entries are binaries which are compiled from terminfo source files. The
database resides at /usr/lib/terminfo. By convention, source files reside in
/usr/share/lib/terminfo and are named *.ti. For example, the source file for the System
V printer types supplied with AIX 5L is svprint.ti. Each compiled terminfo entry is a
separate file which resides in /usr/lib/terminfo/X, where X is the first letter of the
terminfo name. For example, the terminfo entry for printer type bj-300, is
/usr/lib/terminfo/b/bj-300.
Commands
Use the tic command to compile a terminfo source file. Use infocmp to display a
terminfo entry, or to compare two entries.
No printer type
If you do not specify a printer type, it defaults to unknown. Depending on how you are
using the printer, this may not be a problem. It does mean that:
- Your printer is not initialized by the interface program.
- Any -o options on the lp command line (such as -o cpi, -o width, -o length,
and so forth) cannot be used
- Some simple control characters may not function correctly
The exception to this would be if you have a printer specific interface script which
generates the command sequences internally in the script without consulting terminfo.
More information
If you believe that you need to create a new terminfo entry for your printer, see Printing
for Fun and Profit under AIX 5L (Redbook), Appendix C. Virtual printer colon files and
System V terminfo.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-45
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe what a printer type is and how to choose one for your printer.
Details — Usually choosing a printer type is easy. Choose your model from the model.stz
file or the Web-based System Manager, or if you can’t find your model, search for a similar
printer.
Additional Information —
Transition Statement — Next, let’s take a look at printer interface programs.
AP
Interface Programs
interface
program
fast filters
default optional
fast filter fast filter
printer device
Notes:
Introduction
The interface is responsible for performing the functions as listed in the visual:
- Initialize the printer port using stty
- Initialize the printer hardware using commands from terminfo
- Print the banner page
- Print copies of the print job using a filter
- Handle any printer errors from the filter and return exit status (success or failure)
back to lpsched
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-47
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
lpsched
lpsched calls the printer’s interface program for local print requests. lpsched passes
information to the interface program. Some of the information sent to the interface
program includes:
- Terminfo entry to use
- Fast filter to use
- Character set (optional)
- Number of copies
- Files to print
Note: Interface programs are sometimes mistakenly referred to as print drivers.
Administrative concerns
When a printer is created, a copy is made of the interface script for that printer. For
example, if printer myprinter is defined to use the PS interface, the
/usr/lib/lp/model/PS file is copied to /etc/lp/interfaces/myprinter.
If you need to modify a printer’s interface script, modify the copy in /etc/lp/interfaces. If
you want to change the template for all future printers created, modify the source file.
More information
If you need to create a custom interface script, you can use the standard or PS script as
a template. For more information, refer to: Printing for Fun and Profit under AIX 5L
(Redbook), Chapter 4. System V Advanced Printing.
AP Instructor Notes:
Purpose — Describe the purpose of the interface program and how to choose an interface
program for your printer.
Details —
Additional Information —.
Transition Statement — When a job is submitted to a queue, request files are created in
the spool directory.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-49
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Each time a user sends a print job to a printer, the print service creates one or more files
in the spool directory (/var/spool/lp/tmp/<hostname>) that describe the job request.
These files remain in this directory while the job is in the queue waiting to be printed.
When the job is finished printing, information in the files is appended to the log file
/var/lp/logs/requests and the files are removed from the spool directory.
AP Copying files
Normally, if you send a file to the print service using the lp command, the print service
does not copy your file to the spool directory, but instead just reads from the original.
This means that if you delete the original copy after you submit the print request, but
before it is printed, the print request fails. In some circumstances a copy is created. It is
also possible to request that the print service create a copy of the print file in the spool
directory before printing. Files are copied under the following circumstances:
- The job is submitted using lp -c. (The default for the lp command is NOT to copy.)
- The job is submitted using lpr, without the -s flag. (The default for the lpr
command IS to copy.)
- The job is received from a remote system. (In this case, the file does not exist on the
print server system, and so must be copied.)
- Copying files has been enabled as the default by issuing the
lpadmin -O copy command.
Note: This flag sets the value of the copy-files parameter in the /etc/default/lp file to
on.
Files in /var/spool/lp/tmp/<hostname>
This directory contains the following files:
File Description
This file is used to keep track of the next job
.SEQF
number.
These files are the actual request files, where X is
the job number.
X-0
Notice that the printer name is not part of the
request file name, but rather is stored within the file.
If files are being copied to the spool directory, there
X-N may be additional files (X-1, X-2 and so forth) that
contain the actual data to be printed.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-51
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Example
In the example in the visual, job 10 was created without copying while copying was
requested for job 11. Excerpts from the request files are shown in the visual. In the
request file:
- C indicates the number of copies requested.
- D indicates the name of the printer.
- F indicates the name of the file to print.
- O indicates additional information. In this case, the locale and the name and size of
the original file (flist=).
Notice that for job 11, /var/spool/lp/tmp/kca48/11-1 is the file to print. This would be a
copy of the original file, in this case: /etc/passwd.
AP Instructor Notes:
Purpose — Describe the request and log files and copying issues.
Details —
Additional Information — The Guide to Printers and Printing describes different paths for
the spool directories (/usr/spool/...). The System V directories are linked extensively.
/usr/spool is linked to /var/spool.
Also, /etc/lp/logs is a link to /var/lp/logs. And /var/spool/lp/admins/lp is a link to /etc/lp.
The Guide to Printers and Printing says the log is /usr/spool/lp/logs/requests. This file
didn’t exist on the system used for development. Instead the log file was
/var/lp/logs/requests as noted in the student notes.
Currently skulker does not address pruning the System V request log.
Transition Statement — Now that we’ve covered the basic printing process, let’s take a
look at the commands used to manage System V printers.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-53
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Managing Printers
• Start printing:
– enable printer
• Stop printing:
– disable [-c] [-r reason] [-W] printer
• Start queuing:
– accept printer
• Stop queuing:
– reject [-r reason] printer
Notes:
Introduction
The System V print subsystem allows you to control queueing and printing separately.
enable / disable
The enable and disable commands control whether jobs in the queue are printed. For
example, if you need to perform service on the physical printer, or need to mount a
form, use disable to stop printing. This allows users to continue to submit jobs, but
nothing is printed while you perform service on the printer. When service is complete,
use enable to restart printing and jobs from the queue are again printed.
AP disable syntax
The table shows options to disable.
Option Description
Cancel any requests currently printing on any of the
-c
designated printers. Cannot be used with -W.
Assign a reason for disabling the printers. The
-r reason reason is reported by lpstat -p. reason must be
quoted if it includes spaces.
Wait for any currently printing job to complete before
-W
disabling printers. Cannot be used with -c.
accept / reject
The accept and reject commands control whether the printer adds print requests to
the printer queue. For example, use reject to stop queueing for a printer if you need to
change queue parameters. Any jobs remaining in the queue are printed. When the
queue is empty, make the desired changes and then use accept to restart the queue
using the new parameters.
reject syntax
The table shows options to reject.
Option Description
Assign a reason for rejecting requests. The reason
-r reason is reported by lpstat -a. The flag reason must be
quoted if it includes spaces.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-55
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the commands used to control System V printers.
Details — The main idea here is the difference between queueing jobs (accept/reject)
and printing jobs (enable/disable).
Additional Information —
Transition Statement — Now, let’s take a look at the commands available to users to
utilize the print service.
AP
Using the Print Service
• Submit print jobs:
– # lp -d dest [print-options] file_list
• Modify print jobs:
– # lp -i request-id [print-options]
• Cancel print jobs:
– # cancel request-id-list
– # cancel printer
– # cancel -u user-list [printer-list]
• Check status:
– # lpstat [flags] [object-list]
Notes:
Introduction
This visual summarizes the commands (accessible by any user) to utilize the System V
print service. Refer to the respective man page for detailed information on the many
options available.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-57
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
started printing, the changes are accepted, if the printer can handle them. If the job has
started printing, it is stopped and restarted from the beginning. If the job has finished,
the change is rejected.
Command Description
Cancel the jobs specified. You can get the
cancel request-id-list
request-ids using lpstat.
The user’s currently printing job for the requested
cancel printer-list
printer will be cancelled.
Cancel all jobs for specified users. If printer-list
cancel -u user-list
is specified, only cancel the users’ jobs for the
[printer-list]
listed printers.
Check status
Use lpstat to check status. There are many options. Several of the most useful ones
are shown in the table. Options can be combined to get the output you need. If the list
argument is omitted, lpstat reports on all of that type of object. If you have many
printers, omitting list may make the output of lpstat unreasonably long.
Option Description
Reports the status of print requests. list can be
-o [list] [-l] printers, classes, or request-ids. if -l is used,
additional status for each job is reported.
Reports printing status:
• Enabled/disabled
• What is currently printing
-p [list] [-D]
[-l] • Device status (available/defined)
With -D, a brief description of each printer is
included. With -l, a full description is included. list
is a list of printers.
Reports queue status (accepting/rejecting). list
-a [list]
can be printers or classes.
-u [list] Reports status for users in list.
Reports total status (similar to combined output of
-t [list]
-o, -p, and -a).
AP Instructor Notes:
Purpose — Summarize the System V user commands.
Details — Let students know that we will not be going through all the options for these
commands. This is an overview to familiarize them with the commands.
Additional Information —
Transition Statement — Let’s take time out for another review.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-59
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Let's Review 2
Notes:
AP Instructor Notes:
Purpose — Another review
Details —
Additional Information —
Transition Statement — Now that we’ve covered the basics, let’s look a couple of
advanced topics, beginning with using filters.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-61
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Using Filters
• Purpose:
– Convert file content
– Interpret special print modes
– Handle printer faults
• Filter types:
– Slow filters run in background
– Fast filters interact with printer
• Using filters:
– Filters must be registered
– Printer content must be set
– File content must be set
• Managing filters:
– Filter definition files:
/etc/lp/fd/*.fd
– Registering a filter:
# lpfilter -f filter_name -F filter_definition_filename
– Listing filters:
# lpfilter -f [ filter_name | all ] -l
– Removing a filter:
# lpfilter -f filter_name -x
© Copyright IBM Corporation 2005
Notes:
Purpose
We’ll start by reviewing the purpose of using filters. Filters are used by the System V
print subsystem to perform three functions:
- Converting file content:
For example, converting a simple text file to PostScript so that it can be printed on a
PostScript printer.
- Interpreting special print modes requested by the user:
This could include print modes such as landscape page orientation, reverse page
order, and so forth.
- Detecting printer faults:
Printer faults include such things as printer out of paper or printer off line.
AP Filter types
There are two types of filters:
- Slow filters are filters that incur a lot of overhead and do not need to be connected to
the printer while they run.
- Fast filters interact directly with the printer. They can control the printer and receive
status back from the printer, Some fast filters also perform file conversion tasks like
slow filters.
Using filters
In order for filters to work correctly, a number of things need to be taken care of:
- Filters must be registered:
While the System V print subsystem includes a number of useful filters, the print
service will not use them until they are registered. Use lpfilter to register a filter.
- Printer content must be set:
The printer content types must be set correctly
(using lpadmin -I content_type_list) so that the print service knows what types
of files the printer can accept without filtering. If not set, printer content type defaults
to simple.
- File content must be set:
If a print job contains content other than simple, the file content must be set when
the print job is submitted (using lp -T content_type) so that the print service
knows what the file’s content type is. If not set, the print service assumes the file
content is simple.
Item Description
Command File name of the filter program
Input types Content this filter accepts as input
Output types Content this filter can provide as output
Printer types Printer types that may use this filter
Normally, a filter would work with all printers that accept the
Printers output type, however you can restrict which printers may use a
filter if this is desirable
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-63
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Standard filters
The AIX 5L System V print subsystem includes a number of filters. Filter definitions for
these filters are /etc/lp/fd/*.fd.
Managing filters
Use the lpfilter command to register a filter. For example, the dpost filter is used to
convert troff files to PostScript. The dpost filter definition file is /etc/lp/fd/dpost.fd. To
register the dpost filter, enter:
# lpfilter -f dpost -F /etc/lp/fd/dpost.fd
Registered filter definitions are stored in the /etc/lp/filter.table file, however, you should
not directly edit this file. Use lpfilter to manage the registered filters.
If you wish to change how a filter is used, edit the filter definition file and re-enter the
lpfilter command.
To list a registered filter (for example to list the dpost filter):
# lpfilter -f dpost -l
To list all registered filters:
# lpfilter -f all -l
To remove a registered filter (for example to remove the dpost filter):
# lpfilter -f dpost -x
AP Instructor Notes:
Purpose — Describe the purpose of print filters. Describe how to register, list and remove
print filters.
Details — We start with a review of the purpose of filters and filter types.
Additional Information — Why are filters necessary in UNIX printing? In PC-based
printing, printer device drivers provide a standard API and any application can output
directly to any printer installed in the system. In UNIX printing, each application must
provide their own printer-specific output. Print filters hide the printer-specific details from
the applications.
Transition Statement — Next, let’s look at another System V feature: printing using forms.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-65
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Using Forms
• Registering forms with the print service
• Requesting a form for a print job
• Alerting the operator to mount a form
• Mounting a form
• Unmounting a form
• Controlling access to forms
• Displaying information
Notes:
Introduction
A form is a preprinted sheet of paper which can be loaded into a printer in place of plain
paper. Some examples are company letterhead, checks, invoices, receipts, and so
forth.
The System V print subsystem facilitates printing to forms by providing the functions
shown in the visual. We summarize the procedures for using forms here.
Note: The print service does not position print output on a form; this is the responsibility
of the application.
AP character pitch, alignment pattern, and so forth. The alignment pattern is sample output
that can be used to correctly position the form when it is mounted. Once you have
created the definition file, register the form using:
# lpforms -f form_name -F form_definition_file
Option Description
Send alerts to user lp when form_name is
requested. alert_type can be:
mail: Send mail to user lp.
write: Send message to the terminal where lp is
-A alert_type logged in.
none: Do not alert.
shell-command: Execute named command.
quiet: Do not send any more messages for current
form request.
Send alerts after number of form requests have
-Q number
accumulated in the queue. Default is one.
Repeat alert every interval minutes. Default is
-W interval
zero, which indicates alerting once.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-67
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Mounting a form
Mounting a form lets the print service know that the specified form is now loaded onto
the printer. Any queued jobs using that form can now proceed. Use the following steps
to mount a form:
Step Action
Disable the printer:
1.
# disable printer_name
2. Physically load the form in the printer.
Inform the print service that the form is ready:
# lpadmin -p printer -M -f form_name [-a] [-o filebreak]
where:
-M -f form_name Informs print service that form_name is mounted.
-a Prints the alignment pattern (if defined in the form
3. definition file). The operator can then adjust the form
and press <Enter> for another alignment pattern. This
can be repeated as many times as needed to get the
alignment right. Type <q> to quit printing alignment
patterns.
-o filebreak Inserts a form feed at the end of each alignment
pattern. If not specified, no form feed is added.
4. Align the form, if required. (See -a option above.)
5. Physically load the form in the printer.
Enable the printer. Queued jobs for this form will now be printed:
6.
# enable printer_name
Unmounting a form
To unmount a form, follow these steps:
Step Action
Disable the printer.
1.
# disable printer_name
2. Physically remove the form from the printer.
Inform the print service that the form is removed:
3.
# lpadmin -p printer -M -f none
Enable the printer.
4.
# enable printer_name
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-69
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the process of using forms.
Details — This provides an overview of using forms. Actually, really the only thing not
covered is the details of the form description file.
Additional Information —
Transition Statement — In the next visual, we’ll take a look at the kinds of issues you
need to consider when adding a System V printer.
AP
Planning a Local System V Printer
• Printer name
• Printer device
• Printer type
• Class
• Content types and filters
• Alerts
• Banner pages
• Forms
• Access policy
Notes:
Introduction
This visual lists a number of issues which need to be considered when defining a local
System V printer.
Printer name
The printer name should make it easy for users to identify the printer. You can use any
name you wish, with the following restrictions:
- The name must be a valid file name for the file system you are using
- The name cannot begin with a dash (-), although a dash can be used in other
positions in the name
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-71
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Printer device
If you are configuring a local printer, you must decide what printer device driver to use.
If AIX or your printer manufacturer does not provide a printer device specific to your
printer, you can probably use a printer device for a similar printer.
Printer type
In general, it is not critical that you find an exact match for your printer model, just that it
be a similar kind of printer.
Class
Do you want to include this printer in an existing printer class or define a new class?
Classes can give users flexibility. By printing to a class of printers, any of which meet
their requirements, they may be able to get their job printed more quickly.
Alerts
When there is a problem with a printer, how should the print service alert the print
administrator? Printer alerts are configured on a per printer basis using the -A flag to
lpadmin. Refer to the lpadmin man page for complete details.
Forms
Do you require any special forms? If so, consider these questions:
- How should the print service alert the print administrator?
- Do you need to control access to any forms?
Banner pages
The System V print subsystem allows you to control the printing of banner pages. The
default is to print a banner page with every print job. Users can request no banner page.
The print service rejects this request unless enabled to allow skipping the banner using
AP the -o nobanner option to lpadmin. The table summarizes the relevant command
options.
Option Description
lpadmin -o banner Banners are required (default)
lpadmin -o nobanner Users are allowed to request that the banner not be
printed
lp -o nobanner Request print job be printed without a banner
Access policy
Do you need to control access to a printer? The System V print subsystem allows you to
control access to printers using an allow-list, a deny-list, or both. These lists can be
created using the -u allow:user-list or -u deny:user-list options to lpadmin and
function similarly to the cron.allow and cron.deny files. Refer to the lpadmin man page
for complete details.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-73
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the planning process for defining a local system V printer.
Details — This is mostly review, but a couple of topics have not been covered yet: alerts,
banner pages, and access policy.
Additional Information —
Transition Statement — The next three visuals provide an overview of network printing
using the System V print subsystem.
AP
System V Network Printing
• Print server:
– Serving print requests from remote clients using LPD
protocol (RFC 1179)
• Print client:
– Printing to remote LPD printers or servers
•Network attached printers running LPD
•Local printers on a server running LPD
• The lpNet daemon
• /etc/lp/Systems and lpsystem
• Printing to JetDirect-attached printers
Notes:
Introduction
This visual provides an overview of the network printing capabilities of the System V
print subsystem. More details about configuring a AIX system as a print server or print
client are provided in the next two visuals.
Print server
The System V print subsystem can be configured so that a locally attached printer on
your system (the print server) can be used to print requests from remote machines (the
print clients) which are running the LPD protocol as defined in Request for Comments
(RFC) 1179.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-75
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Print client
You can configure the System V print subsystem to print to any network destination that
supports LPD as defined in Request for Comments (RFC) 1179. A network destination
in this sense can be a:
- Printer (directly connected to the network) that is running LPD
- System (with locally attached printers) that is running LPD
lpNet
The lpNet daemon is used by both network printing clients and servers. lpNet is
automatically started by lpsched.
On client machines, lpsched sends the print request to lpNet for transmission to the
print server. No formatting or filtering is done on the client side.
On server machines, lpNet receives the remote print request and sends it to lpsched.
If the request can be printed, lpsched processes the print request as it would any local
request. Printer type, filtering for content and other formatting is all done on the server.
JetDirect-attached printers
The System V print subsystem also supports printing to printers that attach to the
network using the Hewlett-Packard JetDirect interface. Configuring the print subsystem
for JetDirect printers is not included in this class. Refer to Printing for Fun and Profit
under AIX 5L (Redbook) for additional information about this capability.
AP Instructor Notes:
Purpose — Describe the network printing capabilities of the System V print subsystem.
Details —
Additional Information — We are only covering LPD remote printing. JetDirect is not
covered.
Transition Statement — In the next visual, we’ll discuss the steps to configure a network
print server.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-77
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Configuring a network print server is done in two steps:
1. Registering the remote systems (clients) allowed to use the server
2. Granting or denying access to individual remote users or groups of remote users
AP lpsystem syntax
# lpsystem [-T timeout] [-R retry] [-y comment] system_name
# lpsystem -l system_name
# lpsystem -r system_name
The table explains the usage of the various options.
Option Description
system_name This parameter specifies the name or IP address of
the remote system. system_name can be * to allow
access from any system.
-T timeout This option specifies the length of time the print
service will allow a network connection to be idle. If
idle time exceeds timeout, the connection is
dropped. It will be re-established if there are more
requests. timeout can be:
• n: never timeout. This is the default.
• 0: timeout immediately.
• N: timeout after N minutes.
-R retry This option specifies the length of time to wait to
re-establish a connection if the connection was
abnormally dropped. retry can be:
• n: do not retry until there is more work.
• 0: try to reconnect immediately.
• N: try to reconnect after N minutes. The default is
10.
-y comment This option allows you to add a free form comment.
The comment must be quoted if it contains spaces.
-l system_name This option lists the parameters defined for
system_name, including any comment.
-r system_name This option removes system_name from the list of
registered systems.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-79
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Syntax
# lpadmin -p printer -u allow:user_list | -u deny:user_list
The table shows the syntax for this usage of the lpadmin command.
Option Description
-p printer Specifies the name of the printer on the server.
-u allow This parameter specifies the users who are allowed
access.
-u deny This parameter specifies the users who are denied
access.
user_list This is a comma or space separated (must be
quoted if space separated) list of users to allow or
deny. The list can include any of the following:
• userID: a user on the local system
• system_name!userID: a user on system_name
• system_name!all: all users on system_name
• all!userID: a user on all systems
• all!all: all users on all systems
AP Instructor Notes:
Purpose — Describe the process of configuring a network server.
Details — Discuss the options to lpsystem and lpadmin.
Additional Information —
Transition Statement — Now, let’s look at configuring a client.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-81
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Notes:
Introduction
Configuring your system to print using a remote LPD printer is done in three steps:
1. Register remote system (the printer or print server) on the client
2. Define the printer queue on the client
3. accept and enable the printer queue on the client
Of course, the print server or network attached printer must already have been
configured to accept your requests.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-83
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe how to configure a print client.
Details —
Additional Information —
Transition Statement — The next two visuals provide a summary of the System V
commands. First the administrative commands.
AP
System V Administrative Command Summary
Command Description
accept Permits jobs to be queued for specified destination (printer or
class).
reject Prevents jobs from being queued for specified destination.
enable Activates the named printers so they will print from the queue.
disable Deactivates named printers.
cancel Cancels print jobs.
lpadmin Create or modify printer configuration.
lpfilter Manages filters.
lpforms Manages forms. (Use lpadmin to mount a form.)
lpmove Move print jobs to another destination.
lpsched Start the print service.
lpshut Stop the print service.
lpsystem Register remote systems with the print service.
lpusers Manages default priority and priority limits for printer service users.
lpstat Report print service status.
© Copyright IBM Corporation 2005
Notes:
Introduction
This visual provides a brief summary of all the System V administrative commands. A
summary of the options to lpadmin is included on the next page. Refer to the relevant
man page for complete information.
For a comparison of the commands for the System V print subsystem and the AIX print
subsystem, refer to:
Printing for Fun and Profit under AIX 5L (Redbook)
Appendix A. Print Tasks and Commands
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-85
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
lpadmin syntax
The most frequently used administrative command is lpadmin. The following table
summarizes the command syntax. Again, see the man page for a complete description.
Adding or changing a printer:
# lpadmin -p printer [options]
Removing a destination (printer or class):
# lpadmin -x destination
Option Description
Specifies the name of the printer. When adding a
printer, you must specify either:
-p printer
-v (for a local printer) or
-s (for a remote printer)
Used to configure a local printer. Associates a
-v device
device with a printer.
Used to configure a remote printer. server
specifies the name or IP address of the remote
-s server print server. This could be a remote system or a
[!server_printer_name] printer directly connected to the network.
server_printer_name specifies the name of the
printer queue on the server.
Remove destination (which can be a printer or a
-x destination
class) from the print service.
Used to specify the printer interface. Only one of
these options can be specified. If none of these
are specified, the standard interface is used.
-i interface specifies a full file path.
-i interface
-m model -m model specifies one of the supplied interface
-e printer_name programs (a file in /usr/lib/lp/model).
-e printer_name directs lpadmin to copy the
interface used for printer_name to the printer
being added or changed (specified with -p
printer).
Identifies an entry in the terminfo database, which
-T printer_type
is used by the interface program and some filters.
Identifies one or more types of content that this
-I content_type_list printer can handle without filtering. If not specified,
default is simple.
AP Option Description
Add printer to class. Create class if it does not
-c class
already exist.
Remove printer from class. If printer is the last
-r class
member of class, then remove class.
-O copy specifies that files should always be
copied to the spool directory. -O nocopy
specifies that files should not be copied to the
spool directory unless requested by user or
-O {copy|nocopy} otherwise required (for example: a remote print
request or input piped to the lp command).
This flag sets the value of the copy-files
parameter in the /etc/default/lp file to on (copy)
or off (nocopy).
Specifies the type of alert used to notify the
administrator of printer faults. The default is to
-A alert_type send the alert message via mail.
[-W minutes] -W minutes specifies the interval between alerts.
0 or once is the default, which indicates sending
only one alert for a fault.
Mount form_name on printer.
-o filebreak specifies that a form feed be
-M -f form_name [-o filebreak]
inserted between each copy of the alignment
pattern.
Allow or deny the forms in form_list to be
-f allow:form_list
printed on printer. By default, all forms are
-f deny:form_list
denied.
-u allow:user_list Allow or deny the users in user_list to access
-u deny:user_list printer.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-87
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the various System V administrative commands.
Details — Students can use these tables as a quick reference if they can’t remember
which command to use.
Additional Information —
Transition Statement — The next visual provides a summary of user commands.
AP
System V User Command Summary
Command Description
cancel Cancels print jobs.
lp Submit a print job to a printer
lpstat Report print service status.
Notes:
Introduction
This visual provides a brief summary of the System V user commands. Refer to the
relevant man page for complete information.
cancel
The cancel command is used to cancel print jobs, as shown in the table. Regular users
can only cancel their own jobs.
lpstat
The lpstat command displays information about the current status of the line printer.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-89
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
lp syntax
Use the lp command to submit jobs to the System V print service. There are many
options. The following table summarizes the most commonly used options.
Options can be entered in any order, however the files to be printed must occur at the
end of the command line.
# lp -d destination [options] files
Option Description
Specifies the printer destination (printer or class)
-d destination
where the job is to be printed.
Specifies one or more files to be printed. Files are
files printed in the order specified. Use - to specify
standard input.
Copy files to spool directory before printing.
-c Default is not to copy unless lpadmin -O copy
has been used.
-n number Print number copies. Default is one.
Specifies content type of the file. If the requested
printer destination cannot handle this content, the
-T content_type print service looks for a filter to convert the file. If
no acceptable combination of filter/printer can be
found, the job is rejected.
Print the job on form form_name. If the requested
printer destination is not allowed to use this form,
the job is rejected. If the form is not mounted, an
-f form_name
alert is sent to the administrator. (How form alerts
are handled is configured by the lpform
command.)
-o specifies a printer-dependant list of options.
Supported options are defined by the printer type
-o options (terminfo entry). Options can include items such
as: page length, page width, line pitch, character
pitch, and so forth.
Send notification via mail when job has been
-m
printed. Default is no mail.
AP Option Description
Print the job according to the modes in mode_list.
This option may only be used if there is a filter
available to handle the requested modes;
otherwise the print job is rejected. The allowed
-y mode_list
modes are locally defined (in the filter definition
files). Modes can include such items as: reverse
order, landscape mode, print only selected page
numbers, and so forth.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Describe the various System V commands.
Details — Students can use these tables as a quick reference if they can’t remember
which command to use.
Additional Information —
Transition Statement — Checkpoint.
AP
Checkpoint
1. List two advantages of the System V print subsystem.
___________________________________________
2. List two advantages of the AIX print subsystem.
___________________________________________
3. What command is used to switch from AIX to System V
printing? __________________
4. lpsched uses information in _________ and _________ to
screen print jobs.
5. The interface program uses commands in _________ to
initialize the printer.
6. _________ are used to convert file content.
7. Use the _________ command to manage filters.
8. _________ is used to create or modify a System V printer.
9. _________ is used to create a printer device.
© Copyright IBM Corporation 2005
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-93
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Review the unit.
Details —
Checkpoint Solutions
1. List two advantages of the System V print subsystem.
Compatibility, Availability of interface programs, Security, Support for
Forms, Standard PostScript filters, Long term direction
2. List two advantages of the AIX print subsystem.
Powerful and flexible printer drivers, mature system management tools,
Customizable spooling subsystem
3. What command is used to switch from AIX to System V printing?
switch.prt -s SystemV
4. lpsched uses information in the printer configuration file and terminfo
to screen print jobs.
5. The interface program uses commands in terminfo to initialize the
printer.
6. Filters are used to convert file content.
7. Use the lpfilter command to manage filters.
8. lpadmin is used to create or modify a System V printer.
9. mkdev is used to create a printer device.
Additional Information —
Transition Statement — Introduce the optional exercise.
AP
Exercise Appendix C: The System V Print
Subsystem
Notes:
Introduction
This optional exercise can be found in your Student Exercise Guide.
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-95
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Introduce the exercise.
Details —
Additional Information —
Transition Statement — Summarize the unit.
AP
Unit Summary
Notes:
© Copyright IBM Corp. 1997, 2005 Appendix G. The System V Print Subsystem G-97
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
Instructor Notes:
Purpose — Summarize the unit.
Details —
Additional Information —
Transition Statement —
glos Glossary
Note: Synonymous with: This is a backward reference
from a defined term to all other terms that have the
The entries in this glossary were developed a same meaning.
number of years ago and indicate the use of various See: This refers the reader to multiple-word terms
terms at a particular point in UNIX history. Hence, that have the same last word.
some of the definitions may not be applicable to See also: This refers the reader to terms that have a
related, but not synonymous, meaning.
current UNIX implementations such as AIX 5L, and Deprecated term for: This indicates that the term
some other statements in the entries may not be should not be used. It refers to a preferred term,
current. However, this glossary still provides which is defined in its proper place in the glossary.
valuable information regarding the historical use of
the terms listed here.
A
This glossary includes terms and definitions from: access mode A matrix of protection information
stored with each file specifying who may do what to
• The American National Standard Dictionary for a file. Three classes of users (owner, group, all
Information Systems, ANSI X3.172-1990, others) are allowed or denied three levels of access
copyright 1990 by the American National (read, write, execute).
Standards Institute (ANSI). Copies may be access permission See access mode.
purchased from the American National access privilege See access mode.
Standards Institute, 11 West 42nd Street, New address space The address space of a process is
York, New York 10036. Definitions are identified the range of addresses available to it for code and
by the symbol (A) after the definition. data. The relationship between real and perceived
space depends on the system and support
• The ANSI/EIA Standard— 440-A, Fiber Optic hardware.
Terminology. Copies may be purchased from AIX Advanced Interactive Executive. IBM's
the Electronic Industries Association, 2001 implementation of the UNIX Operating System.
Pennsylvania Avenue, N.W., Washington, DC AIX Family Definition IBM's definition for the
20006. Definitions are identified by the symbol common operating system environment for all
(E) after the definition. members of the AIX family. The AIX Family
Definition includes specifications for the AIX Base
• The Information Technology Vocabulary, System, User Interface, Programming Interface,
developed by Subcommittee 1, Joint Technical Communications Support, Distributed Processing,
Committee 1, of the International Organization and Applications.
for Standardization and the International alias The command and process of assigning a new
Electrotechnical Commission (ISO/IEC name to a command.
JTC1/SC1). Definitions of published parts of this ANSI American National Standards Institute. A
vocabulary are identified by the symbol (I) after standards organization. The United States liaison to
the definition; definitions taken from draft the International Standards Organization (ISO).
international standards, committee drafts, and application program A program used to perform an
working papers being developed by ISO/IEC application or part of an application.
JTC1/SC1 are identified by the symbol (T) after argument An item of information following a
the definition, indicating that final agreement has command. It may, for example, modify the command
not yet been reached among the participating or identify a file to be affected.
National Bodies of SC1. ASCII American Standard Code for Information
Interchange. A collection of public domain character
• The Network Working Group Request for sets considered standard throughout the computer
Comments: 1208. industry.
The following cross-references are used in this awk An interpreter, included in most UNIX operating
glossary: systems, that performs sophisticated text pattern
Contrast with: This refers to a term that has an matching. In combination with shell scripts, awk can
opposed or substantively different meaning. be used to prototype or implement applications far
Synonym for: This indicates that the term has the more quickly than traditional programming methods.
same meaning as a preferred term, which is defined
in its proper place in the glossary.
to more than one network and can translate the i-node A collection of logical information about a file
packets of one network to another, possibly including owner, mode, type and location.
dissimilar network. i number The internal index or identification of an
global Applying to all entities of a set. For example: i-node.
• A global search - look everywhere input field An area into which you can type data.
• A global replace - replace all occurrences input redirection The accessing of input data from
• A global symbol - defined everywhere. other than standard input (the keyboard or a pipe).
grep An AIX command which searches for strings interoperability The ability of different kinds of
specified by a regular expression. (Global Regular computers to work well together.
Expression and Print.) interpreter A program which “interprets” program
group A collection of AIX users who share a set of statements directly from a text (or equivalent) file.
files. Members of the group have access privileges Distinguished from a compiler which creates
exceeding those of other users. computer instructions for later direct execution.
interrupt A signal that the operating system must
reevaluate its selection of which process should be
H running. Usually to service I/O devices but also to
hardware The equipment, as opposed to the signal from one process to another.
programming, of a system. IP Internet Protocol.
header A record at the beginning of the file ipl See initial program load.
specifying internal details about the file.
ISO International Standards Organization. A United
heterogeneous Descriptor applied to networks Nations agency that provides for creation and
composed of products from multiple vendors. administration of worldwide standards.
hierarchy A system of objects in which each object
belongs to a group. Groups belong to other groups.
Only the “head” does not belong to another group. In J
AIX this object is called the “Root Directory”. job A collection of activities.
highlight To emphasize an area on the display job number An identifying number for a collection of
screen by any of several methods, such as processes devolving from a terminal command.
brightening the area or reversing the color of
characters within the area.
history A list of recently executed commands. K
home (directory). 1. A directory associated with an kernel The part of an operating system that contains
individual user. programs that control how the computer does its
work, such as input/output, management and control
home (directory). 2. Your current directory on login
or after issuing the cd command with no argument. of hardware, and the scheduling of user tasks.
keyboard An input device consisting of various keys
homogeneous Descriptor applied to networks
composed of products from a single vendor. allowing the user to input data, control cursor and
pointer locations, and to control the user/work
hypertext Term for on-line interactive station dialogue.
documentation of computer software; to be included
with AIX. kill To prematurely terminate a process.
kill character The character which erases an entire
line (usually @).
I
IEEE Institute of Electrical and Electronics L
Engineers. A professional society active in
standards work, the IEEE is the official body for work LAN Local Area Network. A facility, usually a
on the POSIX (Portable Operating System for combination of wiring, transducers, adapter boards,
Computer Environments) open system interface and software protocols, which interconnects
definition. workstations and other computers located within a
department, building, or neighborhood. Token-Ring
index See file index.
and Ethernet are local area network products.
indirect block A file element which points at data
libc A basic set of C callable routines.
sectors or other indirect blocks.
init The initialization process of AIX. The ancestor of library In UNIX operating systems, a collection of
existing subroutines that allows programmers to
all processes.
make use of work already done by other
initial program load The process of loading the programmers. UNIX operating systems often include
system programs and preparing the system to run separate libraries for communications, window
jobs. management, string handling, math, and so forth.
line editor An editor which processes one line at a move Relinking a file or directory to a different or
time by the issuing of a command. Usually additional directory. The data (if any) is not moved,
associated with sequential only terminals such as a only the links.
teletype. multiprogramming Allocation of computer
link An entry in an AIX directory specifying a data resources among many programs. Used to allow
file or directory and its name. Note that files and many users to operate simultaneously and to keep
directories are named solely by virtue of links. A the system busy during delays occasioned by I/O
name is not an intrinsic property of a file. A file is mechanical operations.
uniquely identified only by a system generated multitasking Capability of performing two or more
identification number. computing tasks, such as interactive editing and
lint A program for removing “fuzz” from C code. complex numeric calculations, at the same time. AIX
Stricter than most compilers. Helps former Pascal and OS/2 are multi-tasking operating systems; DOS,
programmers sleep at night. in contrast, is a single-tasking system.
Local Area Network (LAN) A facility, usually a multiuser A computer system which allows many
combination of wiring, transducers, adapter boards, people to run programs “simultaneously” using
and software protocols, which interconnects multiprogramming techniques.
workstations and other computers located within a
department, building, or neighborhood. Token-Ring
and Ethernet are local area network products. N
login Identifying oneself to the system to gain named pipe See FIFO.
access.
Network File System (NFST) A program developed
login directory See home directory. by SUN Microsystems, Inc. for sharing files among
login name The name by which a user is identified systems connected via TCP/IP. IBM's AIX, VM, and
to the system. MVS operating systems support NFS.
logout Informing the system that you are through NFST See Network File System.
using it. NIST National Institute of Science and Technology
(formerly the National Bureau of Standards).
node An element within a communication network.
M • Computer
mail The process of sending or receiving an
electronically delivered message within an AIX • Terminal
system. The message or data so delivered. • Control Unit
make Programming tool included in most UNIX null A term denoting emptiness or nonexistence.
operating systems that helps “make” a new program null device A device used to obtain empty files or
out of a collection of existing subroutines and dispose of unwanted data.
utilities, by controlling the order in which those
programs are linked, compiled, and executed. null string A character string containing zero
characters.
map The process of reassigning the meaning of a
terminal key. In general, the process of reassigning
the meaning of any key.
O
memory Storage on electronic memory such as
random access memory, read only memory, or object-oriented programming Method of
registers. See storage. programming in which sections of program code and
data are represented, used, and edited in the form of
message Information displayed about an error or “objects”, such as graphical elements, window
system condition that may or may not require a user components, and so forth, rather than as strict
response. computer code. Through object-oriented
motd “Message of the day”. The login “billboard” programming techniques, toolkits can be designed
message. that make programming much easier. Examples of
object-oriented programming languages include
MotifT The graphical user interface for OSF, Pareplace Systems, Inc.'s Smalltalk-80T, AT&T's
incorporating the X Window System. Behavior of this C++T, and Stepstone Inc.'s Objective-CR.
interface is compatible with the IBM/Microsoft
Presentation Manager user interface for OS/2. Also oem original equipment manufacturer. In the context
called OSF/Motif. of AIX, OEM systems refer to the processors of a
heterogeneous computer network that are not made
mount A logical (that is, not physical) attachment of or provided by IBM.
one file directory to another. “remote mounting”
allows files and directories that reside on physically Open Software FoundationT (OSF) A non-profit
separate computer systems to be attached to a local consortium of private companies, universities, and
system. research institutions formed to conduct open
technological evaluations of available components
mouse A device that allows you to select objects of UNIX operating systems, for the purpose of
and scroll the display screen by means of buttons. assembling selected elements into a complete
version of the UNIX operating system available to pipe fitting Connecting two programs with a pipe.
those who wish to license it. IBM is a founding pipeline A sequence of programs or commands
sponsor and member of OSF. connected with pipes.
operating system The programs and procedures portability Desirable feature of computer systems
designed to cause a computer to function, enabling and applications, referring to users' freedom to run
the user to interact with the system. application programs on computers from many
option A command argument used to specify the vendors without rewriting the program's code. Also
details of an operation. In AIX an option is normally known as “applications portability”,
preceded by a hyphen. “machine-independence”, and
ordinary file Files containing text, programs, or “hardware-independence”; often cited as a cause of
other data, but not directories. the recent surge in popularity of UNIX operating
systems.
OSFT See Open Software Foundation.
port A physical I/O interface into a computer.
output redirection Passing a programs standard
output to a file. POSIX “Portable Operating Systems for Computer
Environments”. A set of open standards for an
owner The person who created the file or his operating system environment being developed
subsequent designee. under the aegis of the IEEE.
preprocessor The macro generator preceding the
C compiler.
P
process A unit of activity known to the AIX system,
packet switching The transmission of data in small, usually a program.
discrete switching “packets” rather than in streams,
for the purpose of making more efficient use of the process 0 (zero) The scheduler. Started by the
physical data channels. Employed in some UNIX “boot” and permanent. See init.
system communications. process id A unique number (at any given time)
page To move forward or backward on screen full of identifying a process to the system.
data through a file usually referring to an editor process status The process's current activity.
function.
• Non existent
parallel processing A computing strategy in which • Sleeping
a single large task is separated into parts, each of
which then runs in parallel on separate processors. • Waiting
• Running
parent The process emerging from a Fork with a
non#zero return code (the process ID of the child • Intermediate
process). A directory which points at a specified • Terminated
directory. • Stopped.
password A secret character string used to verify profile A file in the users home directory which is
user identification during login. executed at login to customize the environment. The
PATH A variable which specifies which directories name is .profile.
are to be searched for programs and shell files. prompt A displayed request for information or
path name A complete file name specifying all operator action.
directories leading to that file. protection The opposite of permission, denying
pattern-matching character Special characters access to a file.
such as * or ? that can be used in a file specification
to match one or more characters. For example,
placing a ? in a file specification means that any Q
character can be in that position. quotation Temporarily cancelling the meaning of a
permission The composite of all modes associated metacharacter to be used as a ordinary text
with a file. character. A backslash (\) “quotes” the next
pipes UNIX operating system routines that connect character only.
the standard output of one process with the
standard input of another process. Pipes are central
to the function of UNIX operating systems, which R
generally consist of numerous small programs raw I/O I/O conducted at a “physical” level.
linked together into larger routines by pipes. The
read permission Allows reading (not execution or
“piping” of the list directory command to the word
count command is ls | wc. The passing of data by a writing) of a file.
pipe does not (necessarily) involve a file. When the recursive A recursive program calls itself or is
first program generates enough data for the second called by a subroutine which it calls.
program to process, it is suspended and the second redirection The use of other than standard input
program runs. When the second program runs out of (keyboard or pipe output) or standard output
data it is suspended and the first one runs. (terminal display or pipe). Usually a file.
regular expression An expression which specifies which has execution permission. It is invoked by
a set of character strings using metacharacters. simply naming the file as a shell command.
relative path name The name of a directory or file shell script See shell program.
expressed as a sequence of directories followed by single user (mode) A temporary mode used during
a file name, beginning from the current directory. “booting” of the AIX system.
RISC Reduced Instruction Set Computer. A class of signal A software generated interrupt to another
computer architectures, pioneered by IBM's John process. See kill.
Cocke, that improves price#performance by
minimizing the number and complexity of the sockets Destination points for communication in
operations required in the instruction set of a many versions of the UNIX operating system, much
computer. In this class of architecture, advanced as electrical sockets are destination points for
compiler technology is used to provide operations, electrical plugs. Sockets, associated primarily with
such as multiplication, that are infrequently used in 4.3 BSD, can be customized to facilitate
practice. communication between separate processes or
between UNIX operating systems.
root directory The directory that contains all other
directories in the file system. software Programs.
special character See metacharacter.
special file A technique used to access I/O devices
S in which “pseudo files” are used as the interface for
scalability Desirable feature of computer systems commands and data.
and applications. Refers to the capability to use the standard error The standard device at which errors
same environment on many classes of computers,
are reported, normally the terminal. Error messages
from personal computers to supercomputers, to may be directed to a file.
accommodate growth or divergent environments,
without rewriting code or losing functionality. standard input The source of data for a filter, which
is by default obtained from the terminal, but which
SCCS Source Code Control System. A set of may be obtained from a file or the standard output of
programs for maintaining multiple versions of a file
another filter through a pipe.
using only edit commands to specify alternate
versions. standard output The output of a filter which
normally is by default directed to the terminal, but
scope The field of an operation or definition. Global which may be sent to a file or the standard input of
scope means all objects in a set. Local scope means another filter through a pipe.
a restriction to a subset of the objects.
stdio A “Standard I/O” package of C routines.
screen See display screen.
sticky bit A flag which keeps commonly used
scroll To move information vertically or horizontally programs “stick” to the swapping disk for
to bring into view information that is outside the performance.
display screen or pane boundaries.
stopped job A job that has been halted temporarily
search and replace The act of finding a match to a by the user and which can be resumed at his
given character string and replacing each
command.
occurrence with some other string.
storage In contrast to memory, the saving of
search string The pattern used for matching in a
information on physical devices such as fixed disk or
search operation. tape. See memory.
sed Non-interactive stream editor used to do “batch”
store To place information in memory or onto a
editing. Often used as a tool within shell scripts. diskette, fixed disk, or tape so that it is available for
server A provider of a service in a computer retrieval and updating.
network; for example, a mainframe computer with streams Similar to sockets, streams are destination
large storage capacity may play the role of database points for communications in UNIX operating
server for interactive terminals. See client.
systems. Associated primarily with UNIX System V,
setuid A permission which allows the access rights streams are considered by some to be more elegant
of a program owner to control the access to a file. than sockets, particularly for interprocess
The program can act as a filter for user data communication.
requests. string A linear collection of characters treated as a
shell The outermost (user interface) layer of UNIX unit.
operating systems. Shell commands start and subdirectory A directory which is subordinate to
control other processes, such as editors and
another directory.
compilers; shells can be textual or visual. A series of
system commands can be collected together into a subtree That portion of an AIX file system
“shell script” that executes like a batch (.BAT) file in accessible from a given directory below the root.
DOS. suffix A character string attached to a file name that
shell program A program consisting of a sequence helps identify its file type.
of shell commands stored in an ordinary text file
superblock Primary information repository of a file two-digit display Two seven-segment light-emitting
system (location of i-nodes, free list, and so forth). diodes (LEDs) on the operating panel used to track
superuser The system administration; a user with the progress of power-on self-tests (POSTs).
unique privileges such as upgrading execution
priority and write access to all files and directories.
superuser authority The unrestricted ability to
U
access and modify any part of the Operating UNIX Operating System A multi-user, multi-tasking
System. This authority is associated with the user interactive operating system created at AT&T Bell
who manages the system. Laboratories that has been widely used and
developed by universities, and that now is becoming
SVID System V Interface Definition. An AT&T increasingly popular in a wide range of commercial
document defining the standard interfaces to be applications. See Kernel, Shell, Library, Pipes,
used by UNIX System V application programmers Filters.
and users.
user interface The component of the AIX Family
swap space (disk) That space on an I/O device Definition that describes common user interface
used to store processes which have been swapping functions for the AIX PS/2, AIX/RT, and AIX/370
out to make room for other processes. operating systems.
swapping The process of moving processes /usr/grpR One of the oldest, and still active, user
between main storage and the “swapping device”, groups for the UNIX operating systems. IBM is a
usually a disk. member of /usr/grp.
symbolic debugger Program for debugging other uucp A set of AIX utilities allowing
programs at the source code level. Common
symbolic debuggers include sdb, dbx, and xdbx. • Autodial of remote systems
sync A command which copies all modified blocks • Transfer of files
from RAM to the disk. • Execution of commands on the remote system
system The computer and its associated devices • Reasonable security.
and programs.
V
system unit The part of the system that contains
the processing unit, the disk drive and the disk, and vi Visual editor. A character editor with a very
the diskette drive. powerful collection of editing commands optimized
for ASCII terminals; associated with BSD versions of
System V AT&T's recent releases of its UNIX the UNIX operating system.
operating system are numbered as releases of
“UNIX System V”. visual editor An optional editor provided with AIX in
which changes are made by modifying an image of
the file on the screen, rather than through the
exclusive use of commands.
T
TCP Transmission Control Protocol. A facility for the
creation of reliable bytestreams (byte-by-byte, W
end#to#end transmission) on top of unreliable
datagrams. The transmission layer of TCP/IP is wild card A metacharacter used to specify a set of
used to interconnect applications, such as FTP, so replacement characters and thus a set of file names.
that issues of re-transmission and blocking can be For example "*" is any zero or more characters and
subordinated in a standard way. See TCP/IP. "?" is any one character.
TCP/IP Transmission Control Protocol/Internet window A rectangular area of the screen in which
Protocol. Pair of communications protocol the dialog between you and a given application is
considered de facto standard in UNIX operating displayed.
system environments. IBM TCP/IP for VM and IBM working directory The directory from which file
TCP/IP for MVS are licensed programs that provide searches are begun if a complete pathname is not
VM and MVS users with the capability of specified. Controlled by the cd (change directory)
participating in networks using the TCP/IP protocol command.
suite. workstation A device that includes a keyboard from
termcap A file containing the description of several which an operator can send information to the
hundred terminals. For use in determining system, and a display screen on which an operator
communication protocol and available function. can see the information sent to or received from the
termlib A set of C programs for using termcap. computer.
tools Compact, well designed programs to perform write Sending data to an I/O device.
specific tasks. More complex processes are write permission Permission to modify a file or
performed by sequences of tools, often in the form directory.
of pipelines which avoid the need for temporary files.
X
X/OpenT An international consortium, including
many suppliers of computer systems, concerned
with the selection and adoption of open system
standards for computing applications. IBM is a
corporate sponsor of X/Open. See Common
Application Environment.
X Windows IBM's implementation of the X Window
System developed at the Massachusetts Institute of
Technology with the support of IBM and DECT, that
gives users “windows” into applications and
processes not located only or specifically on their
own console or computer system. X-Windows is a
powerful vehicle for distributing applications among
users on heterogeneous networks.
Y
yacc “Yet Another Compiler# Compiler”. For
producing new command interfaces.
Z
zeroeth argument The command name; the
argument before the first.
backpg
Back page
®