AIX 5L Installation - Bull On-line Support Portalsupport.bull.com/.../software/aix/aix5.2/g/86Y207EG01/86A207EG01.pdfAIX 5L Installation Guide and Reference ESCALA AIX REFERENCE

AIX 5L Installation

Guide and Reference

ESC

ALA

AIX

REFERENCE86 A2 07EG 01

ESCALA

AIX 5L InstallationGuide and Reference

AIX

June 2003

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE86 A2 07EG 01

Software

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 1992, 2003

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

AIX® is a registered trademark of International Business Machines Corporation, and is being used under licence.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

iiiPreface

About This Book

This book provides system administrators with complete information about how to performsuch tasks as installing and maintaining the AIX operating system and optional software onstandalone systems and on client systems from a resource server using the Network InstallManagement (NIM) interface. It also includes information on how to migrate a system,manage system backups, install AIX updates, use alternate disk installation, andtroubleshoot problems with installation. This publication is available on the ”HypertextLibrary for AIX 5.1” CD-ROM that is shipped with the operating system.

Beginning with the AIX 5.2 documentation library, all information regarding AIX systemsecurity, or any security–related topic, has moved. For all security–related information, seethe AIX 5L Version 5.2 Security Guide.

This edition supports the release of AIX 5L Version 5.2 with the 5200–01 RecommendedMaintenance package. Any specific references to this maintenance package are indicatedas AIX 5.2 with 5200–01.

Who Should Use This BookThis book is intended for system administrators who are installing AIX 5.2 on standalonesystems or networked systems.

HighlightingThe following highlighting conventions are used in this book:

Bold Identifies commands, subroutines, keywords, files, structures,directories, and other items whose names are predefined by thesystem. Also identifies graphical objects such as buttons, labels,and icons that the user selects.

Italics Identifies parameters whose actual names or values are to besupplied by the user.

Monospace Identifies examples of specific data values, examples of textsimilar to what you might see displayed, examples of portions ofprogram code similar to what you might write as a programmer,messages from the system, or information you should actuallytype.

Viewing Readme Files

The Base Operating System (BOS) includes a readme file that contains information notincluded in other documentation. Each software product may also have its own readme filewith new information specific to that product. After you install BOS, view these files to learnimportant changes before using your system.

Use the following procedure to view the readme files for Base Operating System (BOS)software and optional software products:

1. Log in as root user if you have not already done so.

iv Installation and Reference Guide

2. Enter the following command at the system prompt:

cd /usr/lpp

3. Type:

ls */*README*

The system lists readme files for each software product installed on your system.

4. To view a readme file for a specific software product, use the following command:

pg xxx /README

In this example, xxx is the directory name associated with a particular software product.

Press Enter when the copyright screen appears. Press the following keys or keycombinations to scroll through the readme file:

To page down Press Enter key.

To page up Type the minus ( – ) key, then press theEnter key.

To move forward x pages Type the plus ( + ) key and number ofpages, then press the Enter key.

For example, to move forward five pages,type +5 and press the Enter key.

To move backward x pages Type the minus ( – ) key and number ofpages, then press the Enter key.

For example, to move backward fivepages, type –5 and press Enter.

Type q at the : (colon) prompt to exit the readme file.

Case–Sensitivity in AIXEverything in the AIX operating system is case–sensitive, which means that it distinguishesbetween uppercase and lowercase letters. For example, you can use the ls command to listfiles. If you type LS, the system responds that the command is ”not found.” Likewise, FILEA,FiLea, and filea are three distinct file names, even if they reside in the same directory. Toavoid causing undesirable actions to be performed, always ensure that you use the correctcase.

ISO 9000ISO 9000 registered quality systems were used in the development and manufacturing ofthis product.

Related PublicationsThe following publications contain additional information related to the installation andmanagement of AIX 5.2:

• System Release Bulletin (SRB)

• AIX 5L Version 5.2 Operating System Installation: Getting Started

• AIX 5L Version 5.2 System Management Guide: Operating System and Devices

• AIX 5L Version 5.2 System Management Guide: Communications and Networks

• AIX 5L Version 5.2 Commands Reference

vPreface

• AIX 5L Version 5.2 Files Reference

• AIX 5L Version 5.2 General Programming Concepts: Writing and Debugging Programs

• AIX 5L Version 5.2 System User’s Guide: Operating System and Devices

• AIX 5L Version 5.2 System User’s Guide: Communications and Networks

• AIX 5L Version 5.2 Security Guide

vi Installation and Reference Guide

viiPreface

Contents

About This Book iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1. How–To’s for AIX Installation Tasks 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the System Release Bulletin (SRB) 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2. How–To’s for Base Operating System Installation Tasks 2-1. . . . . . . .

Perform a New and Complete Overwrite Base Operating System Installation from CD 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Prepare Your System 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Boot from the AIX Product CD 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3. Set and Verify BOS Installation Settings 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 4. Configure the System after Installation 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Perform a Migration Base Operating System Installation from CD 2-6. . . . . . . . . . . . . .

Step 1. Prepare for the Migration 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Boot from the AIX Product CD 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3. Verify Migration Installation Settings and Begin Installation 2-7. . . . . . . . . . .

Step 4. Verify System Configuration after Installation 2-8. . . . . . . . . . . . . . . . . . . . . . .

Perform a Nonprompted New and Complete Overwrite Base Operating System Installation from CD 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create a Customized bosinst.data File 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create a Supplementary Diskette 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Boot from the AIX Product CD 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create and Install a Software Bundle 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Create a User–Defined Software Bundle 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Install the Software Bundle 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3. Verify the Installation of the Software Bundle 2-14. . . . . . . . . . . . . . . . . . . . . . .

Add Open Source Applications to Your AIX System 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . .

Clone a rootvg Using Alternate Disk Installation 2-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Prepare for the Alternate Disk Installation 2-17. . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Perform the Alternate Disk Installation and Customization 2-18. . . . . . . . . . . .

Step 3. Boot from the Alternate Disk 2-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 4. Verify the Operation 2-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configure NIM Using EZNIM 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Install a Client Using NIM 2-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create a System Backup to Tape 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Prepare for System Backup Creation 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Create a System Backup to Tape 2-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clone a System Using a System Backup Tape 2-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clean Up a Failed Software Installation 2-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3. Operating System and Optional Software Installation 3-1. . . . . . . . . . .

Chapter 4. What’s New in Base Operating System Installation and SoftwareInstallation? 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BOS Menus 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Maintenance and Utilities 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Service Management 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Emergency Fix Management 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk Migration Installation 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Universal Disk Format Support for DVD–RAM 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii Installation and Reference Guide

Installation Commands 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5. Introduction to Base Operating System Installation 5-1. . . . . . . . . . . . .

BOS Menus 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Electronic License Agreements 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6. Installation Options 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7. New and Complete Overwrite Installation / Preservation Installation 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Complete the Prerequisites 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Prepare Your System for Installation 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3. Set Up an ASCII Terminal 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 4. Boot from Your Installation Media 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 5. Verify or Change the Installation Settings 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 6. Finish the BOS Installation 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Information 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8. Migration Installation 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Binary Compatibility Between Earlier Versions and AIX 5.2 8-2. . . . . . . . . . . . . . . . . . . .

Pre–Migration and Post–Migration Checking 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Migrating to AIX 5.2 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1. Complete the Prerequisites 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2. Prepare Your System for Installation 8-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3. Boot from Your Installation Media 8-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 4. Finish the BOS Migration 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Chapter 9. Configuring the Operating System 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Assistant 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation Assistant 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Chapter 10. Customized BOS Installations 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Customized BOS Installations 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customizing and Using a bosinst.data File 10-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create and Use a Client File 10-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create and Use a Supplementary Diskette 10-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Chapter 11. The bosinst.data File 11-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

bosinst.data File Stanza Descriptions 11-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

control_flow Stanza 11-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

target_disk_data Stanza 11-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

locale Stanza 11-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

large_dumplv Stanza 11-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

dump Stanza 11-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

bosinst.data File Example 11-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Nonprompted Network Installation 11-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12. Optional Software Products and Service Updates 12-1. . . . . . . . . . . . .

Optionally Installed Software 12-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Product Identification 12-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Licensing 12-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing Optional Software Products and Service Updates 12-3. . . . . . . . . . . . . . . . . . . .

Step 1. Complete the Prerequisites 12-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ixPreface

Step 2. Install Optional Software Products or Service Updates 12-4. . . . . . . . . . . . . . .

Maintaining Optional Software Products and Service Updates 12-7. . . . . . . . . . . . . . . . .

Apply Action (Service Updates Only) 12-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Commit Action (Service Updates Only) 12-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reject Action (Service Updates Only) 12-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remove Action (Software Products Only) 12-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Copy Software Bundle to Hard Disk for Future Installation 12-10. . . . . . . . . . . . . . . . . .

Cleaning Up Optional Software Products and Service Updates 12-10. . . . . . . . . . . . . . . . .

Manage an Existing installp Image Source 12-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Service Management 12-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Comparison Reports 12-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rename Software Images in Repository 12-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clean Up Software Images in Repository 12-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

InstallShield MultiPlatform Packaged Installations 12-14. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing an InstallShield MultiPlatform Product 12-14. . . . . . . . . . . . . . . . . . . . . . . . . . .

Uninstalling an InstallShield MultiPlatform Product 12-15. . . . . . . . . . . . . . . . . . . . . . . . .

Silent Installations and Using Response Files 12-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using Response Files with NIM 12-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Emergency Fix Management 12-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing and Managing Emergency Fixes 12-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Additional Emergency Fix Information 12-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packaging Emergency Fixes 12-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Chapter 13. AIX Online Documentation 13-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 14. Creating and Installing System Backups 14-1. . . . . . . . . . . . . . . . . . . . . .

Creating System Backups 14-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Install All Device and Kernel Support Before the Backup is Created 14-2. . . . . . . . . .

Prerequisites for Creating Backups 14-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Root Volume Group Backup to Tape or File 14-4. . . . . . . . . . . . . . . . . . . . .

System Backup to CD–R, DVD–R, or DVD–RAM 14-6. . . . . . . . . . . . . . . . . . . . . . . . . .

User Volume Group Backup 14-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Backup Options 14-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing System Backups 14-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cloning a System Backup 14-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing a System Backup on the Source Machine, ”network installation” 14-16. . . . .

Chapter 15. Alternate Disk Installation 15-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Filesets to Install 15-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate mksysb Disk Installation 15-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk rootvg Cloning 15-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Phased Alternate Disk Installation 15-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk Migration Installation 15-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Requirements 15-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitations 15-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk Migration Installation Usage 15-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk Migration Installation Process 15-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Access Between the Original rootvg and the New Alternate Disk 15-6. . . . . . . . . .

Installing to an Alternate Disk using Web–based System Manager 15-6. . . . . . . . . . . . .

Running Alternate Disk Installation Using SMIT 15-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alternate Disk Installation and Dynamic Logical Partitioning 15-7. . . . . . . . . . . . . . . . . . .

Examples 15-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

x Installation and Reference Guide

Chapter 16. Software Product Packaging Concepts 16-1. . . . . . . . . . . . . . . . . . . . . . .

Software Package Formats 16-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fileset Installation Packaging 16-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Software Packages 16-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bundle Packaging 16-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 17. Troubleshooting Operating System and Optional Software Installation 17-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting an Installation from a System Backup 17-2. . . . . . . . . . . . . . . . . . . . . . . .

Bootup Failure 17-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Problems with mksysb Image Configuration on System Backup Tapes 17-2. . . . . . . .

Troubleshooting Reported Problems with mksysb Backup Installations 17-3. . . . . . .

Troubleshooting a Migration Installation 17-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Boot Logical Volume Not Large Enough 17-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Insufficient Disk Space for Migration 17-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting an Alternate Disk Installation 17-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Other Problems 17-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting After an Installation 17-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing a System That Does Not Boot 17-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 17-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing the System 17-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting a Full /usr File System 17-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing BOS Installation Logs 17-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing Logs with SMIT 17-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing Logs with the alog Command 17-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handling System and Error Messages 17-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 18. Network Installation 18-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 19. What’s New in Network Installation Management (NIM)? 19-1. . . . . . .

Working with EZNIM 19-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Resources Simultaneously 19-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LPP Source Enhancements 19-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Resource Groups 19-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Commands 19-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 20. Network Installation Management Introduction 20-1. . . . . . . . . . . . . . . .

Chapter 21. NIM Task Roadmap 21-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 22. EZNIM 22-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EZNIM Master Operations 22-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EZNIM Client Operations 22-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 23. Basic NIM Operations and Configuration 23-1. . . . . . . . . . . . . . . . . . . . . .

Configuring the NIM Master and Creating Basic Installation Resources 23-3. . . . . . . . .

Prerequisites 23-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From Web-based System Manager 23-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From SMIT 23-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From the Command Line 23-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding a Standalone NIM Client to the NIM Environment 23-6. . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Verifying the Status of Your Client Machine 23-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xiPreface

Using Installation Images to Install the Base Operating System (BOS) on a NIM Client 23-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using a mksysb Image to Install the Base Operating System (BOS) on a NIM Client (mksysb Installation) 23-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cloning Considerations 23-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Performing a Nonprompted BOS Installation 23-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Installing to Clients on ATM Networks 23-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BOS Installation over Non–ATM Adapters 23-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BOS Installation over ATM Adapters 23-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Configuration Requirements for ATM Networks 23-17. . . . . . . . . . . . . . . . . . . . . . . .

Converting Generic Networks Into ATM Networks 23-17. . . . . . . . . . . . . . . . . . . . . . . . . .

System Recovery After Boot Failure 23-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customizing NIM Clients and SPOT Resources 23-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Configuring the NIM Master and Creating Resources to Support Diskless and DatalessClients Only 23-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Adding a Diskless or Dataless Client to the NIM Environment 23-24. . . . . . . . . . . . . . . . . .

Prerequisites 23-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Initializing and Booting a Diskless or Dataless Machine 23-26. . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 23-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Uninitializing Diskless and Dataless Machines 23-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Installing to an Alternate Disk on a NIM Client (cloning or mksysb) 23-29. . . . . . . . . . . . .

Prerequisites 23-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 23-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Network Installation Management Commands Reference 23-31. . . . . . . . . . . . . . . . . . . . .

xii Installation and Reference Guide

The nim_master_setup Command 23-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The nim_clients_setup Command 23-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Other NIM Commands Reference 23-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 24. Advanced NIM Installation Tasks 24-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controlling the Master or Client 24-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disabling Master Push Permissions 24-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Resetting Machines 24-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using Client Machines as Resource Servers 24-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Defining a Machine Group 24-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Adding New Members to Machine Groups 24-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Removing Members from Machine Groups 24-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Including and Excluding a Group Member from Operations on the Group 24-9. . . . . . . .


From SMIT 24-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using Resource Groups to Allocate Related Resources to NIM Machines 24-10. . . . . . .

Defining a Resource Group 24-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Allocating a Resource Group 24-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Default Resource Groups 24-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managing Software on Standalone Clients and SPOT Resources 24-12. . . . . . . . . . . . . .

Listing Software Installed on a Standalone Client or SPOT 24-12. . . . . . . . . . . . . . . . . .

Listing Software Updates, Installed on a Standalone Client or SPOT, by Keyword 24-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maintaining Software on Standalone Clients and SPOT Resources 24-14. . . . . . . . . .

Rebuilding Network Boot Images for a SPOT 24-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Maintaining Software in an lpp_source 24-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Copying Software to an lpp_source 24-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Removing Software from an lpp_source 24-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Running the NIM check Operation 24-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing Installation, Configuration, and Boot Logs 24-18. . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Verifying Installation with the lppchk Operation 24-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xiiiPreface


Using NIM to Install Clients Configured with Kerberos Authentication 24-20. . . . . . . . . . .

Using NIM to Install Clients Configured with Kerberos 4 Authentication 24-20. . . . . . .

Using NIM to Install Clients Configured with Kerberos 5 Authentication 24-20. . . . . . .

Concurrency Control 24-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 24-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Chapter 25. Advanced NIM Configuration Tasks 25-1. . . . . . . . . . . . . . . . . . . . . . . . . . .

Removing Machines from the NIM Environment 25-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Creating Additional Interface Attributes 25-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Defining /usr versus non–/usr SPOTs 25-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using the installp Command 25-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Re–Creating SPOT Resources from Existing Directories 25-7. . . . . . . . . . . . . . . . . . . . . .

Defining an lpp_source on CD–ROM versus Disk 25-8. . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Establishing a Default NIM Route Between Networks 25-9. . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Establishing a Static NIM Route Between Networks 25-10. . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Recovering the /etc/niminfo File 25-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Backing Up the NIM Database 25-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Restoring the NIM Database and Activating the NIM Master 25-14. . . . . . . . . . . . . . . . . . .


From SMIT 25-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Unconfiguring the NIM Master 25-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Booting Diagnostics 25-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


xiv Installation and Reference Guide

Verifying the diag Operation 25-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading Diagnostics without the diag Operation 25-17. . . . . . . . . . . . . . . . . . . . . . . . . . .

Booting in Maintenance Mode 25-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 25-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using Maintenance Mode 25-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Secondary Adapter Support 25-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Secondary Adapter File Rules 25-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Secondary Adapter File Keywords 25-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Secondary Adapter File Stanza Errors 25-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Secondary Adapter File 25-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Examples 25-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 26. Additional NIM Topics 26-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Master Management Tasks 26-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deactivating the NIM Master and Removing the NIM Master Fileset 26-2. . . . . . . . . .

Increasing the Number of Hosts to Which NIM Can NFS–Export a Resource 26-2. .

Controlling the Asynchronous Behavior of NIM Operations 26-3. . . . . . . . . . . . . . . . . .

Suppressing Output from NIM Operations 26-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reducing Space Requirements for NIM Resources 26-3. . . . . . . . . . . . . . . . . . . . . . . .

NIM Name Resolution 26-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Booting a FDDI Interface Over a Router 26-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Default Paging Space During BOS Installation Through NIM 26-6. . . . . . . . . . . . . . . . . . .

Migrating Diskless and Dataless Clients and NIM SPOTS 26-7. . . . . . . . . . . . . . . . . . . . .

Defining the NIM Environment Using the nimdef Command 26-8. . . . . . . . . . . . . . . . . . . .

Name Requirements for NIM Object Definitions 26-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interacting with the Dynamic Host Configuration Protocol 26-10. . . . . . . . . . . . . . . . . . . . .

Creating File Resources in the root Directory 26-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restricting NIM Client Resource Allocation 26-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From SMIT 26-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Preventing Machines from Adding Themselves as Clients 26-13. . . . . . . . . . . . . . . . . . . . .

From SMIT 26-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Disabling Client CPU ID Validation 26-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 26-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Exporting NIM Resources Globally 26-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


From SMIT 26-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Creating Network Boot Images to Support Only the Defined Clients and Networks 26-16


From SMIT 26-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Updating a Spot with New Device Support for a New Level of AIX 26-17. . . . . . . . . . . . . .

Tuning Client–Request Processing 26-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From SMIT 26-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



xvPreface

Chapter 27. Network Installation Management Concepts 27-1. . . . . . . . . . . . . . . . . . .

NIM Machines 27-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Operations on Client Machines 27-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining NIM Clients 27-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standalone Clients 27-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diskless and Dataless Clients 27-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Networks 27-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supported NIM Network Types 27-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining NIM Networks 27-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining a Network’s IP Address 27-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Routes 27-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining a Heterogeneous Network 27-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding Another Network Type to a NIM Network 27-14. . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Resources 27-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

adapter_def Resource 27-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

boot Resource 27-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

bosinst_data Resource 27-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

dump Resource 27-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

exclude_files Resource 27-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

fb_script Resource 27-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

fix_bundle Resource 27-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

home Resource 27-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

image_data Resource 27-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

installp_bundle Resource 27-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

lpp_source Resource 27-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

mksysb Resource 27-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

nim_script Resource 27-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

paging Resource 27-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

resolv_conf Resource 27-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

root Resource 27-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

script Resource 27-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

shared_home Resource 27-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SPOT (Shared Product Object Tree) Resource 27-28. . . . . . . . . . . . . . . . . . . . . . . . . . . .

tmp Resource 27-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Distributed NIM Resources 27-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Operations 27-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

allocate 27-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

alt_disk_install 27-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

bos_inst 27-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

change 27-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

check 27-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

cust 27-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

deallocate 27-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

define 27-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

diag 27-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

dkls_init 27-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

dtls_init 27-47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

fix_query 27-47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

lppchk 27-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

lppmgr 27-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

maint 27-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

maint_boot 27-50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

reboot 27-50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

remove 27-51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

reset 27-51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi Installation and Reference Guide

select 27-51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

showlog 27-52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

showres 27-53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

sync_roots 27-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

unconfig 27-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

update 27-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NIM Groups 27-56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Machine Groups 27-56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Resource Groups 27-57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 28. Sample Files 28-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

script Resource File 28-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Definition File for the nimdef Command 28-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 29. NIM Error and Warning Messages 29-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 30. NIM Troubleshooting 30-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Debugging a Network Boot Problem 30-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying Network Communication Between the Client and Server 30-1. . . . . . . . . . .

Obtaining the Boot Image from the Server 30-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Running the Boot Image on the Client 30-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Producing Debug Output for NIM BOS Installations 30-4. . . . . . . . . . . . . . . . . . . . . . . . . . .

Producing Debug Output from a Network Boot Image 30-4. . . . . . . . . . . . . . . . . . . . . .

Producing Debug Output from the BOS Installation Program 30-5. . . . . . . . . . . . . . . .

Port Number Conflicts with NIM and Other Applications 30-7. . . . . . . . . . . . . . . . . . . . . . .

Appendix A. Network Boot A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Booting a Machine Over the Network A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Method A A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Method B (Booting Micro Channel–Based, Symmetric Multiprocessor Systems) A-3

Method C (Booting an rspc Platform Machine) A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating IPL ROM Emulation Media A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From Web-based System Manager A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

From SMIT A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary G-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index X-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1How–To’s for AIX Installation Tasks

Chapter 1. How–To’s for AIX Installation Tasks

Part 1 contains how–to instructions for performing installation tasks.

Using the System Release Bulletin (SRB)Before installing a software on your system, we recommend you to carefully read theSystem Release Bulletin (SRB) that comes with the software media.

The SRB provides release-specific information and instructions related to softwareinstallation. It also contains information it is important to be aware of, such as knownlimitations or special operational notes.

The SRB for AIX also contains information and instructions for added software contained onthe Bull Enhancement CD-ROM.

1-2 Installation Guide and Reference


Chapter 2. How–To’s for Base Operating SystemInstallation Tasks

This chapter provides the following how–to instructions for performing common installationtasks:

• Perform a New and Complete Overwrite Base Operating System Installation from CD onpage 2-2

• Perform a Migration Base Operating System Installation from CD on page 2-6

• Perform a Nonprompted New and Complete Overwrite Base Operating SystemInstallation from CD on page 2-9

• Create and Install a Software Bundle on page 2-12

• Add Open Source Applications to Your AIX System on page 2-15

• Clone a rootvg Using Alternate Disk Installation on page 2-17

• Configure NIM Using EZNIM on page 2-20

• Install a Client Using NIM on page 2-21

• Create a System Backup to Tape on page 2-23

• Clone a System Using a System Backup Tape on page 2-25

• Clean Up a Failed Software Installation on page 2-26


Perform a New and Complete Overwrite Base OperatingSystem Installation from CD

Using this scenario, you can install the AIX operating system for the first time or overwritean existing version of the operating system. In this scenario, you will do the following:

• Boot from the AIX product CD

• Set BOS Installation Settings

– Perform a new and complete overwrite installation of AIX onto hdisk0

– Use English as the primary language

– Use the default options in the More Options menu

• Start the BOS Installation and Configure the System

If you are overwriting an existing system, gather the TCP/IP information from the systembefore you begin this scenario. Attention: This procedure requires shutting down andreinstalling the base operating system. Whenever you reinstall any operating system,schedule your downtime when it least impacts your workload to protect yourself from apossible loss of data or functionality. Before you perform a new and complete overwriteinstallation, ensure you have reliable backups of your data and any customized applicationsor volume groups. For instructions on how to create a system backup, refer to CreatingSystem Backups on page 14-2.

The following steps show you how to use the system’s built–in CD–ROM device to performa new and complete overwrite base operating system installation.

Step 1. Prepare Your System• There must be adequate disk space and memory available. AIX 5.2 requires 128 MB of

memory and 2.2 GB of physical disk space. For additional release information, see theAIX 5.2 Release Notes.

• Make sure your hardware installation is complete, including all external devices. See thedocumentation provided with your system unit for installation instructions.

• If your system needs to communicate with other systems and access their resources,make sure you have the information in the following worksheet before proceeding withinstallation:

Network Attribute Value

Network Interface (For example: en0, et0)

Host Name

IP Address _______.________.________.________

Network Mask _______.________.________.________

Nameserver _______.________.________.________

Domain Name

Gateway _______.________.________.________

Step 2. Boot from the AIX Product CD1. Insert the AIX Volume 1 CD into the CD–ROM device.

2. Make sure all external devices attached to the system (such as CD–ROM drives, tapedrives, DVD drives, and terminals) are turned on. Only the CD–ROM drive from whichyou will install AIX should contain the installation media.

3. Power on the system.


4. When the system beeps twice, press F5 on the keyboard (or 5 on an ASCII terminal). Ifyou have a graphics display, you will see the keyboard icon on the screen when thebeeps occur. If you have an ASCII terminal (also called a tty terminal), you will see theword keyboard when the beeps occur.

Note: If your system does not boot using the F5 key (or the 5 key on anASCII terminal), refer to your hardware documentation for informationabout how to boot your system from an AIX product CD.

5. Select the system console by pressing F1 (or 1 on an ASCII terminal) and press Enter.

6. Select the English language for the base operating system (BOS) Installation menus bytyping a 1 in the Choice field. Press Enter to open the Welcome to Base OperatingSystem Installation and Maintenance screen.

7. Type 2 to select 2 Change/Show Installation Settings and Install in the Choice fieldand press Enter.

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

88 Help ?

99 Previous Menu

>>> Choice [1]: 2

Step 3. Set and Verify BOS Installation Settings1. In the Installation and Settings screen, verify the installation settings are correct by

checking the method of installation (new and complete overwrite), the disk or disks youwant to install, the primary language environment settings, and the advanced options.

If the default choices are correct, type 0 and press Enter to begin the BOS installation.The system automatically reboots after installation is complete. Go to Step 4. Configurethe System after Installation.

Otherwise, go to sub–step 2.

2. To change the System Settings, which includes the method of installation and disk whereyou want to install, type 1 in the Choice field and press Enter.

Installation and Settings

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 System Settings: Method of Installation.............New and Complete Overwrite

Disk Where You Want to Install.....hdisk0

>>> Choice [0]: 1

3. Type 1 for New and Complete Overwrite in the Choice field and press Enter. TheChange Disk(s) Where You Want to Install screen now displays.


Change Disk(s) Where You Want to Install

Type one or more numbers for the disk(s) to be used for installation and press

Enter. To cancel a choice, type the corresponding number and Press Enter.

At least one bootable disk must be selected. The current choice is indicated

by >>>.

Name Location Code Size(MB) VG Status Bootable

1 hdisk0 04–B0–00–2,0 4296 none Yes

2 hdisk1 04–B0–00–5,0 4296 none Yes

3 hdisk2 04–B0–00–6,0 12288 none Yes

>>> 0 Continue with choices indicated above

66 Disks not known to Base Operating System Installation

77 Display More Disk Information

88 Help ?

99 Previous Menu

>>> Choice [0]:

4. In the Change Disk(s) Where You Want to Install screen:

a. Select hdisk0 by typing a 1 in the Choice field and press Enter. The disk will nowbe selected as indicated by >>>. To unselect the destination disk, type the numberagain and press Enter.

b. To finish selecting disks, type a 0 in the Choice field and press Enter. TheInstallation and Settings screen displays with the selected disks listed under SystemSettings.

5. Change the Primary Language Environment Settings to English (United States). Use thefollowing steps to change the Cultural Convention, Language, and Keyboard to English.

a. Type 2 in the Choice field on the Installation and Settings screen to select thePrimary Language Environment Settings option.

b. Type the number corresponding to English (United States) as the Cultural Conventionin the Choice field and press Enter.

c. Select the appropriate keyboard and language options.

You do not need to select the More Options selection, because you are using thedefault options in this scenario. For more information about the installation optionsavailable in AIX 5.2, see Installation Options.

6. Verify that the selections are correct in the Overwrite Installation Summary screen, asfollows:

Overwrite Installation Summary

Disks: hdisk0

Cultural Convention: en_US

Language: en_US

Keyboard: en_US

64 Bit Kernel Enabled: No

JFS2 File Systems Created: No Desktop: CDE

Enable System Backups to install any system: Yes

Optional Software being installed:

>>> 1 Continue with Install

88 Help ?

99 Previous Menu

>>> Choice [1]:


7. Press Enter to begin the BOS installation. The system automatically reboots afterinstallation is complete.

Step 4. Configure the System after Installation1. On systems with a graphics display, after a new and complete overwrite installation, the

Configuration Assistant opens. On systems with an ASCII display, after a new andcomplete overwrite installation, the Installation Assistant opens.

2. Select the Accept Licenses option to accept the electronic licenses for the operatingsystem.

3. Set the date and time, set the password for the administrator (root user), and configurenetwork communications (TCP/IP).

Use any other options at this time. You can return to the Configuration Assistant or theInstallation Assistant by typing configassist or smitty assist at the command line.

4. Select Exit the Configuration Assistant and select Next. Or, press F10 (or ESC+0 ) toexit the Installation Assistant.

5. If you are in the Configuration Assistant, select Finish now, and do not startConfiguration Assistant when restarting AIX and select Finish.

At this point, the BOS Installation is complete, and the initial configuration of the system iscomplete.


Perform a Migration Base Operating System Installation fromCD

Using this scenario, you can migrate a system from AIX 4.3.3 (or earlier) to AIX 5.2. In thisscenario, you will do the following:

• Perform a migration installation of AIX 4.3.3 to AIX 5.2

• Use English as the primary language

• Use the default options in the Advanced Options menu

If you are overwriting an existing system, gather the TCP/IP information before you beginthis scenario. Attention: This procedure requires shutting down and reinstalling the baseoperating system. Whenever you reinstall any operating system, schedule your downtimewhen it least impacts your workload to protect yourself from a possible loss of data orfunctionality. Before you perform a migration installation, ensure you have reliable backupsof your data and any customized applications or volume groups. For instructions on how tocreate a system backup, refer to Creating System Backups on page 14-2.

The following steps show you how to use the system’s built–in CD–ROM device to performa migration base operating system installation.

Step 1. Prepare for the MigrationBefore starting the migration, complete the following prerequisites:

• Ensure that the root user has a primary authentication method of SYSTEM. You cancheck this condition by typing the following command:

# lsuser –a auth1 root

If needed, change the value by typing the following command:

# chuser auth1=SYSTEM root

• Before you begin the installation, other users who have access to your system must belogged off.

• Verify that your applications will run on AIX 5.2. Also, check if your applications arebinary–compatible with AIX 5.2. If your system is an application server, verify that thereare no licensing issues. Refer to your application documentation or provider to verify onwhich levels of AIX your applications are supported and licensed.

• Verify that all currently installed software is correctly entered in the Software VitalProduct Database (SWVPD), by using the lppchk command. To verify that all filesetshave all required requisites and are completely installed, type the following:

# lppchk –v

• Check that your hardware microcode is up–to–date.

• All requisite hardware, including any external devices (such as tape drives orCD/DVD–ROM drives), must be physically connected and powered on. If you needfurther information, refer to the hardware documentation that accompanied your system.

• Use the errpt command to generate an error report from entries in the system error log.To display a complete detailed report, type the following:

# errpt –a

• There must be adequate disk space and memory available. AIX 5.2 requires 128 MB ofmemory and 2.2 GB of physical disk space. For additional release information, see theAIX 5.2 Release Notes.

• Make a backup copy of your system software and data. For instructions on how to createa system backup, refer to Creating System Backups.


Step 2. Boot from the AIX Product CD1. If they are not already on, turn on your attached devices.

2. Insert the AIX Volume 1 CD into the CD–ROM device.

3. Reboot the system by typing the following command:

# shutdown –r



5. Select the system console by pressing F1 (or 1 on an ASCII terminal) and press Enter.

6. Select the English language for the BOS Installation menus by typing a 1 at the Choicefield and press Enter. The Welcome to Base Operating System Installation andMaintenance menu opens.

7. Type 2 to select 2 Change/Show Installation Settings and Install in the Choice fieldand press Enter.




1 Start Install Now with Default Settings



88 Help ?

99 Previous Menu

>>> Choice [1]: 2

Step 3. Verify Migration Installation Settings and Begin Installation1. Verify that migration is the method of installation. If migration is not the method of

installation, select it now. Select the disk or disks you want to install.

1 System Settings:

Method of Installation.............Migration


2. Select Primary Language Environment Settings (AFTER Install).

3. Type 3 and press Enter to select More Options. To use the Help menu to learn moreabout the options available during a migration installation, type 88 and press Enter inthe Installation Options menu. For more information about the installation optionsavailable in AIX 5.2, see Installation Options.

4. Verify the selections in the Migration Installation Summary screen and press Enter.

5. When the Migration Confirmation menu displays, follow the menu instructions to listsystem information or continue with the migration by typing 0 and pressing Enter.


Migration Confirmation

Either type 0 and press Enter to continue the installation, or type the

number of your choice and press Enter.

1 List the saved Base System configuration files which will not be

merged into the system. These files are saved in /tmp/bos.

2 List the filesets which will be removed and not replaced.

3 List directories which will have all current contents removed.

4 Reboot without migrating.

Acceptance of license agreements is required before using system.

You will be prompted to accept after the system reboots.

>>> 0 Continue with the migration.

88 Help ?

+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

WARNING: Selected files, directories, and filesets (installable options)

from the Base System will be removed. Choose 2 or 3 for more information.

>>> Choice[0]:

Step 4. Verify System Configuration after InstallationAfter the migration is complete, the system will reboot. Verify the system configuration, asfollows:

1. On systems with a graphics display, after a migration installation, the ConfigurationAssistant opens. On systems with an ASCII display, after a migration installation, theInstallation Assistant opens.

For more information on the Configuration Assistant or the Installation Assistant, seeConfiguring the Operating System on page 9-1.

2. Select the Accept Licenses option to accept the electronic licenses for the operatingsystem.

3. Verify the administrator (root user) password and network communications (TCP/IP)information.

Use any other options at this time. You can return to the Configuration Assistant or theInstallation Assistant by typing configassist or smitty assist at the command line.

4. Select Exit the Configuration Assistant and select Next. Or, press F10 (or ESC+0 ) toexit the Installation Assistant.

5. If you are in the Configuration Assistant, select Finish now, and do not startConfiguration Assistant when restarting AIX and select Finish.

When the login prompt displays, log in as the root user to perform system administrationtasks.


Perform a Nonprompted New and Complete Overwrite BaseOperating System Installation from CD

Using this scenario, you can perform a nonprompted new and complete overwrite baseoperating system installation from CD. The first time you install, the base operating system(BOS) installation program presents menus from which you must choose setup options.

For subsequent installations, you can change many aspects of the default BOS installationprogram by editing the bosinst.data file. The bosinst.data file directs the actions of theBOS installation program. The file resides in the /var/adm/ras directory on the installedmachine only, and it is not accessible on the commercial tape or the CD on which youreceived AIX 5.2.

Also, the bosinst.data file can be used to replicate one set of installation settings on othermachines. For example, system administrators can create a bosinst.data file with settingsthat can be used to install all the machines they support that have the same configuration.

In this scenario, you will create a bosinst.data file that will not prompt the user during theBOS installation menus.

In this scenario, you will do the following:

• Create a customized bosinst.data file

• Create a supplementary diskette

• Boot from the AIX product CD

If you are overwriting an existing system, gather the TCP/IP information from the systembefore you begin this scenario. Attention: This procedure requires shutting down andreinstalling the base operating system. Whenever you reinstall any operating system,schedule your downtime when it least impacts your workload to protect yourself from apossible loss of data or functionality. Before you perform a new and complete overwriteinstallation, ensure you have reliable backups of your data and any customized applicationsor volume groups. For instructions on how to create a system backup, refer to CreatingSystem Backups on page 14-2.

Create a Customized bosinst.data File1. Use the cd command to change your directory to the /var/adm/ras directory.

2. Copy the /var/adm/ras/bosinst.data file to a new name, such as bosinst.data.orig.This step preserves the original bosinst.data file.


3. Edit the bosinst.data file with an ASCII editor as follows:

Note: The following example includes automatic acceptance of Software LicenseAgreements.

control_flow:

CONSOLE = /dev/lft0 INSTALL_METHOD = overwrite PROMPT = no EXISTING_SYSTEM_OVERWRITE = yes INSTALL_X_IF_ADAPTER = yes

RUN_STARTUP = yes

RM_INST_ROOTS = no

ERROR_EXIT =

CUSTOMIZATION_FILE =

TCB =

INSTALL_TYPE = full

BUNDLES =

SWITCH_TO_PRODUCT_TAPE = no

RECOVER_DEVICES = yes

BOSINST_DEBUG = no

ACCEPT_LICENSES = yes

INSTALL_64BIT_KERNEL =

INSTALL_CONFIGURATION =

DESKTOP = CDE

target_disk_data:

LOCATION =

SIZE_MB =

HDISKNAME = hdisk0

locale

BOSINST_LANG = en_US

CULTURAL_CONVENTION = en_US

MESSAGES = C

KEYBOARD = en_US

4. Verify the contents of the edited bosinst.data file using the bicheck command:

/usr/lpp/bosinst/bicheck bosinst.data

5. Copy the edited file to the root directory:

cp /var/adm/ras/bosinst.data /bosinst.data

Create a Supplementary Diskette1. Create an ASCII file consisting of one word:

data

2. Save the new ASCII file, naming it signature.

3. Copy the signature file to the root directory.

4. Create the supplementary diskette and use it for installation:

– Back up the edited bosinst.data file and the new signature file to the diskette withthe following command:

ls ./bosinst.data ./signature | backup –iqv

Note: Make sure you back up the files to the diskette relative to the rootpath.


Boot from the AIX Product CD1. Insert the diskette in the diskette drive of the target machine you are installing.

2. Insert the AIX Volume 1 CD in the CD–ROM drive.

3. Boot the system.

The BOS installation program uses the customized bosinst.data file on the diskette, ratherthan the default bosinst.data file shipped with the installation media to answer thequestions in the BOS menus. If you filled in the values correctly in the bosinst.data file, theBOS installation will begin. If the BOS installation program detects an error with a value inthe bosinst.data file, the BOS menus will display with a message explaining whatinformation needs to be corrected.


Create and Install a Software BundleUsing this scenario, you can create a user–defined software bundle and install its contents.A user–defined software bundle is a text file ending in.bnd that is located in the/usr/sys/inst.data/user_bundles path. By creating the software bundle file in the/usr/sys/inst.data/user_bundles path, SMIT (System Management Interface Tool) canlocate the file and display it in the bundle selection screen.


• Create a user–defined software bundle that contains Netscape Communicator – U.S.Version, the HTTP Server Base Run–Time, and the Web–based System ManagerSecurity application, which are located on the Expansion Pack

• Install the software bundle

• Verify the installation of the software bundle was successful

It is recommended that you first perform a system backup to ensure safe system recovery.For instructions on how to create a system backup, refer to Creating System Backups onpage 14-2.

The following procedure shows you how to create a software bundle and install its contents.

Step 1. Create a User–Defined Software Bundle1. Create a text file with the extension.bnd in the /usr/sys/inst.data/user_bundles path by

running the following:

# vi /usr/sys/inst.data/user_bundles/ MyBundle .bnd

2. Add the software products, packages, or filesets to the bundle file with one entry per line.Add a format–type prefix to each entry. For this example, we are dealing with AIX installppackages, so the format–type prefix is I:. Type the following in the MyBundle.bnd file:

I:Netscape.communicator

I:http_server.base

I:sysmgt.websm.security

For more information on installation format types, see Software Product PackagingConcepts.

3. Save the software bundle file and exit the text editor.

Step 2. Install the Software Bundle1. Type the following at the command line:

# smitty easy_install

2. Enter the name of the installation device or directory.

3. From the selection screen, select the name of the user–defined software bundle,MyBundle, you created.


Install Software Bundle

Type or select a value for the entry field.

Press Enter AFTER making all desired changes.

+––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

| Select a Fileset Bundle |

| |

| Move cursor to desired item and press Enter. |

| |

| App–Dev |

| CDE |

| GNOME |

| KDE |

| Media–Defined |

| MyBundle |

| ... |

| ... |

| |

| F1=Help F2=Refresh F3=Cancel |

| F8=Image F10=Exit Enter=Do |

| /=Find n=Find Next |

+––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

4. Change the values provided in the Install Software Bundle screen as appropriate to yoursituation. You can change the PREVIEW only? option to yes to preview the installationof your software bundle before you install it. You might also need to accept new licenseagreements if the software in your bundle has an electronic license.


Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]

* INPUT device / directory for software /cdrom

* BUNDLE MyBundle +

* SOFTWARE to install [all] +

PREVIEW only? (install operation will NOT occur) no/yes +

COMMIT software updates? yes +

SAVE replaced files? no +

AUTOMATICALLY install requisite software? yes +

EXTEND file systems if space needed? yes +

VERIFY install and check file sizes? no +

Include corresponding LANGUAGE filesets? yes +

DETAILED output? no +

Process multiple volumes? yes +

ACCEPT new license agreements? no/yes +

Preview new LICENSE agreements? no +

F1=Help F2=Refresh F3=Cancel F4=List

Esc+5=Reset F6=Command F7=Edit F8=Image

F9=Shell F10=Exit Enter=Do

5. Press Enter to continue. Press Enter a second time to confirm your decision and beginthe installation of your software bundle.

6. Check the installation summary at the end of the installation output by scrolling to theend of the output. The output indicates whether the installation of your user–definedsoftware bundle was successful.


Step 3. Verify the Installation of the Software Bundle• Check the installation summary at the end of the installation output by scrolling to the

end of the output. The output indicates whether the installation of your user–definedsoftware bundle was successful, you may see output similar to the following:

+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

Summaries:

+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

Installation Summary

––––––––––––––––––––

Name Level Part Event Result

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

sysmgt.websm.security 5.1.0.0 USR APPLY SUCCESS

sysmgt.websm.security 5.1.0.0 ROOT APPLY SUCCESS

http_server.base.source 1.3.12.2 USR APPLY SUCCESS

http_server.base.rte 1.3.12.2 USR APPLY SUCCESS

http_server.base.rte 1.3.12.2 ROOT APPLY SUCCESS

Netscape.communicator.com 4.7.6.1 USR APPLY SUCCESS

Netscape.communicator.us 4.7.6.1 USR APPLY SUCCESS

Netscape.communicator.com 4.7.6.1 ROOT APPLY SUCCESS

Netscape.msg.en_US.communic 4.7.6.1 USR APPLY SUCCESS


Add Open Source Applications to Your AIX SystemThe AIX Toolbox for Linux Applications CD that is shipped with your base operating systemsoftware contains the most commonly used open source applications that you can use withthe AIX operating system. Your options for installing from this CD include:

• Using the SMIT install_software fast path to install RPM packages from the AIXToolbox for Linux Applications CD.

• Using the geninstall command to install RPM packages from the AIX Toolbox for LinuxApplications CD.

• Installing a bundle. Bundles group the applications you need for a basic Linux operatingenvironment, basic desktop use, GNOME or KDE desktop use, or applicationdevelopment.

• Installing from a directory of packages classified by function. These directory groupingscover a broad range of applications, shell environments, network applications,development tools, application libraries, and so on.

• Installing a single package for a particular application.

The following procedures provide examples of installing RPM packages from AIX Toolboxfor Linux Applications CD.

• To install the cdrecord and mtools RPM packages using SMIT, do the following:

1. Run the SMIT install_software fast path.

2. Enter the device name for the AIX Toolbox for Linux Applications CD (for example,/dev/cd0 ), and press Enter.

3. Use the F4 key to list the contents of the device.

4. Select the cdrecord and mtools packages, and press Enter.

5. Accept the default values for the rest of the Install Software menu fields, and pressEnter.

6. Confirm that you do want to install the software, and press Enter. The softwareinstallation process begins at this point.

• To install the cdrecord and mtools RPM packages from the command line, type thefollowing:

# geninstall –d/dev/cd0 R:cdrecord R:mtools

The software installation process begins at this point.

• Use the rpm command, which is automatically installed with the base operating systemfor AIX 5.1 and later versions, to install the bundles required for the GNOME desktopand the bc application package. Complete instructions are available on the README fileof the AIX Toolbox for Linux Applications for POWER Systems CD.

1. With your system powered on and AIX 5.1 or a later version running, insert the AIXToolbox for Linux Applications for POWER Systems CD into the CD–ROM drive ofyour system.

2. With root authority, mount the CD–ROM drive using the following command:

mount –vcdrfs –oro /dev/cd0 /mnt

The –v flag specifies the virtual file system type of cdrfs. The –o flag specifies the ro option, which means the mounted file is read–only. The device name is /dev/cd0.The directory in which you want to mount the CD–ROM is /mnt.

3. Change to the /mnt directory by using the following command:

cd /mnt


4. Use the ls command to list the contents of the CD. The listing contains the following,which you can view or print:

. The readme file contains complete instructions for installing from this CD.

. The CONTENTS file lists all packages available on this CD and provides a shortdescription of the purpose for each package.

5. In your Web browser, open the /mnt/LICENSES/index.html file to view softwarelicensing information.

6. In your terminal window, change to the ezinstall/ppc directory by using the followingcommand:

cd /mnt/ezinstall/ppc

In the next step, you use the rpm program to install GNOME by installing fourbundles (Base, Desktop Base, GNOME Base, and GNOME Apps). Alternatively, youcan install all necessary packages using the smit install_bundle fast path andselecting the GNOME bundle.

7. Install GNOME by using the following sequence of commands:

rpm –Uhv ezinstall/ppc/base/*

rpm –Uhv ezinstall/ppc/desktop.base/*

rpm –Uhv ezinstall/ppc/gnome.base/*

rpm –Uhv ezinstall/ppc/gnome.apps/*

The –U flag updates any earlier versions of each package that you might have onyour system. The –h flag prints hash marks (#) at timed intervals to indicate that theinstallation is progressing. The –v flag displays relevant informational or errormessages that occur during the installation. Your result will look similar to thefollowing:

rpm –Uhv ezinstall/ppc/desktop.base/* gdbm ##################################################

libjpeg ##################################################

libpng ##################################################

libtiff ##################################################

libungif ##################################################

readline ##################################################

zlib ##################################################

If your rpm command returns an error, it is probably caused by one of the following:

. Not enough space in your current file system. Resize the file system or changeyour mount point.

. Package is already installed. The rpm program discovered an existing package ofthe same name and version level, so it did not replace the package. A script on theCD installs only those packages from a directory that are not already installed onyour system, as shown in the following example:

/mnt/contrib/installmissing.sh ezinstall/ppc/desktop.base/*

. Failed dependencies. The packages listed in the error message must be installedbefore you can install this package or bundle.

8. Install the bc application package by using the following command:

rpm –Uhv RPMS/ppc/bc–*.rpm


Clone a rootvg Using Alternate Disk InstallationUsing this scenario, you can clone AIX running on rootvg to an alternate disk on the samesystem, install a user–defined software bundle, and run a user–defined script to customizethe AIX image on the alternate disk. Because the alternate disk installation processinvolves cloning an existing rootvg to a target alternate disk, the target alternate disk mustnot be already assigned to a volume group.

In this scenario you will do the following:

• Prepare for the alternate disk installation

• Perform the alternate disk installation and customization

• Boot off the alternate disk

• Verify the operation

For information about alternate disk installation, see Alternate Disk Installation on page15-1. Also, refer to the alt_disk_install man page.

Step 1. Prepare for the Alternate Disk Installation1. Check the status of physical disks on your system. Type:

# lspv

Output similar to the following displays:

hdisk0 0009710fa9c79877 rootvg active

hdisk1 0009710f0b90db93 None

We can use hdisk1 as our alternate disk because no volume group is assigned to thisphysical disk.

2. Check to see if the alt_disk_install fileset has been installed by running the following:

# lslpp –L bos.alt_disk_install.rte

Output similar to the following displays if the alt_disk_install fileset is not installed:

lslpp: 0504–132 Fileset bos.alt_disk_install.rte not installed.

3. Using volume 2 of the AIX installation media, install the alt_disk_install fileset byrunning the following:

# geninstall –d/dev/cd0 bos.alt_disk_install.rte


+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

Summaries:

+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+

Installation Summary

––––––––––––––––––––

Name Level Part Event Result

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

bos.alt_disk_install.rte 5.2.0.0 USR APPLY SUCCESS

4. Create a user–defined bundle called /usr/sys/inst.data/user_bundles/MyBundle.bndthat contains the following filesets:

I:bos.content_list

I:bos.games

For more information on how to create a user–defined software bundle, refer to Createand Install a Software Bundle.


5. Create a user–defined customization script called /home/scripts/AddUsers.sh thatcontains the following:

mkuser johndoe

touch /home/johndoe/abc.txt

touch /home/johndoe/xyz.txt

Step 2. Perform the Alternate Disk Installation and Customization1. To clone the rootvg to an alternate disk, type the following at the command line to open

the SMIT menu :

# smit alt_clone

2. Select hdisk1 in the Target Disk to Install field.

3. Select the MyBundle bundle in the Bundle to Install field.

4. Type /dev/cd0 in the Directory or Device with images field.

5. Type /home/scripts/AddUsers.sh in the Customization script field.

6. Press Enter to start the alternate disk installation.

7. Check that the alternate disk was created, by running the following:

# lspv


hdisk0 0009710fa9c79877 rootvg

hdisk1 0009710f0b90db93 altinst_rootvg

Step 3. Boot from the Alternate Disk1. By default, the alternate–disk–installation process changes the boot list to the alternate

disk. To check this run the following:

# bootlist –m normal –o


hdisk1

2. Reboot the system. Type:

# shutdown –r

The system boots from the boot image on the alternate disk ( hdisk1 ).

Step 4. Verify the Operation1. When the system reboots, it will be running off the alternate disk. To check this, type the

following:

# lspv


hdisk0 0009710fa9c79877 old_rootvg

hdisk1 0009710f0b90db93 rootvg

2. Verify that the customization script ran correctly, by typing the following:

# find /home/johndoe –print


/home/johndoe

/home/johndoe/.profile

/home/johndoe/abc.txt

/home/johndoe/xyz.txt


3. Verify that the contents of your software bundle was installed, by typing the following:

# lslpp –L bos.games bos.content_list


Fileset Level State Description

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

bos.content_list 5.2.0.0 C AIX Release Content List

bos.games 5.2.0.0 C Games


Configure NIM Using EZNIMUsing this scenario, you will use the SMIT EZNIM option to configure the NIM environmentfor the first time. The SMIT EZNIM option installs the bos.sysmgt.nim.master fileset andconfigures the NIM environment. The configuration involves creating the NIM database andpopulating it with several default entries. Several basic NIM resources will then be createdand defined in the NIM database.

1. Type the following:

# smitty eznim

2. Select Configure as a NIM Master, and press Enter.

3. Select Setup the NIM Master Environment, and press Enter.

4. Verify that the default selections for software source, volume group, and file system arecorrect for your environment. Change the selections, if needed.

5. Press Enter to begin configuring the NIM environment.

6. To display the NIM resources that have been created, do the following:

a. Use the SMIT eznim_master_panel fast path to open the EZNIM Master menu.

b. Select Show the NIM environment, and press Enter.


Install a Client Using NIMUsing this scenario, you can perform a new and complete BOS (base operating system)installation on a NIM client. It is assumed that you have already configured the NIM master,defined the basic NIM resources, and defined the NIM client you want to install.

For a guide on configuring the NIM environment and defining resources, see NIM TaskRoadmap on page 21-1.


1. Perform an BOS (rte) installation.

2. Use a bosinst_data resource to perform a nonprompted installation. For information onhow to create a bosinst.data file for nonprompted installation, see bosinst.data FileExample on page 11-11.

3. Use a resolv_conf resource to configure the network nameserver and domain.

It is recommended that you first perform a system backup on the client to ensure safesystem recovery. For instructions on how to create a system backup, see Creating SystemBackups on page 14-2.


# smit nim_bosinst

2. Select a target for the BOS installation operation.

3. Select rte installation for the installation type.

4. Select the lpp_source resource for the BOS installation.

5. Select the SPOT resource for the BOS installation.

6. Select the BOSINST_DATA to use during installation option, and select abosinst_data resource that is capable of performing a nonprompted BOS installation.

7. Select the RESOLV_CONF to use for network configuration option, and select aresolv_conf resource.

8. Select the Accept New License Agreements option, and select Yes.

9. Accept the default values for the remaining menu options.

10.Press Enter to confirm and begin the NIM client installation.

11.To check the status of the NIM client installation, type:

# lsnim –l va09



va09 :

class = machines

type = standalone

default_res = basic_res_grp

platform = chrp

netboot_kernel = up

if1 = master_net va09 0

cable_type1 = bnc

Cstate = Base Operating System installation is being performed

prev_state = BOS installation has been enabled

Mstate = in the process of booting

info = BOS install 7% complete : 0% of operations completed. boot = boot

bosinst_data = bid_tty_ow

lpp_source = 520lpp_res

nim_script = nim_script

resolv_conf = master_net_conf

spot = 520spot_res

cpuid = 0009710F4C00

control = master

Cstate_result = success


Create a System Backup to TapeUsing this scenario, you can create and verify a bootable system backup, also known as aroot volume group backup or mksysb image.

Step 1. Prepare for System Backup CreationBefore creating system backups, complete the following prerequisites:

• Be sure you are logged in as root user.

• If you plan to use a backup image for installing other differently configured targetsystems, you must create the image before configuring the source system, or set theRECOVER_DEVICES variable to no in the bosinst.data file. For more informationabout the bosinst.data file, refer to The bosinst.data File in the AIX 5L Version 5.2Installation Guide and Reference.

• Consider altering passwords and network addresses if you use a backup to make mastercopies of a source system. Copying passwords from the source to a target system cancreate security problems. Also, if network addresses are copied to a target system,duplicate addresses can disrupt network communications.

• Mount all file systems you want to back up. The mksysb command backs up onlymounted JFS (journaled file systems) in the rootvg. To back up file systems, use themount command.

Note: The mksysb command does not back up file systems mounted acrossan NFS network.

• Unmount any local directories that are mounted over another local directory.

Note: This backup procedure backs up files twice if a local directory ismounted over another local directory in the same file system. Forexample, if you mount /tmp over /usr/tmp, the files in the /tmp directoryare then backed up twice. This duplication might exceed the number offiles that a file system can hold, which can cause a future installation ofthe backup image to fail.

• Use the /etc/exclude.rootvg file to list files you do not want backed up.

• Make at least 8.8 MB of free disk space available in the /tmp directory. The mksysbcommand requires this working space for the duration of the backup.

Use the df command, which reports in units of 512–byte blocks, to determine the freespace in the /tmp directory. Use the chfs command to change the size of the file system,if necessary.

For example, the following command adds 12 MB of disk space to the /tmp directory of asystem with 4 MB partitions:

# chfs –a size=+24000 /tmp

• All hardware must already be installed, including external devices, such as tape andCD–ROM drives.

• The bos.sysmgt.sysbr fileset must be installed. The bos.sysmgt.sysbr fileset isautomatically installed in AIX 5.2. To determine if the bos.sysmgt.sysbr fileset isinstalled on your system, type:

# lslpp –l bos.sysmgt.sysbr

If the lslpp command does not list the bos.sysmgt.sysbr fileset, install it beforecontinuing with the backup procedure. Type the following:

# installp –agqXd /dev/cd0 bos.sysmgt.sysbr


Step 2. Create a System Backup to Tape1. Enter the smit mksysb fast path.

2. Select the tape device in the Backup DEVICE or File field.

3. If you want to create map files, select yes in the Create Map Files? field.

For more information, see Using Map Files for Precise Allocation in AIX 5L Version 5.2System Management Concepts: Operating System and Devices.

Note: If you plan to reinstall the backup to target systems other than thesource system, or if the disk configuration of the source system mightchange before reinstalling the backup, do not create map files.

4. To exclude certain files from the backup, select yes in the Exclude Files field.

For more information, see Excluding Files in System Backups in AIX 5L Version 5.2Installation Guide and Reference.

5. Select yes in the List files as they are backed up field.

6. Use the default values for the rest of the menu options.

7. Press Enter to confirm and begin the system backup process.

8. The COMMAND STATUS screen displays, showing status messages while the systemmakes the backup image. When the backup process finishes, the COMMAND: fieldchanges to OK.

9. To exit SMIT when the backup completes, press F10 (or Esc+0).

10.Remove the tape and label it. Write–protect the backup tape.

11.Record any backed–up root and user passwords. Remember that these passwordsbecome active if you use the backup to either restore this system or install anothersystem.

You have successfully created the backup of your rootvg. Because the system backupcontains a boot image, you can use this tape to start your system if for some reason youcannot boot from hard disks.


Clone a System Using a System Backup TapeWith a mksysb image, you can clone one system image onto multiple target systems. Thetarget systems might not contain the same hardware devices or adapters, require the samekernel (uniprocessor or microprocessor), or be the same hardware platform as the sourcesystem.

Beginning in AIX 5.2, all devices and kernel support are installed by default during the baseoperating system (BOS) installation process. If the Enable System Backups to install anysystem selection in the Install Software menu is set to yes, you can create a mksysbimage that boots and installs supported systems. Verify that your system is installed with alldevices and kernel support, by typing the following:

# grep ALL_DEVICES_KERNELS /var/adm/ras/bosinst.data


ALL_DEVICES_KERNELS = yes

Use this scenario if your system was not installed with all devices and kernel support duringBOS installation. Be sure to boot from the appropriate product media for your system and atthe same maintenance level of BOS (base operating system) as the installed source systemon which the mksysb was made. For example, use BOS AIX 5.2 media with a mksysbfrom a BOS AIX 5.2 system. Use this how–to when installing a system backup tape to adifferent system.


1. Boot the system with the AIX Volume 1 CD in the CD–ROM drive and the system backuptape in the tape device.

2. Select Start Maintenance Mode for System Recovery.

3. Select Install from a System Backup.

4. Select the drive containing the backup tape, and press Enter.

The system reads the media and begins the installation.

You are then prompted for the BOS installation language, and the Welcome screendisplays. Continue with the Prompted Installation, because cloning is not supported innonprompted installations.

If you are cloning from the product CD to restore a backup tape, do not remove the CD fromthe CD–ROM drive.

After the mksysb installation completes, the installation program automatically installsadditional devices and the kernel (uniprocessor or microprocessor) on your system, usingthe original product media you booted from. Information is saved in BOS installation logfiles. To view BOS installation log files, type cd /var/adm/ras and view the devinst.logfile in this directory.

If the source system does not have the correct passwords and network information, you canmake modifications on the target system now. Also, some products (such as graPHIGS)ship device–specific files. If your graphics adapter is different on the target system, verifythat the device–specific filesets for graphics–related LPPs are installed.


Clean Up a Failed Software InstallationUsing this scenario, you can clean up software products and service updates after aninterrupted or failed installation. The cleanup procedure attempts to delete items that werepartially installed or left in an incomplete state. This scenario applies only to the update orinstallation of optional software products. If your AIX 5.2 BOS installation was unsuccessful,see Troubleshooting Operating System and Optional Software Installation on page 17-1.

Note: It is recommended that you first perform a system backup before installingsoftware updates to ensure safe system recovery. For instructions on howto create a system backup, refer to Creating System Backups on page14-2.

The cleanup procedure attempts to revert the update to its previous state. For example,when cleaning up an update that was interrupted in the COMMITTING state, the cleanupprocedure attempts to return the update to its APPLIED state.

If an update installation is interrupted, run the lslpp –l command to see the current state ofthe update. For example, if you run lslpp –l on an interrupted update installation, it mightreport the update status as APPLYING rather than APPLIED.

If the interruption occurs during the initial state of an installation, then the cleanup procedureattempts to delete the installation entirely and restore the previous version of the product (ifthere is one). When the previous version is restored, it becomes the active version. Whenthe previous version cannot be restored, the software is listed by the lslpp –l command asBROKEN.

When the product is deleted or BROKEN, you can attempt to reinstall the software. Anyproduct in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.

To initiate a cleanup procedure using SMIT:

1. Type smit maintain_software on the command line.

2. Select Clean Up After Failed or Interrupted Installation and press Enter.

To initiate a cleanup procedure from the command line:Type installp –C on the command line and press Enter.

If prompted to reboot (restart) the system after running the cleanup procedure, then do sonow.

If you get a message indicating that no products were found that could be cleaned up, youmay have executed the cleanup procedure when it was not needed. Try your installationagain.

3-1Operating System and Optional Software Installation

Chapter 3. Operating System and Optional SoftwareInstallation

Part 2 provides information about installing and configuring AIX on a standalone system,regardless of network connectivity. The chapters in this part describe the different baseoperating system installation methods, including new and complete overwrite installation,migration installation, and preservation installation.

3-2 Installation and Reference Guide


Chapter 4. What’s New in Base Operating SystemInstallation and Software Installation?

This chapter gives an overview of the new features in the base operating system (BOS)installation and software installation procedures for AIX 5.2.

BOS MenusInstallation options are available for you to configure your system during a BOS installationprocess.

The installation options include the following:

• Desktop selection

• Trusted Computing Base

• Controlled Access Protection Profile (CAPP) and Evaluation Assurance Level 4+(EAL4+)

• 64–bit kernel enablement

• Enhanced journaled file system (JFS2)

• Graphics software

• Documentation services software

• Installation of all device and kernel filesets

For information about the installation options, see Installation Options.

Software Maintenance and UtilitiesThe Copy Software Bundle to Hard Disk for Future Installation option is available in theSMIT Software Maintenance and Utilities menu.

For information about the SMIT Copy Software Bundle to Hard Disk for Future Installationoption, see Copy Software Bundle to Hard Disk for Future Installation on page 12-9.

Software Service ManagementThe SMIT Software Service Management menu allows you to manage how you updatesystems with fixes and preventive maintenance package levels. You can compare levels ofdifferent systems against a base system or a base set of fixes. Support is provided throughthe command line and SMIT to allow you to compare the filesets installed on yourstandalone system with the contents of an image repository or a service report that isdownloaded from the ESCALA support Web site.

This option also allows you clean up or rename software images in a repository. Thefollowing software maintenance options are available in the SMIT Software ServiceManagement menu and the SMIT Software Maintenance and Utilities menu:

• Rename Software Images in Repository

• Clean Up Software Images in Repository


The Rename Software Images in Repository option allows you to rename software imageswith the PTF prefix to the fileset names generated by the bffcreate command. This allowsyou to determine exactly what updates are contained in a directory because the filesetname is recognizable.

The Clean Up Software Images in Repository option allows you to perform various tasks toclean up software image directories on standalone systems. This allows you to removeduplicate or unnecessary filesets from image repositories, easing management of theimages and reducing the amount of space required to store them.

For information about the SMIT Software Service Management menu, see Software ServiceManagement.

Emergency Fix ManagementThe emergency fix (efix) management solution allows users to track and manage efixes ona system. The efix management solution consists of: the efix packager (epkg) commandand the efix manager (emgr) command.

The epkg command creates efix packages that can be installed by the emgr command.The emgr command installs and removes efix packages created with the epkg command.

The efix management solution provides the following functions:

• Emergency fixes can be packaged in either interactive or template–based modes

• List all of the efixes on a given system

• Install efixes

• Remove efixes

• Force remove efixes

• Verify efixes

• Display efix package locks

For more information about efix management, see Emergency Fix Management on page12-19.

Alternate Disk Migration InstallationAlternate disk migration installation allows the user to create a copy of rootvg to a free disk(or disks) and simultaneously migrate it through Network Installation Management (NIM) toa new release level. Using alternate disk migration installation over a conventional migrationprovides several advantages:

• Less downtime (the migration is performed while the system is up normally, and there isno need to boot from any media).

• Quick recovery in case of migration failure.

• High degree of flexibility and customization.

For more information about alternate disk migration installation, see Alternate Disk MigrationInstallation.


Universal Disk Format Support for DVD–RAMThe Universal Disk Format (UDF) allows you to manipulate files directly on the DVD–RAMmedia. The system backup image is an archived file composed of many files that cannot bemanipulated. However, the installation packages and any files that are not contained in thebackup image can be directly manipulated on the DVD–RAM. After the DVD is mounted, thefiles can be changed by using an editor, or new files can be copied to the DVD using thevarious copy and restore commands (such as the cp, mv, and restore commands).

For information about the SMIT Software Service Management menu, see DVD–RAM andUniversal Disk Format on page 14-9.

Installation CommandsThe following commands have been added to AIX:

• The lsmksysb command. For further information, see Backup Options.

• The install_all_updates command. For further information, see Update InstalledSoftware to Latest Level from the Command Line.

• The lppmgr command. For further information, see Manage an Existing installp ImageSource.

• The compare_report command. For further information, see Comparison Reports.


5-1Introduction to Base Operating System Installation

Chapter 5. Introduction to Base Operating SystemInstallation

This chapter provides information about completing an installation of the AIX 5.2 baseoperating system (BOS).

The BOS installation program first restores the run–time bos image, then installs theappropriate filesets, depending on your selections. The installation program automaticallyinstalls required message filesets, according to the language you choose.

In the BOS menus, you can also configure the following options:

• Desktop selection

• Trusted Computing Base

• Controlled Access Protection Profile (CAPP) and Evaluation Assurance Level 4+(EAL4+)

• 64–bit kernel enablement

• Enhanced journaled file system (JFS2)

• Graphics software

• Documentation services software

• Installation of all device and kernel filesets

For more information about the installation options, refer to Installation Options on page 6-1.

The following installation methods are available on AIX:

New and Complete OverwriteThis method installs AIX 5.2 on a new machine or completely overwritesany BOS version that exists on your system.

For instructions on installing AIX 5.2 on a new machine or to completelyoverwrite the BOS on an existing machine, refer to New and CompleteOverwrite Installation / Preservation Installation on page 7-1.

Preservation This method replaces an earlier version of the BOS but retains the rootvolume group, the user–created logical volumes, and the /home filesystem. The system file systems /usr, /var, /tmp, and / (root) areoverwritten. Product (application) files and configuration data stored inthese file systems will be lost. Information stored in other non–system filesystems will be preserved.

For instructions on preserving the user–defined structure of an existingBOS, refer to New and Complete Overwrite Installation / PreservationInstallation on page 7-1.

Migration This method upgrades from AIX 4.3 or earlier versions of the BOS to AIX5.2. The migration installation method is used to upgrade from an existingversion or release of AIX to a later version or release of AIX. A migrationinstallation preserves most file systems, including the root volume group,logical volumes, and system configuration files. It overwrites the /tmp filesystem.

For instructions on migrating an existing version or release of AIX to a laterversion or release of AIX, refer to Migration Installation on page 8-1.


The following table shows the differences in the installation steps among the installationmethods.

Table 2. AIX BOS Installation Methods

Installation Steps New and CompleteOverwrite

Preservation Migration

Create rootvg Yes No No

Create file system /,/usr, /var

Yes Yes No

Create file system/home

Yes No No

Save Configuration No No Yes

Restore BOS Yes Yes Yes

Install AdditionalFilesets

Yes Yes Yes

RestoreConfiguration

No No Yes

BOS MenusAfter you select the console and language to be used for the BOS menus, the Welcome toBase Operating System Installation and Maintenance screen displays, as follows:




>>> 1 Start Install Now with Default Settings



88 Help ?

99 Previous Menu

>>> Choice [1]:

Note: To turn on the debug mode for the BOS installation process, type 911 inthe Choice field and press Enter. The Welcome to Base Operating SystemInstallation and Maintenance screen refreshes and the BOS installationprocess runs in debug mode when the installation occurs. Continue theprocedure for selecting options and specifying data until the installationbegins. Debug output is sent to the client’s display as the installationproceeds.

5-3Introduction to Base Operating System Installation

If you select Start Install Now with Default Settings, the BOS command determines thedefault installation method to use based on your system’s configuration. A summary screendisplays, similar to the following, where you can confirm the installation method andinstallation options:

Overwrite Installation Summary

Disks: hdisk0

Cultural Convention: en_US

Language: en_US

Keyboard: en_US

64 Bit Kernel Enabled: No

JFS2 File Systems Created: No Desktop:

Enable System Backups to install any system: Yes

Optional Software being installed:

HTTP_Server (Expansion Pack)

Kerberos_5 (Expansion Pack)

>>> 1 Continue with Install

88 Help ?

99 Previous Menu

>>> Choice [1]:

If the selections are correct, press Enter to begin the BOS installation.

However, if you would like to change the installation method or options, selectChange/Show Installation Settings and Install at the BOS welcome screen. TheInstallation and Settings screen displays, as follows:

Installation and Settings

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 System Settings:

Method of Installation.............New and Complete Overwrite


2 Primary Language Environment Settings (AFTER Install):

Cultural Convention................English (United States)

Language ..........................English (United States)

Keyboard ..........................English (United States)

Keyboard Type......................Default

3 More Options (Desktop, Security, Kernel, Software, ...)

>>> 0 Install with the current settings listed above.

+–––––––––––––––––––––––––––––––––––––––––––––––––––––

88 Help ? | WARNING: Base Operating System Installation will

99 Previous Menu | destroy or impair recovery of ALL data on the

| destination disk hdisk0.

>>> Choice [0]:

For more information on the BOS menu options, refer to the Help at any time by typing 88in the Choice field. For conceptual information on the BOS installation procedures, refer tothe following sections:

• New and Complete Overwrite Installation / Preservation Installation

• Migration Installation

For how–to instructions for performing BOS installations, refer to the following:

• Perform a New and Complete Overwrite Base Operating System Installation from CD

• Perform a Migration Base Operating System Installation from CD


Electronic License AgreementsAIX 5.2 ships with software license agreements that can be viewed electronically. If aproduct has an electronic license agreement, it must be accepted before softwareinstallation can continue. In the case of initial BOS installation, you can view and accept orreject license agreements in a license agreement dialog after the installation has occurred,but before the system is available for use as part of Configuration Assistant (graphicsconsoles) or Installation Assistant (ASCII consoles).

The AIX BOS has a license agreement, but not all software packages do. When you agreeto the license agreement for BOS installation, you are also accepting all license agreementsfor any software installed automatically with the BOS. Some software, such as the GNOMEor KDE desktops, can be optionally installed during BOS installation; the appropriatelicensing information for such software is displayed separately.

If a customized bosinst.data file is used (usually for unattended installations, ornonprompted installations), the ACCEPT_LICENSES field in the control_flow stanza canbe used to accept the license agreements so users are not prompted at reboot time. Whenperforming a ”push” installation using the Network Installation Management (NIM)environment, the licenses must be accepted, either from the choices made when initializingthe installation or in a customized bosinst.data file, before the installation can continue. Formore information about the bosinst.data file, refer to The bosinst.data File on page 11-1.

For additional software package installations, the installation cannot occur unless theappropriate license agreements are accepted. This option, as well as options to previewlicenses, is offered in both the System Management Interface Tool (SMIT) and theWeb-based System Manager installation interfaces. When using the installp command, usethe –Y flag to accept licenses and the –E flag to view license agreement files on the media.

For more information about license manipulation, refer to the inulag command descriptionin the AIX 5L Version 5.2 Commands Reference.

6-1Installation Options

Chapter 6. Installation Options

This chapter provides information about installation options for the AIX base operatingsystem. The installation options are available by typing 3 in the More Options field in theInstallation and Settings screen.

On 32–bit systems, the new and complete overwrite installation options are the following:

Install Options

1. Desktop........................................ NONE, CDE, GNOME, KDE

2. Enable Trusted Computing Base.................................... No

3. Graphics Software................................................ Yes

4. Documentation Services Software.................................. Yes

5. Enable System Backups to install any system...................... Yes

(Installs all devices and kernels)

>>> 6. Install More Software

0 Install with the current settings listed above.

88 Help ?

99 Previous Menu

>>> Choice [6]:

On 64–bit systems, the new and complete overwrite installation options are the following:

Install Options

1. Desktop...................................... NONE, CDE, GNOME, KDE


3. Enable CAPP and EAL4+ Technology................................. No

(English only, 64–bit kernel enablement, JFS2 file systems)

4. Enable 64–bit Kernel............................................. No

5. Create JFS2 File Systems......................................... No

(Requires 64–bit Kernel Enabled)

6. Graphics Software................................................ Yes

7. Documentation Services Software.................................. Yes





88 Help ?

99 Previous Menu

>>> Choice [9]:


On 64–bit systems, the preservation installation options are the following:

Install Options

1. Desktop............................................NE, CDE, GNOME. KDE


3. Import User Volume Groups........................................ Yes

4. Graphics Software................................................ No

5. Documentation Services Software.................................. No





88 Help ?

99 Previous Menu

>>> Choice [9]:

On 64–bit systems, the migration installation options are the following:

Install Options


2. Import User Volume Groups........................................ Yes



4. Remove Java 1.1.8 Software....................................... No


88 Help ?

99 Previous Menu

>>> Choice [0]:

The following are the installation options available:

Desktop The default is CDE for new and complete overwrite installations. If youselect NONE, a minimal configuration is installed including X11, Java, perl,SMIT, and the Web-based System Manager (if Graphics Software isselected).

If you select GNOME or KDE, the BOS installation process prompts you forthe AIX Toolbox for Linux Applications CD. If this CD is not available, youcan type q to continue the installation without the AIX Toolbox for LinuxApplications CD.

Enable Trusted Computing BaseThe Trusted Computing Base (TCB) is the part of the system that isresponsible for enforcing the information security policies of the system. Allof the computer’s hardware is included in the TCB, but a personadministering the system should be concerned primarily with the softwarecomponents of the TCB.

If you install the Trusted Computing Base option, you enable the trustedpath, trusted shell, and system–integrity checking ( tcbck command).These features can be enabled only during BOS installation.

The choices are yes and no. To enable the Trusted Computing Base, type2 and press Enter. The default is no.

Enable CAPP and EAL4+ TechnologyAvailable in a new and complete overwrite installation. If you enableControlled Access Protection Profile (CAPP) and Evaluation AssuranceLevel 4+ (EAL4+), other restrictions exist on installation choices, such as:

. Desktop = CDE or NONE

. TCB = yes

6-3Installation Options

. 64–bit kernel = yes

. JFS2 = yes

. Enable System Backups to install any system (Installs all devices andkernels) = no

. Install more software options = no

For information about CAPP and EAL4+, see Controlled Access ProtectionProfile and Evaluation Assurance Level 4+ in the AIX 5L Version 5.2Security Guide.

Import User Volume GroupsAvailable in migration installation and preservation installation. You have theoption to have user volume groups imported after the installation completes.These volume groups can be manually imported at a later time.

Enable 64–bit KernelAvailable only on 64–bit Common Hardware Reference Platform (CHRP)systems.To toggle the choice between no (the default) and yes, type 3 and pressEnter. If you choose no, the 64–bit kernel is still installed, but it is not linkedto the running /unix. If you choose yes, the 64–bit kernel is installed andbegins running when your system reboots.

Create JFS2 File SystemsAvailable in new and complete overwrite installation, as well as preservationinstallation with 64–bit kernel enabled option. Create enhanced journaledfile systems during BOS installation.

Graphics SoftwareAvailable in new and complete overwrite installation, as well as preservationinstallation. Install graphics software support.

Documentation Services SoftwareAvailable in new and complete overwrite installation, as well as preservationinstallation. Install the documentation services software.

Remove Java 1.1.8 SoftwareAvailable in migration installation and preservation installation. You have theoption to have all Java version 1.1.8 software removed.

Enable System BackupsIf Enable System Backups to install any system is selected, all devices andkernels are installed, so that a system backup can be installed on a differentsystem. For more information about installing a system backup to a differentsystem, see Cloning a System Backup on page 14-16.


The Install More Software option is available in the new and complete overwrite installationmethod, as well as the preservation installation method. Select Install More Software tochoose additional software to install after the BOS installation process finishes. A softwarebundle file corresponds to each selection that contains the required packages and filesets.The following software bundles are available:

Install More Software

1. Netscape (Expansion Pack)......................................... No

2. HTTP_Server (Expansion Pack)...................................... Yes

3. Kerberos_5 (Expansion Pack)....................................... Yes

4. Server (Volume 2)................................................ No

5. Alternate Disk Install (Volume 2)................................ No


88 Help ?

99 Previous Menu

>>> Choice [0]:

7-1New and Complete Overwrite Installation / Preservation Installation

Chapter 7. New and Complete Overwrite Installation /Preservation Installation

This chapter provides information on the New and Complete Overwrite Installation operationand the Preservation Installation operation.

Step 1. Complete the PrerequisitesBefore starting the installation, complete the following prerequisites:


• All requisite hardware, including any external devices (such as tape drives, CD–ROM orDVD–ROM drives), must be physically connected. If you need further information, referto the hardware documentation that accompanied your system.

• The installation media must be loaded in the boot device.

• The system must be set to boot from the device in which the installation media is loaded.Refer to the hardware documentation that accompanied your system for instructions onsetting the boot device.


• If the system you are installing is currently running, create or locate a backup of thesystem. For instructions on how to create a system backup, refer to Creating SystemBackups.

• If your system needs to communicate with other systems and access their resources,make sure you have the information in the following worksheet before proceeding withinstallation:

Network Attribute Value

Network Adapter

Host Name

IP Address _______.________.________.________

Network Mask _______.________.________.________

Nameserver _______.________.________.________

Domain Name

Gateway _______.________.________.________

Step 2. Prepare Your System for InstallationPrepare for a new and complete overwrite or preservation installation by doing the following:


2. Shut down your system. If your machine is currently running, power it off now byfollowing these steps:

a. Log in as the root user.


b. Type the following command:

shutdown –F

c. If your system does not automatically power off, place the power switch in the Off ( 0) position. Attention: You must not turn on the system unit until instructed to do so inStep 4. Boot from Your Installation Media on page 7-3 .

3. Turn on all attached external devices. These include the following:

– Terminals

– CD–ROM or DVD–ROM drives

– Tape drives

– Monitors

– External disk drives

Turning on the external devices first is necessary so the system unit can identify eachperipheral device during the startup (boot) process.

Step 3. Set Up an ASCII TerminalIf you are using a graphics terminal, skip directly to Step 4. Boot from Your InstallationMedia.

If you are using an ASCII terminal, use the criteria listed below and your terminal referencedocumentation to set the communications, keyboard, and display options. The followingsettings are typical, but your terminal might have different option names and settings thanthose listed here.

Note: If your terminal is an IBM 3151, 3161, or 3164, press the Ctrl+Setup keysto display the Setup Menu and follow the on–screen instructions to setthese options.

Communication Options

Option Setting

Line Speed (baud rate) 9600

Word Length (bits per character) 8

Parity no (none)

Number of Stop Bits 1

Interface RS–232C (or RS–422A)

Line Control IPRTS

Keyboard and Display Options

Option Setting

Screen normal

Row and Column 24x80

Scroll jump

Auto LF (line feed) off

Line Wrap on

Forcing Insert line (or both)

Tab field


Operating Mode echo

Turnaround Character CR

Enter return

Return new line

New Line CR

Send page

Insert Character space

Step 4. Boot from Your Installation Media1. Turn the system unit power switch from Off ( 0 ) to On ( | ).



The system begins booting from the installation media.

3. If you have more than one console, each might display a screen that directs you to pressa key to identify your system console. A different key is specified for each consoledisplaying this screen. If this screen displays, press the specified key only on the consoleyou want to use for the installation. (The system console is the keyboard and displaydevice used for installation and system administration.)

A screen displays, asking you to select a language to be used during installation.

4. Select the language you prefer to use during installation.

5. When the Welcome to Base Operating System Installation and Maintenance screendisplays, type 2 in the Choice field to select Change/Show Installation Settings andInstall and press Enter. Go to Step 5. Verify or Change the Installation Settings on page7-3 for instructions on verifying or changing installation settings.

Step 5. Verify or Change the Installation SettingsVerify the default installation settings from the Installation and Settings screen. If theinstallation and system settings are correct, type 0 in the Choice field and press Enter.Confirm that the selections on the installation summary screen are correct, and press Enterto begin the BOS installation. Go to Step 6. Finish the BOS Installation.

To change the installation settings, use the following procedure:

1. Select either New and Complete Overwrite Installation or Preservation Installation.

a. Type 1 in the Choice field to select the System Settings option.

b. When the Change Method of Installation screen displays, type the numbercorresponding to desired installation (either 1 for New and Complete Overwrite or 2for Preservation) in the Choice field and press Enter.

Note: Available installation methods depend on whether your system has aprevious version of AIX installed.

If you only want to install the next recommended maintenance level of AIX, seeInstalling Optional Software Products and Service Updates. You can also use


the SMIT update_all fast path or the install_all_updates command to updateexisting filesets to the next recommended maintenance level.

c. When the Change Disk(s) screen displays, you can change the destination disk forthe installation. If you selected the preservation installation, the screen lists only diskscontaining a rootvg.

The disk name, the location, the size of the disk, and the root volume group status isdisplayed for each available disk. The Bootable column indicates whether the disk isbootable. Type 77 to select Display More Disk Information to view additional diskattributes such as physical volume identifier, device adapter connection location, orWorld Wide Port Name//Lun ID.

If the default shown is correct, type 0 in the Choice field and press Enter. To changethe destination disk, use the following procedure:

i. Type the number for each disk you choose in the Choice field and press Enter. Donot press Enter a final time until you have finished selecting all disks. If you needto deselect a disk, type its number a second time and press Enter.

– You can specify a supplemental disk by typing 66 and pressing the Enter keyfor the Disks not known to Base Operating System Installation option. Thisoption opens a new menu that prompts for a device support media for thesupplemental disk. The device–support media is only needed when the devicecannot configure with the generic SCSI or bus–attached device drivers. BOSinstallation configures the system for the disk and then returns to the ChangeDisk screen.

ii. When you have finished selecting the disks, type 0 in the Choice field and pressEnter. The Installation and Settings screen displays with the selected disks listedunder System Settings.

2. Change the primary language environment, if needed. Use the following steps to changethe primary language used by this installation.

Note: Changes to the primary language environment do not take effect untilafter BOS is installed and your system is rebooted.

a. Type 2 in the Choice field on the Installation and Settings screen to select thePrimary Language Environment Settings option.

b. Select the appropriate set of cultural convention, language, and keyboard options.Most of the options are a predefined combination, however, you can define your owncombination of options.

. To select a predefined Primary Language Environment, type that number in theChoice field and press Enter.

. To configure your own primary language environment:

i. Select MORE CHOICES.

ii. Page through the choices and select the Create Your Own Combinationoption.

iii. When the Set Primary Cultural Convention screen displays, type the number inthe Choice field that corresponds to the cultural convention of your choice andpress Enter.

iv. When the Set Primary Language screen displays, type the number in theChoice field that corresponds to your choice for the primary language and pressEnter.

v. When the Set Keyboard screen displays, type the number in the Choice fieldthat corresponds to the keyboard attached to the system and press Enter.

3. Change the installation options by typing 3 to select More Options and press Enter. Formore information on the installation options, see Installation Options.


4. Verify your selections in the installation summary screen and press Enter to begin theBOS installation process.

Your system automatically reboots after installation is complete. Go to Step 6. Finish theBOS Installation.

Step 6. Finish the BOS Installation1. The Installing Base Operating System screen displays the status of your installation.

After the base run–time environment is installed, status information displays about othersoftware that is being installed.

2. The system automatically reboots.

3. After the system has restarted, you are prompted to configure your installation. Forinformation on configuring your system after a BOS installation process, refer toConfiguring the Operating System on page 9-1.

Note: If the system being installed has 4 GB or more of memory and you haveperformed an overwrite installation, then a dedicated dump device iscreated for you. If so, the device name is /dev/lg_dumplv, and its size isbased on the following formula:

4>= RAM < 12 size of dump device= 1 GB



RAM >= 48 size of dump device= 4 GB

Related Information• For additional release information, see the AIX 5.2 Release Notes.

• For late–breaking information, which might include information on the configurationprocess and installed software, refer to readme files. For information on how to viewreadme files, see Viewing Readme Files.

• For information about installing optional software, refer to Installing Optional SoftwareProducts and Service Updates.


8-1Migration Installation

Chapter 8. Migration Installation

Migration is the default installation method to move from AIX 4.2 and later to AIX 5.2.

Note: If you only want to install the next recommended maintenance level of theoperating system, use the SMIT update_all fast path or the install_all_updatescommand to update the filesets currently installed. For more information about updatingto the next recommended maintenance level of AIX, see Optional Software Products andService Updates on page 12-1.

During a migration, the installation process determines which optional software products areinstalled on the existing version of the operating system. Components from previousreleases that have been replaced by new software in AIX 5.2 are installed at the AIX 5.2level.

Migration attempts to preserve all user configuration, while moving the operating system toa new level of software. The following steps are taken to achieve this objective:

• Save configuration files

• Prepare and remove old files

• Restore new files

• Remove unsupported or unnecessary filesets

• Migrate configuration data wherever possible

• Prepare VPD for install

• Update additional filesets

When performing a migration, the following occurs:

• All files in the /usr/lib/drivers, /usr/lib/microcode, /usr/lib/methods and /devdirectories are removed from the system, so software support for device drivers must bereinstalled. Non–device software products and applications remain on the system, andwork correctly if they are among those files described in Binary Compatibility BetweenEarlier Versions and AIX 5.2 on page 8-2.

• The following software products are removed from the system:

– AIXwindows Interface Composer

– Remote Customer Services

– AIXwindows Development Environment

– Display PostScript functionality from AIXwindows Run–Time Environment Extensions

– Performance Tools functionality from Extended Commands

– OpenGL and graPHIGS

– Xstation Manager

In most cases, user–configuration files from the previous version of a product are savedwhen the new version is installed during a migration installation.


Binary Compatibility Between Earlier Versions and AIX 5.2After a migration installation, you might notice filesets on the system in the OBSOLETEstate. Obsolete filesets were installed by earlier versions of the operating system, but theyremain on the current system because the migration only replaced some, but not all, of thefiles they contain. These filesets remain necessary for systems running mixed levels of theoperating system.

During a migration installation, the following filesets are automatically included:

• Base operating system commands

• Base operating system libraries

• Base operating system curses/termcap

• Base operating system networking

• Base operating system directories/files (symlinks)

• Messages

• X11R3

• X11R4

• X11 fonts

All operating system applications based on AIX 4.2 and those intended for use with POWERfamily, POWER2, and POWER–based models run compatibly on AIX 5.2 withoutrecompilation for those same models. The only exceptions to this statement are applicationsusing the following:

• Unsupported self–loadable kernel extensions

• Certain High–Function Terminal (HFT) control interfaces

• X11R3 input device interfaces

• CIO LAN device driver interface

• SCSI device configuration methods (IHVs)

• nlist subroutine interface

• DCE threads

• Applications compiled using POWER2 or POWER–based compiler options, but executedon models other than POWER2 or POWER–based models.

Note: Any program that must run in all environments (POWER family, POWER2, andPOWER–based models 601 and higher) must be compiled using the common modeof the compiler. Programs compiled to exploit POWER2 technology must be run onPOWER2 processors. Existing code need not be recompiled to run.

A system using AIX 4.2 can operate as a server system for client machines using AIX 5.2with the following exceptions:

• Network installation of AIX 5.2 clients

• Service SNA or X.25 to AIX 5.2 clients

• Service HCON to AIX 5.2 clients

• Service CGE extensions of PEX and PEX–PHIGS

• Use of AIX 5.2 client installation formats

Font servers might be required on the AIX 5.2 clients to reliably handle AIXwindowsbetween server and client.


A system using AIX 5.2 might operate as a server system for client machines using AIX 4.2or later versions as long as the necessary compatibility options are installed. All statementsabout binary compatibility apply in this case. AIX 5.2 applications might not execute reliablyon AIX 4.2 systems using remote network mounts from an AIX 5.2 file system.

Pre–Migration and Post–Migration CheckingThe pre_migration and post_migration commands perform various system checks toensure a successful migration installation. Both commands are shipped in the bos.rtefileset.

In case the pre_migration command does not exist on a level of AIX that you want to checkbefore performing a migration installation, the pre_migration command is also located inthe /usr/lpp/bos directory of the CD file system. Copy the pre_migration command fromthe /usr/lpp/bos directory of the new AIX CD version you are about to perform themigration.

The output from the pre_migration command is saved to the system in the/home/pre_migration date directory.

The pre_migration command performs the following actions:

• List the device filesets being removed.

• List all other filesets being removed.

• List the saved base configuration files that will not be merged.

• List configuration files that will be merged.

• Verify fileset version consistency.

• Create a list of all filesets installed, to be used by the post_migration command.

• Check the size and location of the boot logical volume.

• Check the major number for rootvg is 10.

• Check for the missing DB directory for the bos.net.ipsec.keymgt fileset.

• Determine if Kerberos is being used.

• Check disk and memory sizes.

• If migrating from AIX 4.2, verify that the correct updates are applied.

• Verify system platform.

• Print a recommendation that a system backup be made before the migration.

The output from the post_migration command is saved in the /home/post_migration datedirectory.

The post_migration command performs the following actions:

• Verify fileset version consistency.

• Check the installation list from before the migration, and inform the user of any filesetsthat might still need migrating.

• Compare saved and merged configuration scripts and save the differences.


Migrating to AIX 5.2Notes:

1. The boot logical volume requires 12 MB of contiguous disk space. During migrations, theinuextendblv command runs to ensure there are contiguous partitions for hd5. Ifcontiguous partitions are not present, the inuextendblv command attempts to createthem. If the partitions are not present and the inuextendblv command fails to createthem, the migration is stopped.

2. The settings in your bootlist are not migrated. After a migration, the bootlist is set to theprimary boot device.

Use the following steps to migrate your current version of the operating system to the AIX5.2 BOS:

• Step 1. Complete the Prerequisites

• Step 2. Prepare Your System for Installation

• Step 3. Boot from Your Installation Media

• Step 4. Finish the BOS Migration Attention: This procedure requires shutting down andreinstalling the base operating system. Whenever you reinstall any operating system,schedule your downtime when it least impacts your workload to protect yourself from apossible loss of data or functionality. Before you perform a migration installation, ensurethat you have reliable backups of your data and any customized applications or volumegroups. For instructions on how to create a system backup, refer to Creating SystemBackups.

Step 1. Complete the PrerequisitesBefore starting the migration, complete the following prerequisites:

• All requisite hardware, including any external devices (such as tape, CD, or DVD–ROMdrives), must be physically connected. If you need further information, refer to thehardware documentation that accompanied your system.

• Before migrating your BOS to AIX 5.2, ensure that the root user has a primaryauthentication method of SYSTEM. You can check this condition by typing the followingcommand:

# lsuser –a auth1 root

Change the value, if needed, by typing the following command:

# chuser auth1=SYSTEM root


• Verify that your applications runs on AIX 5.2. Also, verify that your applications arebinary–compatible with AIX 5.2. If your system is an application server, verify that thereare no licensing issues. Refer to your application documentation or provider to verify onwhich levels of AIX your applications are supported and licensed.

• Verify that all currently installed software is correctly entered in the Software VitalProduct Database (SWVPD), by using the lppchk command. To verify that all filesetshave all required requisites and are completely installed, type the following:

# lppchk –v

• Verify that your hardware microcode is up–to–date.

• All requisite hardware, including any external devices (such as tape, CD, or DVD–ROMdrives), must be physically connected and powered on. If you need further information,refer to the hardware documentation that accompanied your system.


• Use the errpt command to generate an error report from entries in the system error log.To display a complete detailed report, type the following:

# errpt –a


• Make a backup copy of your system software and data. For instructions on how to createa system backup, refer to Creating System Backups on page 14-2.

Step 2. Prepare Your System for InstallationPrepare for migrating to the AIX 5.2 BOS by doing the following:


2. Shut down your system. If your machine is currently running, power it off now byfollowing these steps:


b. Type the following command:

# shutdown –F

c. If your system does not automatically power off, place the power switch in the Off( 0 ) position.

Attention: You must not turn on the system unit until instructed to do so in Step 3.Boot from Your Installation Media.

3. Turn on all attached external devices. These include the following:

– Terminals

– CD or DVD–ROM drives

– Tape drives

– Monitors


Turning on the external devices first is necessary so the system unit can identify eachperipheral device during the startup (boot) process.

Step 3. Boot from Your Installation MediaIf you are using an ASCII console that was not defined in your previous system, completeStep 3. Set Up an ASCII Terminal on page 7-2 before proceeding.

The following steps migrate your current version of the operating system to AIX 5.2:

1. Turn the system unit power switch from Off ( 0 ) to On ( | ).

2. When the system beeps twice, press F5 on the keyboard (or 5 on an ASCII terminal). Ifyou have a graphics display, you see the keyboard icon on the screen when the beepsoccur. If you have an ASCII terminal (also called a tty terminal), you see the wordkeyboard when the beeps occur.


The system begins booting from the installation media.

3. If your system has an LED display, the three–digit LED should display c31.

If you have more than one console, each might display a screen that directs you to pressa key to identify your system console. A different key is specified for each console


displaying this screen. If this screen displays, press the specified key only on the deviceto be used as the system console. (The system console is the keyboard and displaydevice used for installation and system administration.) Press a key on one console only.

A screen displays, asking you to select a language to be used for installationinstructions.

4. Select the language you prefer to use for installation instructions.

5. When the Welcome to Base Operating System Installation and Maintenance screendisplays, either begin the migration immediately by typing 1 to select Start Install Nowwith Default Settings, or verify the installation and system settings by typing 2 to selectChange/Show Installation Settings and Install. If you want to change any settings,follow the procedure in Step 5. Verify or Change the Installation Settings on page 7-3 .

Notes:

. You should not have to change settings simply to select the migration installationmethod. If a previous version of the operating system exists, the installationmethod defaults to migration.

. The available installation methods vary, depending on the version of the operatingsystem that is currently installed (before migration). For information about the BOSinstallation methods, refer to Introduction to Base Operating System Installation onpage 5-1. For information about the installation options available for a migrationinstallations, refer to Installation Options on page 6-1.

6. Verify the selections in the Migration Installation Summary screen and press Enter.

7. Confirm the migration installation process in the Migration Confirmation screen, andpress Enter to begin the migration installation.

Step 4. Finish the BOS MigrationAfter prompting for confirmation, the installation process begins. The Installing BaseOperating System screen displays.

As the installation progresses, the numbers increment in the fields that show percentagecomplete and elapsed time to indicate the installation status. After the base run–timeenvironment is installed, status information displays about other software that is beinginstalled. After the BOS installation is complete, the system automatically reboots.

After the system has restarted, you are prompted to configure your installation of the BOS.Go to Configuring the Operating System for information on the configuration process.

Note: If there is not enough space to migrate all of the usually migrated software, acollection of software called a Migration Bundle is available when you install additionalsoftware later. You must create additional disk space on the machine on which you wantto install, and then you can run smit update_all to complete the installation, duringwhich the Migration Bundle is installed.

If you are not doing the installation from a graphics console, a Graphics_Startup bundleis created. Refer to Installing Optional Software Products and Service Updates for moreinformation about installing software bundles and for information on migrating orinstalling optional software products. Maintaining Optional Software Products andService Updates describes how to remove software from the system to release diskspace.


Related Information• For additional release information, see the AIX 5.2 Release Notes.

• For late–breaking information, which might include information on the configurationprocess and installed software, refer to readme files. For information on how to viewreadme files, see Viewing Readme Files on page iii.

• For information about installing optional software, refer to Installing Optional SoftwareProducts and Service Updates on page 12-3.


9-1Configuring the Operation System

Chapter 9. Configuring the Operating System

This chapter provides information concerning the tasks you might need to perform afterinstalling the base operating system (BOS). Complete all configuration tasks that apply toyour newly installed system. Two configuration tools are available to assist you. Dependingon which type of console you are using, one of the following usually begins automaticallyafter installation:

• Configuration Assistant on page 9-1 for graphics consoles

• Installation Assistant on page 9-2 for ASCII consoles

Notes:

– If your system was installed by a network installation server, the ConfigurationAssistant or Installation Assistant does not display when the BOS installation programcompletes.

If your system was installed using a system backup image, or if your BOS installationwas customized, or if you selected migration installation from AIX 4.2 or later, theConfiguration Assistant or Installation Assistant might not display when the BOSinstallation program completes.

– The Configuration Assistant and the Installation Assistant do not contain the tasksneeded to configure your machine as a server. If you need to configure your systemfor a specific resource, refer to the documentation pertaining to that resource.

– If your terminal type is not set, the first menu displayed by the ASCII InstallationAssistant requires you to enter your terminal type (tty). If you enter a terminal typethat is not valid, this menu redisplays until a valid type is entered.

If you enter a valid terminal type that does not match your terminal, the next screendisplayed might be unreadable. In this case, press the break key sequence to returnto the Set Terminal Type screen. For most terminal types, the break key sequence isCtrl–C.

Configuration Assistant

On a system with a graphical interface, the newly installed BOS reboots and theConfiguration Assistant starts to guide you through the configuration tasks. For example,much of the processing on a system uses the date and time–of–day information, requiringthe system have the date and time set correctly.

If there are outstanding software license agreements that must be accepted before you cancontinue to use the machine, the Configuration Assistant prompts you to view and acceptthese agreements.

The Configuration Assistant guides you through the following configuration tasks:

• Set the system date and time for your time zone.

• Set a root user account password to restrict access to system resources.

• Configure network communications.


Note: To configure your machine as an NFS server, refer to NFS Installation andConfiguration in the AIX 5L Version 5.2 System Management Guide: Communicationsand Networks.

• Configure Web-based System Manager to run in a Web browser (applet mode).

• Manage Software.

• Exit the Configuration Assistant.

The Manage Software option allows you to perform software management tasksimmediately after a BOS installation. The following options are available:

• List installed software

• Install additional software

• List software licenses with license text

If you select List installed software, the following options are available:

• List automatically installed Software – Displays a list of all installed packages

• List optionally installed software – Displays a list of all optional software that wasselected to be installed during BOS installation

If you select Install additional software, the following options are available:

• Install by bundles – Allows you to select from a list of software bundles to installadditional software, such as the Netscape Communicator Software Bundle or aUser–Defined Software Bundle

• Selective install – Allows you to select a specific package or set of packages to install

The graphical interface for the Configuration Assistant provides step–by–step instructionsfor completing each configuration task. The tasks are presented to you in a logicalsequence. Complete all configuration tasks before you use your system.

When you exit the Configuration Assistant, the guide asks you whether you want to startConfiguration Assistant again the next time you restart the operating system. After exitingthe Configuration Assistant, users can begin logging in to and using AIX.

To access the Configuration Assistant later, type configassist on the command line.

Installation AssistantOn a system with an ASCII interface, the newly installed BOS reboots and starts theInstallation Assistant to guide you through completing configuration tasks. You must haveroot user authority to use the Installation Assistant. To access the Installation Assistant later,type install_assist on the command line. You can also access it from a graphicssystem through the SMIT smit assist fast path.

If there are outstanding software license agreements that must be accepted before you cancontinue to use the machine, the Installation Assistant prompts you to view and acceptthese agreements.

The Installation Assistant guides you through the following configuration tasks:

• Set the system date and time for your time zone.

• Set a root user account password to restrict access to system resources.

• Configure network communications.

• Install software applications.

• Using SMIT (information only).

• Tasks Completed – Exit to Login.

9-3Configuring the Operation System

The Install software applications option allows you to perform software management tasksimmediately after a BOS installation. The following options are available:

• Add License Passwords for Applications

• Install and Update Software

If you select Install and Update Software, the following menu displays:

Install and Update Software

Move cursor to desired item and press Enter.

Install Software

Update Installed Software to Latest Level (Update All)


Update Software by Fix (APAR)

Install and Update from ALL Available Software

You can also access this SMIT menu by using the install_update fast path.

Related InformationFor late–breaking information, which might include information about the configurationprocess and installed software, refer to readme files. For information about viewing how toview readme files, see Viewing Readme Files.

If you are installing from CD/DVD–ROM, or would like more information about installingoptional software, refer to Installing Optional Software Products and Service Updates.


10-1Customized BOS Installations

Chapter 10. Customized BOS Installations

This chapter describes how to customize subsequent installations of the BOS after theoperating system has been installed. Customizing an installation requires you to edit thebosinst.data file and use it with your installation media.

Introduction to Customized BOS Installations

The first time you install, the Base Operating System (BOS) installation program presentsmenus from which you must choose setup options. This initial installation also automaticallystarts a post–installation configuration program, either the graphical Configuration Assistantor the ASCII Installation Assistant. For more information about Configuration Assistant andInstallation Assistant, refer to Configuring the Operating System.

For subsequent installations, you can change many aspects of the default BOS installprogram by editing the bosinst.data file. For example, to install the BOS without menus,you can specify that no prompts be provided. You can also customize a BOS installation tobypass Configuration Assistant or Installation Assistant and start your own configurationscript. Also, the bosinst.data file can be used to replicate one set of installation settings onother machines. For example, system administrators can create a bosinst.data file withsettings that can be used to install all the machines they support that have the sameconfiguration. For AIX 4.3.3 and later versions of the operating system, you can use theWeb-based System Manager Reinstall Base Operating System wizard to install systemsfrom product or backup media. This application lets you customize your installation byanswering prompts before installation and creates a bosinst.data file appropriate for thetype of installation wanted. For more information on the bosinst.data file, refer to Thebosinst.data File.

If you run your own configuration script from a bosinst.data file or from the NetworkInstallation Management (NIM) interface, the environment that is in place at the time thescript is run is a single–user environment. This environment is not available as a multiuserenvironment, and thus, there are limits to what can be run from a configuration script. The/etc/init file is not running, so no process management can take place. All available memorycannot be made available because the RAM file system still exists, so devices that requirelarge amounts of memory to run might fail to configure. In addition, signal handling is notavailable.

Because of the single–user environment, use the following guidelines for configurationscripts:

• Base devices can be configured, but devices that require daemons or more complexconfiguration should be started at reboot time by adding the necessary code to the endof the /etc/firstboot script.

• Daemons should not be started.

• Items such as NIS configuration, which uses system resource controller (SRC)commands, should be done by creating a separate entry in the /etc/inittab file andrunning a configuration script at reboot time.

• Beginning in AIX 5.2, the BOS installation process automatically creates and extendspaging space based on available memory.


The bosinst.data file directs the actions of the BOS installation program. The file resides inthe /var/adm/ras directory on the installed machine only, and it is not accessible on thecommercial tape or the CD on which you received AIX 5.2.

The bosinst.data file contains stanzas with variables set to default values. Each variable ison a new line, in the Variable = Value form. A blank line separates each stanza. Thesestanzas provide the installation program with information such as the method and type ofinstallation, the disks in the machine, and the language used. By editing the file with anASCII text editor, you can substitute new values for the default variables.

Another installation file, image.data, can also be modified and used during BOS installation.The image.data file contains information describing the root volume group image createdduring the BOS installation process. This information includes the sizes, names, maps, andmount points of logical volumes and file systems in the root volume group. The installationprogram also takes input from the image.data file regarding defaults for the machine beinginstalled. For a description of the image.data file, see AIX 5L Version 5.2 Files Reference.The procedure for using the bosinst.data file to customize BOS installation can also beused for the image.data file. The modified files can be used together to override BOSinstallation defaults.

You can also use the instructions in this chapter to create a supplemental diskette, a CD–R,or a DVD–RAM containing a modified preserve.list file, which is used during a preservationInstallation. For more information about a preservation installation, see Introduction to BaseOperating System Installation.

Customizing and Using a bosinst.data File

You must install the BOS before you can access and modify the default bosinst.data file.The Web-based System Manager Reinstall Base Operating System wizard can be usedto prepare your next installation and in customizing the bosinst.data file. This file may alsobe retrieved and edited like any other ASCII file. If you are editing the bosinst.data file, useone of the following procedures:

• Create and Use a Client File on page 10-3

• Create and Use a Supplementary Diskette on page 10-3

For information about the contents of the file and examples of edited files, refer tobosinst.data File Stanza Descriptions on page 11-2 and bosinst.data File Example on page11-11. To verify the contents of your modified bosinst.data file, use the bicheck command.

Note: If you are customizing the /bosinst.data file so that it becomes part of asystem backup (mksysb), beginning with AIX 4.3.3, the mksysb commandalways updates the target_disk_data stanzas to reflect the current disks inthe rootvg. If you do not want this update to occur, you must create the file/save_bosinst.data_file. The existence of this file is checked by themksysb command, before the target_disk_data stanzas are updated.

10-3Customized BOS Installations

Create and Use a Client FileCreate one customized bosinst.data file for each client, and using Network InstallationManagement (NIM), define the files as NIM resources. For more information about how touse the bosinst.data file as a resource in network installations, refer to The bosinst.dataFile.

Create and Use a Supplementary DisketteUse this procedure to create the supplementary diskette and use it in future installations:

1. Customize the bosinst.data file:

a. Use the cd command to change your directory to the /var/adm/ras directory.

b. Copy the /var/adm/ras/bosinst.data file to a new name, such as bosinst.data.orig.This step preserves the original bosinst.data file.

c. Edit the bosinst.data file with an ASCII editor.

d. Create an ASCII file consisting of one word:

data

e. Save the new ASCII file, naming it signature.

2. Create the diskette and use it for installation:

a. Back up the edited bosinst.data file and the new signature file to diskette with thefollowing command:

ls ./bosinst.data ./signature | backup –iqv

OR

If you create a bundle file named mybundle, back up the edited bosinst.data file,the new signature file, and the bundle file to diskette with the following command:

ls ./bosinst.data ./signature ./mybundle | backup –iqv

b. Insert the diskette in the diskette drive of the target machine you are installing.

c. Boot the target machine from the installation media (tape, CD/DVD–ROM, ornetwork) and install the operating system.

The BOS installation program uses the diskette file, rather than the defaultbosinst.data file shipped with the installation media. For more information on thebosinst.data file, refer to The bosinst.data File on page 11-1.

Related Information• For more information about the bosinst.data file, refer to The bosinst.data File.

• For a description of the image.data file, see AIX 5L Version 5.2 Files Reference.


11-1The boinst.data File

Chapter 11. The bosinst.data File

This chapter provides information on the bosinst.data file. The chapter includes thefollowing sections:

• bosinst.data File Stanza Descriptions on page 11-2

• bosinst.data File Example on page 11-11


bosinst.data File Stanza DescriptionsThis section describes the contents of the bosinst.data file. Example files follow the stanzadescriptions. (See bosinst.data File Example on page 11-11.)

control_flow StanzaThe control_flow stanza contains variables that control the way the installation programworks:

Variable Description

CONSOLE Specifies the full path name of the device youwant to use as the console. If this value isDefault, and you are performing a nonpromptedinstallation, then the console is set to /dev/lft0, ifthis device exists. If /dev/lft0 does not exist, theconsole is set to /dev/tty0. (Instructions for whichkey to press are displayed on the screen.) If youchange the PROMPT variable to no, you mustspecify a console here.

INSTALL_METHOD Specifies a method of installation: migrate,preserve, or new and complete overwrite. Thedefault value is initially blank. The installationprogram assigns a value, depending on whichversion of AIX was previously installed. SeeIntroduction to Base Operating SystemInstallation for more information.

The default method of installation is migrate if aprevious version of the operating system is onthe machine. If no previous version exists, thedefault method is new and complete overwrite.

PROMPT Specifies whether the installation program usesmenus from which you make choices. Thepossible values are yes (default) and no.

Note:You must fill in values for all variables in thelocale stanza to uniquely identify the disk, ifyou set the PROMPT variable to no.Similarly, if PROMPT equals no, you mustsupply values for variables in thecontrol_flow stanza, with two exceptions: theERROR_EXIT and CUSTOMIZATION_FILEvariables, which are optional.

Attention: Fill in values for enough variables in thetarget_disk_data stanza if you set thePROMPT variable to no. The BOSinstallation program assigns target disks forblank variables. You can lose data if theinstallation program assigns a disk whereyou store data. For more information on diskselection during nonprompted installations,see ***.


EXISTING_SYSTEM_OVERWRITE Confirms that the installation program canoverwrite existing volume groups. This variable isapplicable only for a nonprompted overwriteinstallation. The possible values are no (default),yes, and any.

no(Default) Only disks that are not part of avolume group can be used for the installation.

yesDisks that contain the root volume group isused first, and if additional disks are needed forthe installation, then disks that contain novolume groups are used.

anyAny disks can be used for the installation.

When the installation is nonprompted and thetarget_disk_data stanza is empty, the installationprocess uses the value of theEXISTING_SYSTEM_OVERWRITE field todetermine the disks to install on.

When you do a prompted installation, this valueis changed to yes, and is saved with otherchanges in the /var/adm/ras/bosinst.data file.Network Install Manager (NIM) creates a defaultbosinst.data file (NIM bosinst_data resource)with this value set to yes, and system backupsuse the bosinst.data file that is copied from the/var/adm/ras directory, so in most cases thisvalue is already be set to yes. If this field is setto no, as seen in the/usr/lpp/bosinst/bosinst.template file, an errormessage informs you that there are not enoughdisks matching the criteria needed to completethe installation during a nonprompted install. TheBOS installation is then changed to a promptedBOS installation, and the value of theEXISTING_SYSTEM_OVERWRITE field is set toyes.

RUN_STARTUP Starts the Configuration Assistant on first bootafter the BOS installation completes, if thesystem has a graphical interface. StartsInstallation Assistant if the machine has an ASCIIinterface. The possible values are yes (default)and no. The no value is valid only when theACCEPT_LICENSES field is set to yes.

RM_INST_ROOTS Removes all files and directories in the/usr/lpp/*/inst_roots directories. The possiblevalues are no (default) and yes.

The /usr/lpp/bos/inst_roots directories mustremain if the machine is used as a networkserver. To save disk space, set this value to yesif the machine is not a network server.


ERROR_EXIT Starts an executable program if an error occursin the installation program. The default value isblank, which signals BOS installation to use acommand that is shipped on the installationmedia. The command starts an error messageroutine when the installation program haltsbecause of an error. As an alternative to thedefault, you can enter the path name of your ownscript or command for a customized error routine.

CUSTOMIZATION_FILE Specifies the path name of a customization fileyou create. The default value is blank. Thecustomization file is a script that startsimmediately after the installation programconcludes.

TCB Specifies whether you want to install the TrustedComputing Base (TCB). When you install theTCB, the trusted path, the trusted shell, andsystem integrity checking are installed. The TCBmust be installed and initialized when theoperating system is installed. The TCB cannot beinstalled later. By not installing the TCB,installation time is reduced. The possible valuesare no (default) and yes.

BUNDLES Specifies what software bundles to install. Typethe full path name of each bundle file. Be surethere is sufficient disk space and paging spaceon the target machine for the software youspecify in the BUNDLES variable.

This list of bundle file names is limited to 139bytes. If your list of bundle file names is longerthan 139 bytes, use the cat command tocombine the bundle files into a single custombundle file and enter the name of your custombundle file in this field.

If you are installing from tape, to specifysystem–defined bundles on the product media,use the full path name of each bundle file asfollows:

/usr/sys/inst.data/sys_bundles/BundleFil

eName

If you are using a bosinst.data diskette to defineyour own bundle files, specify the full path nameof each bundle file as follows: /../DirectoryName / BundleFileName. Forexample, if you put a bundle file namedmybundle in the root directory, the full pathname would be /../mybundle.

If you are using preservation installation, createbundle files before you start the installation.Create the files in /home and specify the full pathname of each bundle file as follows:

/home/BundleFileName


RECOVER_DEVICES Specifies whether to reconfigure the devices. Thedefault value is Default. For mksysbinstallations, the ODM configuration database issaved in the image. The device names andattributes are automatically extracted from thedatabase, and the BOS installation programattempts to recreate the devices the same waythey were on the machine the mksysb wascreated on. This is normal procedure for regularmksysb restores on the same system. However,for cloning (installing the mksysb image onanother system), you may not want thesedevices configured this way, especially fornetwork configuration.

When the mksysb image is created, the CPU IDis saved. If you are reinstalling the same system,then the device information is recovered. If themksysb image is used to install another system,device information is not recovered from themksysb image.

The Default value can be overwritten. Forexample, if your system had the planar replaced,or you upgraded to another system, you mightwant to recover devices. In these cases, you canselect yes in the Backup Restore menu torecover devices.

BOSINST_DEBUG Specifies whether to show debug output duringBOS installation. The value yes sends set –xdebug output to the screen during BOSinstallation. The possible values are no (default)and yes.

ACCEPT_LICENSES Specifies whether to accept software licenseagreements during the BOS installation. Thedefault is no. To automatically accept them, setthis value to yes. When the software licensesagreements are not accepted during BOSinstallation, Configuration Assistant or InstallationAssistant prompts you to view and accept them.During a BOS installation, if this value is blank,the default of no is assumed.

For mksysb installations, when theACCEPT_LICENSES field is no, the user isforced to accept the licenses again beforecontinuing to use the system. When theACCEPT_LICENSES field is set to yes, thelicenses are automatically accepted for the user.If blank, the state of the licenses is the same aswhen the mksysb was created.

DESKTOP Specifies the desktop to be installed. The choiceof available desktops are CDE (the default),NONE, GNOME, and KDE. If you chooseGNOME or KDE, you will be prompted for theAIX Toolbox for Linux Applications CD.


INSTALL_DEVICES_AND_UPDATES When installing a mksysb image to a systemwith a different hardware configuration, boot fromproduct media to get any missing device driversinstalled. In addition, if the product media is alater level of AIX than the mksysb, software inthe mksysb image will be updated. To preventeither of these additional installations fromoccuring, set this field to no. The default is yes.

IMPORT_USER_VGS Specifies whether you want any user volumegroups to be automatically imported after thesystem has been installed. The choices are yesand no.

ENABLE_64BIT_KERNEL Specifies whether you want to enable the 64–bitkernel. The choices are yes and no.

CREATE_JFS2_FS Specifies whether you want to create enhancedjournaled file systems. The choices are yes andno.

ALL_DEVICES_KERNELS Specifies whether to install all device and kernelfilesets. The choices are yes and no. If youselect no, your system will be installed with thedevices and kernel specific to your systemconfiguration. If you select yes, when you createa system backup of your system, you can usethat system backup to install any system.

GRAPHICS_BUNDLE Specifies whether to install the graphics softwarebundle during the BOS installation. This softwarebundle contains the graphics support for theWeb-based System Manager and Linuxdesktops. The choices are yes and no.

NETSCAPE_BUNDLE Specifies whether to install the NetscapeCommunicator software bundle during the BOSinstallation. This software bundle contains theNetscape Communicator software. The choicesare yes and no.

HTTP_SERVER_BUNDLE Specifies whether to install the HTTP Web serversoftware bundle during the BOS installation. Thissoftware bundle installs the HTTP Web serversoftware. The choices are yes and no.

KERBEROS_5_BUNDLE Specifies whether to install the Kerberos 5 clientsoftware bundle during the BOS installation. Thissoftware bundle installs the Kerberos 5 clientsoftware. The choices are yes and no.

SERVER_BUNDLE Specifies whether to install the AIX serversoftware bundle during the BOS installation. Thissoftware bundle installs additional networkingsoftware, performance tools, and accountingservices software. The choices are yes and no.

ALT_DISK_INSTALL_BUNDLE Specifies whether to install the alternate diskinstallation software during the BOS installation.The choices are yes and no.

REMOVE_JAVA_118 Specifies whether to remove the Java 1.1.8software from the current system whenperforming a migration installation. The choicesare yes and no.


target_disk_data StanzaThe target_disk_data stanza contains variables for disks in the machine where the programis to install BOS. The default bosinst.data file has one target_disk_data stanza, but youcan 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 theroot volume group. Only one field (PVID, PHYSICAL_LOCATION, SAN_DISKID,CONNECTION, LOCATION, SIZE_MB, HDISKNAME) must be non–null for BOSinstallation to choose a disk. The order of precedence is PVID (Physical Volume ID),PHYSICAL_LOCATION, SAN_DISKID, then CONNECTION (parent attribute//connwhereattribute), then LOCATION, then SIZE_MB, and then HDISKNAME. The BOS installationprocess uses the following logic to determine how to use the target_disk_data stanzainformation:

• If PVID is set, BOS installation checks to see if a disk matches the value. If so, otherattributes are ignored.

• If PVID is empty and CONNECTION is set, then BOS installation checks to see if theparent and connwhere attributes (separated by ”//”) match a disk. If they do, otherattributes are ignored.

• If either PVID or CONNECTION is set, and neither value matches a disk on the targetsystem, and no other attributes are set, an error message is generated, and a disk mustbe explicitly selected.

• If PVID is empty and SAN_DISKID is set, then, for fibre channel–attached disks, BOSinstallation interprets the SAN_DISKID as a World Wide Port Name and a Logical UnitID (separated by ”//”). The World Wide Port Name (ww_name) and Logical Unit ID(lun_id) can be obtained on a running system from the lsattr command.

The SAN_DISKID field is checked before the CONNECTION field.

• If the ww_name and lun_id match a disk, other attributes are ignored.

• If either PVID or SAN_DISKID is set, and neither value matches a disk on the targetsystem, and no other attributes are set, an error message is generated and a disk mustbe explicitly selected.

• If PVID and SAN_DISKID are empty and CONNECTION is set, BOS installation verifiesif the parent and connwhere attributes (separated by ”//”) match a disk. If this is true,other attributes are ignored.

• If CONNECTION is set, the value does not match a disk on the target system, and noother attributes are set, an error message is generated and a disk must be explicitlyselected.

• If other attributes are specified, processing occurs as described below:

– If LOCATION is set, BOS installation ignores SIZE_MB and HDISKNAME.

– If LOCATION is not set and SIZE_MB is, BOS installation selects disks based onSIZE_MB and ignores HDISKNAME.

– If LOCATION and SIZE_MB are both empty, BOS installation chooses the diskspecified in HDISKNAME.

– If all fields are empty, BOS installation chooses a disk for you.

For the PVID, PHYSICAL_LOCATION, SAN_DISKID, and CONNECTION fields, the BOSinstallation process uses the following logic to determine how to use the target_disk_datastanza information:

• Does the information in one or more of the PVID, PHYSICAL_LOCATION,SAN_DISKID, and CONNECTION fields match the disk information?

• If the disk information matches the information in one of these four fields, use thatinformation.


• If the disk information does not match the information in one of these four fields, and ifthe LOCATION, SIZE_MB, and HDISKNAME fields are not set, display an errormessage and prompt the user for the correct disk information.

The PHYSICAL_LOCATION information can be retrieved using the lsdev command. Forexample:

# lsdev –Cc disk –l hdisk0 –F ”name physloc”

returns the hdisk0 diskname and the P2/Z1–A8 physical location.

Attention: If prompt=no, do not leave the target_disk_data stanzas empty, unless it isunimportant which disk BOS installation overwrites. This is because the algorithm thatdetermines the default disk for the installation is not always predictable.

The SIZE_MB field can contain either a size or the word largest. If a size is listed, BOSinstallation does a ”best–fit” on the disks. If the word largest is in that field, BOSinstallation selects the largest disk. If there is more than one target_disk_data stanza, BOSinstallation selects the two ”largest” disks, and so on.

PVID Specifies the 16–digit physical volume identifier for thedisk.

PHYSICAL LOCATION The physical location code provides a way to identifyfibre channel disks during BOS Install. For fibre channeldisks the PHYSICAL_LOCATION field includes theWorld Wide Port Name and Lun ID that are included inthe SAN_DISKID field. The information in thePHYSICAL_LOCATION field supercedes the informationin the SAN_DISKID field.

SAN_DISKID Specifies the World Wide Port Name and a Logical UnitID for fibre channel–attached disks. The ww_name andlun_id are separated by two slashes ( // ). Thisinformation can be obtained on a running system fromthe lsattr command.

CONNECTION Specifies the combination of the parent attribute and theconnwhere attribute associated with a disk. The parentand connwhere values are separated by two slashes ( //). If the parent value is scsi0 and the connwherevalue is 0,1, then the CONNECTION value isscsi0//0,1. An example of the CONNECTION valuefor a SSA disk would be ssar//000629CCC07300D. Inthe example, the parent attribute is represented by ssarand the ConnectionLocation (15–character uniqueidentity) of the disk drive 000629CCC07300D is used forthe connwhere attribute.

SIZE_MB Specifies the formatted size of the disk, in megabytes,where the program is to install BOS. The default value isblank. You can specify the size of your target disk bytyping the number of megabytes available on theformatted disk. Also, you can type largest if you wantto use the largest disk (that has not already beenselected) found by the installation program.


LOCATION Specifies a location code for the disk where the programis to install BOS. The default value is blank. If you do notspecify a value, the installation program assigns a valuebased on the next two variables. For more informationabout physical location codes, refer to the DiagnosticInformation for Multiple Bus Systems guide.

HDISKNAME Specifies the path name of the target disk. The defaultvalue is blank. To name a target disk, use the hdisknameformat, where hdiskname is the device name of your disk(for example, hdisk0).

locale StanzaThe locale stanza contains variables for the primary language the installed machine is touse. Refer to Understanding Locale Categories in AIX 5L Version 5.2 National LanguageSupport Guide and Reference, which provides information about locales and the format touse when editing variables.

BOSINST_LANG Specifies the language that the installation program usesfor prompts, menus, and error messages. The defaultvalue is blank.

CULTURAL_CONVENTION Specifies the primary locale to install. The default value isblank.

MESSAGES Specifies the locale for message catalogs to install. Thedefault value is blank.

KEYBOARD Specifies the keyboard map to install. The default valueis blank.

large_dumplv StanzaThe optional large_dumplv stanza specifies characteristics used if a dedicated dumpdevice is to be created on the systems. A dedicated dump device is only created forsystems with 4 GB or more of memory. The following characteristics are available for adedicated large dump device:

DUMPDEVICE Specifies the name of the dedicated dump device.

SIZEGB Specifies the size of the dedicated dump device ingigabytes.

If the stanza is not present, the dedicated dump device is created when required. Adedicated dump device is created in machines with at least 4 Gigabytes of real memoryduring an overwrite install. By default, the name of the dedicated dump device is lg_dumplvand its size is determined by the following formula:




RAM >= 48 size of dump device= 4 GB


dump StanzaThe dump stanza specifies the following system dump characteristics:

PRIMARY Specifies the primary dump device to be set bysysdumpdev –P –p device.

SECONDARY Specifies the secondary dump device to be set bysysdumpdev –P –s device.

COPYDIR Specifies the directory to which the dump is copied atsystem boot.

FORCECOPY Specifies whether the system boots into menus that allowcopy of the dump to external media if the copy fails.

ALWAYS_ALLOW Specifies whether the key mode switch can be ignoredwhen a dump is requested.

If the stanza is not present in the bosinst.data file, no additional dump–device handlingoccurs beyond what is already in place. Checking on the values of the fields is limited; if thedevice specified for a dump device is not valid, any error processing comes from thesysdumpdev command and is sent to the console and stored in the BOS installation log.

• If FORCECOPY is specified and no COPYDIR is specified, the value field of theautocopydump attribute from /etc/objrepos/SWservAt is retrieved and used for thesysdumpdev –[d|D] copydir operation.

• If only the COPYDIR is specified without FORCECOPY being specified, forcecopydefaults to yes. The sysdumpdev –d ( FORCECOPY = no) or sysdumpdev –D (FORCECOPY = yes) is used to set the copy directory.

• If ALWAYS_ALLOW=yes, run sysdumpdev –K. Otherwise, run sysdumpdev –k.

• If any values other than yes and no are specified for FORCECOPY orALWAYS_ALLOW, the default actions occur, and processing continues.

• If no value is specified for a particular dump field, no analogous sysdumpdev operationis performed. This leaves the system values in the appropriate state, even for amigration or system backup image installation. If a COPYDIR is specified butFORCECOPY is not specified, the value of the forcecopydump attribute is retrievedfrom the /etc/objrepos/SWservAt file to determine the correct form of sysdumpdev toinvoke.


bosinst.data File Example

The following example bosinst.data file shows you how customize a nonprompted networkinstallation. The values in the bosinst.data file for this example are not specific to a networkinstallation and can be applied for other types of installations, such as a mksysbinstallation.

Note: The depicted values illustrate formatting only and do not apply to your installation.

For information about a bosinst.data variable or values, see bosinst.data File StanzaDescriptions on page 11-2.

To check the contents of your customized bosinst.data file, use the bicheck command, asfollows:

/usr/lpp/bosinst/bicheck filename

Nonprompted Network Installation

The following is an example of a modified bosinst.data file that might be used in anonprompted network installation:

control_flow:

CONSOLE = Default

INSTALL_METHOD = overwrite

PROMPT = no

EXISTING_SYSTEM_OVERWRITE = yes

RUN_STARTUP = no

RM_INST_ROOTS = yes

ERROR_EXIT =

CUSTOMIZATION_FILE =

TCB = no

BUNDLES =

RECOVER_DEVICES = Default

BOSINST_DEBUG = no

ACCEPT_LICENSES = yes

INSTALL_CONFIGURATION =

DESKTOP = CDE

INSTALL_DEVICES_AND_UPDATES = yes

IMPORT_USER_VGS = yes

ENABLE_64BIT_KERNEL = yes

CREATE_JFS2_FS = yes


GRAPHICS_BUNDLE = no

DOC_SERVICES_BUNDLE = no

NETSCAPE_BUNDLE = yes

HTTP_SERVER_BUNDLE = yes

KERBEROS_5_BUNDLE = yes

SERVER_BUNDLE = yes

ALT_DISK_INSTALL_BUNDLE = yes

REMOVE_JAVA_118 = no

target_disk_data:

PVID =

CONNECTION =

LOCATION =

SIZE_MB =

HDISKNAME = hdisk0

locale:

BOSINST_LANG = en_US

CULTURAL_CONVENTION = en_US

MESSAGES = en_US

KEYBOARD = en_US


12-1Optional Software Products and Service Updates

Chapter 12. Optional Software Products and ServiceUpdates

After the Base Operating System (BOS) is installed, you might want to install optionalsoftware or service updates. This chapter includes information on the following topics:

• Optionally Installed Software on page 12-1

• Software Product Identification on page 12-2

• Software Licensing on page 12-2

• Installing Optional Software Products and Service Updates on page 12-3

• Maintaining Optional Software Products and Service Updates on page 12-7

• Cleaning Up Optional Software Products and Service Updates on page 12-10

• Software Service Management on page 12-11

• InstallShield MultiPlatform Packaged Installations on page 12-14

• Emergency Fix Management on page 12-19

Note: AIX 5.2 provides the cdromd CD and DVD automount facility, which isincluded in the bos.cdmount fileset. To determine if the cdromd daemon isenabled on your system, run the following command:

# lssrc –s cdromd

The cdromd daemon can interfere with scripts, applications, or instructions thatattempt to mount the CD or DVD device without first checking to see if the device isalready enabled. A resource or device busy error occurs in such a condition. Use the cdumount or cdeject command to unmount the device. Then mount the device asspecified in the program or instructions. Alternatively, use the cdcheck –m or mount command to determine the current mount point of the device. For furtherinformation, see the cdromd command documentation in the AIX 5L Version 5.2Commands Reference.

The installation code allows for this automatic mounting. If cdromd is enabled andthe mkcd command is run, the CD–R or DVD–RAM is ejected after the image iscompleted. If you do not want to have the media ejected, then the cdromd daemonmust be put in the inoperative state with the following command:

# stopsrc –s cdromd

Optionally Installed SoftwareOptionally installable software includes:

• Optional Software Products: Software that is not automatically installed on yoursystem when you install the BOS. Software products include those shipped with theoperating system and those purchased separately. The BOS is divided into subsystemsthat can be individually updated, such as bos.rte.install. Any update that begins withbos.rte updates a BOS subsystem.

• Service Updates: Software that corrects a defect in the BOS or in an optional softwareproduct. Service updates are organized by filesets. This type of update always changespart of a fileset.


Software products can be divided into the following categories:

Licensed ProgramA licensed program (LP) is also known as a licensed program product(LPP) or a product. An LP is a complete software product including allpackages associated with that licensed program. For example, bos (thebase operating system) is a licensed program.

Package A group of separately installable units that provide a set of related functions.For example, bos.net is a package.

Fileset An individually installable option. Filesets provide a specific function. Anexample of a fileset is bos.net.nfs.client 5.1. For more information onfileset packaging, see Fileset Installation Packaging.

Fileset Update An individually installable update. Fileset updates either enhance or correcta defect in a previously installed fileset.

Bundle A collection of packages, products, or individual filesets that suit a specificpurpose, such as providing personal productivity software or software for aclient machine in a network environment. A set of bundles is provided withBOS that contain a specific set of optional software. For more informationon bundle packaging, see Bundle Packaging.

A product can be composed of several packages, which in turn can be composed ofdifferent filesets. A product might be installed in its entirety, or only certain packages orfilesets for the product might be installed. Software products are subdivided in this way,because many software products are large and have many pieces that can be usedindependently. Dividing a product into separately installable filesets allows you to install onlythose filesets you need.

You can install all the filesets included in a package or the entire product, or you can installonly selected filesets, especially if you have limited hard disk space on your system.

Software Product Identification

The product name and level number identify a software product. The format for a softwareproduct level in AIX 5.2 is as follows:

versionnumber . releasenumber . modificationlevel . fixlevel

Each field in the software product identification is defined as follows:

• The versionnumber field consists of 1 to 2 digits that identify the version number.

• The releasenumber field consists of 1 to 2 digits that identify the release number.

• The modificationlevel field consists of 1 to 4 digits that identify the modification level.

• The fixlevel field consists of 1 to 4 digits that identify the fix level.

For example, 05.01.0000.0000 is a software product level number, and05.01.0000.0032 is a software product update level. It is not necessary to include theleading zeroes in the version, release, modification level, and fix level fields of the level.Level 05.01.0000.0000 can also be written as 5.1.0.0.

Software LicensingThe types of software licensing that can be implemented in the software purchase arerun–time licensing and acceptance of software license agreements. Normally, softwarerequiring run–time licenses is only selected for installation when you have a license to usethat software. Although the Web-based System Manager and System ManagementInterface Tool (SMIT) allow you to install licensed software even if you do not own a license,


you might be prevented from using the newly installed software until you have obtained theappropriate license.

Accepting software license agreements requires that the license agreement be accepted aspart of the installation process. If software installed as part of your BOS installation requiresaccepting a software license agreement, you cannot exit the Configuration Assistant (or theInstallation Assistant for non–graphics consoles) until the license agreement has beenaccepted. You can view as well as accept the license agreement. The BOS installation canbe customized to automatically accept software licenses. For more information, refer toCustomized BOS Installations.

For optional software installation, you can preview the license agreements on theinstallation media using the smit license_on_media fast path or the installp –El command.During the installation process, you can use the menu item to accept the software license,or you can use the installp command with the –Y flag. To view accepted licenseagreements on a system, you can use the SMIT smit installed_license fast path or thelslpp –E command. To view licenses using the Web–based System Manager, type wsm tostart the application, and select Software. When a product is uninstalled, the licenseagreement acceptance is changed to the inactive state. If the product is reinstalled, you arenot be prompted to reaccept the license agreement.

After completing the prerequisites in the next section, your next step is deciding whether toinstall software with the Web-based System Manager or with SMIT. Descriptions of bothapplications are included in this chapter.

Before you install optional software and service updates, refer to the specific instructionsthat accompany your installation media. If you ever need to reinstall your system, refer tothe installation media instructions.

Note: For information about developing software products that are installed using theinstallp command, refer to Packaging Software for Installation in AIX 5L Version 5.2General Programming Concepts: Writing and Debugging Programs.

Installing Optional Software Products and Service UpdatesIf either of the following conditions apply to you, go to the referenced section. Otherwise,continue with the procedures in this chapter.

• If you need to commit updates or remove previously installed software, go to MaintainingOptional Software Products and Service Updates on page 12-7.

• If you are using a network installation server, refer to Network Installation on page 18-1.

Step 1. Complete the Prerequisites

Before installing optional software or service updates, complete the following prerequisites:

• You must be logged in to the system as the root user.

• AIX 5.2 BOS must be installed on your system. If the BOS is not yet installed on yoursystem, go to Introduction to Base Operating System Installation, or if you are installingover a network, refer to Network Installation.

• Either insert the media that contains the optional software or service updates into theappropriate drive or know the local or routed path to the software.

• If you are installing service updates and do not have a current backup of your system,use the procedures in Creating System Backups. To create a system backup, you musthave the backup fileset (bos.sysmgt.sysbr) installed on your system.

• If system files have been modified, back them up separately before updates are applied,because the update process might replace configuration files.


• If you are installing from CD–ROM or DVD–ROM and currently have a mounteddocumentation CD in the same CD/DVD–ROM drive that you want to install from, youmust perform the operations described in the “Usage” page of the Bull Hypertext LibraryCD–ROM drive usage section.

• To eject the documentation CD/DVD–ROM, press the eject button on the CD/DVD–ROMdrive for at least two seconds.

Step 2. Install Optional Software Products or Service UpdatesOptional software products and service updates can be installed using system managementtools provided with the operating system. The following sections provide a brief descriptionof the procedures:

• Web–based System Manager. See Install Optional Software Products or ServiceUpdates with Web-based System Manager on page 12-4.

• System Management Interface Tool (SMIT). See Install Optional Software and ServiceUpdates Using SMIT on page 12-5.

To view the files as they are being installed, do the following:

• In SMIT, you can set the DETAILED Output field to yes to list the files being restoredduring an installation.

• In Web–based System Manager, expand the Software container and select InstalledSoftware. From the Software menu, select New Software (Install/Update) ––> InstallAdditional Software ––> Advanced Method. In the resulting screen, select the sourcedrive and click on Advanced. In the resulting dialog, click beside Show detailedmessages.

• You can also use the installp command with the verbose option (–V2) to show whichfiles have been updated.

Install Optional Software Products or Service Updates with Web-based SystemManager

The graphics interface provides access to Web-based System Manager options for installingthe following:

• Optional software. See Installing Optional Software.

• Service updates. See Installing Service Updates.

• Software bundles. See Installing Software Bundles.

The Web-based System Manager allows you to install software, as well as to change thesystem’s default install settings and specify other options. By default, the Web-basedSystem Manager applies and commits any software updates you are installing. However,you can change this default setting and have the software updates applied only.

Note: Base software applications are always committed. If a previous version of thesoftware is installed, it cannot be saved.

Installing Optional Software

1. Start the Web-based System Manager by typing wsm on the command line.

2. Expand the machine name.

3. Expand Software in the Navigation area.

4. Select Overview and Tasks.

5. Select Install Software.


Installing Service Updates





5. Select Update Software to the Latest Level.

Installing Software Bundles




4. Select Installed Software.

5. From the Software menu, select New Software (Install/Update) ––> Install Bundles(Easy).

Install Optional Software and Service Updates Using SMIT

The following installation paths are available in SMIT:

Install Software Install or update software from the latest levels of software available on themedia. To shorten the list of software displayed, message and localesoftware are omitted from the list. To use this option, type smitinstall_latest on the command line.

Update Installed Software to Latest LevelUpdate all currently installed software to the latest level available on theinstallation media. To use this option, type smit update_all on the commandline.

Beginning in AIX 5L Version 5.2 with the 5200–01 RecommendedMaintenance package, if you select the option to install all devices andkernels during a BOS installation, then during subsequent update_allprocessing, any new devices.* filesets are installed from the installationmedia. This option can be turned off by setting theALL_DEVICES_KERNELS variable in the /var/adm/ras/bosinst.data file tono.

Install Software BundleInstall complete bundles of software simply by specifying the input deviceand which bundle you are installing. You can also preview a bundleinstallation to see what software will be installed and how much space isrequired in the file system to install the bundle. To use this option, typesmit install_bundle on the command line.

Update Software by FixInstall a specific fix for a problem. This menu allows you to list all servicefixes on the media and select a fix to install. You can also preview theinstallation to see what software will be updated and how much space isrequired in the file system to apply the fix. To use this option, type smitupdate_by_fix on the command line.

Install and Update from ALL Available SoftwareInstall or update software from all software available on the media. To usethis option, type smit install_all on the command line.

Note: If a problem occurs during the installation of optional software that causes theinstallation process to halt abnormally, you might have to complete a cleanup procedure


to remove the partially installed software from the system before attempting to reinstall it.If the system instructs you to do a cleanup, go to Cleaning Up Optional SoftwareProducts and Service Updates on page 12-10.

Completing the SMIT Installation and Reading the Status Messages

This section describes the system activity and actions that you must take after theinstallation process has begun.

1. When you press Enter to start the installation, the COMMAND STATUS screen displays.As the installation proceeds, a series of messages display. The amount of time that theinstallation takes varies depending on your system and the software you are installingand updating.

Note: The system might prompt you to insert the volume of the installation media,with a message similar to the following:

Mount volume 2 on /dev/cd0.

Press the Enter key to continue.

When this message displays, insert the specified media and press Enter.

When the installation finishes, the Command: status field on the COMMAND STATUSscreen changes to OK or failed. OK indicates that the installation ran to completion,although some filesets may not have installed successfully. The failed status means thatthere was a problem with the installation. Although a preview installation always finisheswith an OK status, always check the summaries.

For information about error messages, refer to Handling System and Error Messages.

2. When the installation halts or finishes, the screen returns to the top of the list ofmessages that display during installation. You can review the message list as describedin the next step, or you can exit SMIT and review the smit.log file ( /smit.log or /home/user_id /smit.log).

3. Review the message list for error messages on software products or service updatesthat may not have been successfully installed. Use the following procedure to correct anyerrors in the installation:

a. Look at the pre– and post–installation summaries at the end of the message list tosee whether any installation failure occurred.

b. Use the message list to determine problems and which software products or serviceupdates were involved. For example, space limits might have been exceeded or therequisites might not have been met for some software. The system lists how muchextra space is needed and which requisite software products or service updates toinstall.

c. Any product that is marked as FAILED, BROKEN, or CANCELLED can be reinstalledafter the condition that caused the failure has been corrected. You do not need toreinstall any service update or software product that was marked as SUCCESS in theInstallp Summary report. If you need to perform the installation again, changeinstallation settings as appropriate. For example, if requisites were missing, setAUTOMATICALLY install requisite software? to yes. If there was not enough space tocomplete the installation, set EXTEND file systems if space needed? to yes.

If you need to install again and you have AIX BOS multivolume media, insert volume1 of the AIX product CDs. Press F3 to return to the previous screen, then restart theinstallation. See Handling System and Error Messages for information about bosbootcommand errors that may occur while the installation program is running, and aboutrecovery procedures for these errors.

d. If the installation was interrupted (for example, a power failure), you might need touse the cleanup procedure before continuing. Press F10 (or Esc+0) to exit SMIT, andrefer to Cleaning Up Optional Software Products and Service Updates.


e. If the software has been installed successfully, and you have no other software toinstall, go to Step 4.

If you have additional software to install from a different installation media, removethe media that is in that drive and insert the new media.

Press F3 (or Esc+3) to return to the previous screen and continue installing thesoftware product or service update.

4. Press F10 (or Esc+0) to exit SMIT.

5. Remove all installation media from the drives.

6. When you are directed, reboot your system by typing:

# shutdown –Fr

Update Installed Software to Latest Level from the Command LineThe install_all_updates command updates installed system software to the latest level thatis on the media and verifies the current recommended maintenance level.

Beginning in AIX 5L Version 5.2 with the 5200–01 Recommended Maintenance package, ifyou select the option to install all devices and kernels during a BOS installation, then duringsubsequent update_all processing, any new devices.* filesets are installed from theinstallation media. This option can be turned off by setting the ALL_DEVICES_KERNELSvariable in the /var/adm/ras/bosinst.data file to no.

If the ALL_DEVICES_KERNELS variable is set to no, the install_all_updates commanddoes not install any filesets that are present on the installation media but not installed on thesystem, unless these filesets are installed as requisites of other selected filesets.

For installp images, all installp requisites are enforced.

The following example shows how to install all installp updates on the /dev/cd0 device andto verify the current recommended maintenance level:

# install_all_updates –d /dev/cd0

For more information about the install_all_updates command, refer to the AIX 5L Version5.2 Commands Reference.

Maintaining Optional Software Products and Service Updates

During and after installation, the following major maintenance actions can be taken withoptional software products and service updates. Optional software and service updates canbe:

• Applied. See Apply Action (Service Updates Only).

• Committed. See Commit Action (Service Updates Only).

• Rejected. See Reject Action (Service Updates Only).

• Removed. See Remove Action (Software Products Only).

Whether a particular action can be taken depends on whether the action is being applied tothe entire software product, or only to a service update that has had a previous action takenon it.

You can perform these actions using either the Web-based System Manager or the SystemManagement Interface Tool (SMIT) or by using commands directly from the command line.The following sections briefly describe how to do each action using Web–based SystemManager, SMIT, or a command. Both Web-based System Manager and SMIT provide onlinehelp to guide you through each process.


Apply Action (Service Updates Only)

When installing a service update, it can be left in the applied state. In this state, the formerversion of that software product is saved in the /usr/lpp/ PackageName directory. ServiceUpdates in the applied state allow you to restore the former version of the software withouthaving to reinstall it.

Only service updates can be placed in the applied state. In contrast, after you install anentire software product, the product is left in the committed state. Software products in thecommitted state do not save the previous version of the software, because two versions ofthe same software product cannot be installed at the same time.

To apply a service update using Web–based System Manager:



3. Expand Software.


5. Select Update Software to the Latest Level.

To apply a service update using SMIT:Type smit update_by_fix on the command line.

To apply a service update from the command line:Use the installp –a command to only apply the update.

Commit Action (Service Updates Only)

Committing a service update removes the previous version of a product from the system,which conserves disk space. After a software product or update has been committed, itcannot be deleted from the system except by removing the entire software product (thebase level product and all of its updates) or by force–installing it back to a previous level. Todo a force–installation, you must have the base level of the fileset available on media.

Although applying and committing a service update are considered separate actions, bothcan be accomplished while installing the update. In fact, the default action under Web-basedSystem Manager and SMIT is to both apply and commit the service update duringinstallation. This default can be changed to just apply the update.

To commit a service update using Web–based System Manager:



3. Expand the Software container.


5. From the Software menu, choose Software Utilities –> Commit Applied Updates.

You can list all service updates in the applied state by selecting List Installed Software–> Updates in Applied State from the Software menu.

To commit a service update using SMIT:Type smit commit on the command line.

You can list all service updates in the applied state by typing smitlist_installed on the command line.

To commit a service update from the command line:Use the installp –c command to commit applied updates.


You can list all service updates in the applied state by typing installp –s on thecommand line.

Reject Action (Service Updates Only)

When you reject an applied service update, the update files are removed from the systemand the previous version of the software is restored. Only service updates in the appliedstate can be rejected. You can use the Web-based System Manager or SMIT to rejectapplied service updates.

To reject a service update using Web–based System Manager:





5. From the Software menu, choose Software Utilities ––> Reject Applied Updates.

To reject a service update using SMIT:Type smit reject on the command line.

To reject a service update from the command line:Use the installp –r command to reject an applied update.

Remove Action (Software Products Only)

When you remove a software product, that product’s files are removed from the system andthe Software Vital Product Data information is changed to indicate that the product isremoved. The remove process also attempts to restore the system’s configuration to itsprevious state, although this is dependent on the product and might not always becomplete. After a product is removed, no version of that product remains running on thesystem.

Use the Web-based System Manager or SMIT to remove software products. In eitherapplication, if you set the Remove dependent software? field to yes, any requisite software(software that is dependent on the product you are removing) is also removed, unless it isrequired by other software on your system.

To remove a software product using Web–based System Manager:





5. Select the software product you want to remove.

6. From the Selected menu, choose Remove Software.

To remove a software product using SMIT:Type smit remove on the command line.

To remove a software product from the command line:Use the geninstall –u command to remove the product.


Copy Software Bundle to Hard Disk for Future InstallationThe Copy Software Bundle to Hard Disk for Future Installation option allows you to copy asoftware bundle from a specified source to a location on your local system.

Installation software bundles include the following:

• Alt_Disk_Install

• CDE

• DocServices

• GNOME

• Graphics

• HTTP_Server

• KDE

• Kerberos_5

Cleaning Up Optional Software Products and Service UpdatesNote: This procedure applies only to the update or installation of optional softwareproducts. If your AIX 5.2 BOS installation was unsuccessful, see Accessing a SystemThat Does Not Boot for more information.

This section describes how to clean up software products and service updates after aninterrupted installation. The cleanup procedure attempts to delete items that were partiallyinstalled or left in an incomplete state. For example, after an update is interrupted, the lslpp–l command might report the update status as APPLYING rather than APPLIED.

The cleanup procedure attempts to revert the update to its previous state. For example,when cleaning up an update that was interrupted in the COMMITTING state, the cleanupprocedure attempts to return the update to its APPLIED state.

If the interruption occurs during the initial state of an installation, then the cleanup procedureattempts to delete the installation entirely and restore the previous version of the product (ifthere is one). When the previous version is restored, it becomes the active version. Whenthe previous version cannot be restored, the software is listed by the lslpp –l command asBROKEN.

When the product is deleted or BROKEN, you can attempt to reinstall the software. Anyproduct in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.

The system automatically initiates a cleanup when an installation fails or is interrupted.Normally, you must initiate a cleanup procedure if the system shuts down or loses powerduring an installation or if the installation process terminates abnormally. Occasionally, youare prompted to reboot (restart) the system after running the cleanup procedure.

To initiate a cleanup procedure using Web–based System Manager:





5. From the Software menu, choose Troubleshooting ––> Cleanup Failed orInterrupted Installation.

To initiate a cleanup procedure using SMIT:

1. Type smit maintain_software on the command line.

2. Select Clean Up After Failed or Interrupted Installation.


To initiate a cleanup procedure from the command line:Type installp –C on the command line.

If you get a message indicating that no products were found that could be cleaned up, youmay have run the cleanup procedure when it was not needed. Try your installation again.

If you get a message indicating that you need to clean up a failed installation, contact yourpoint of sale for assistance.

Manage an Existing installp Image SourceThe lppmgr command is used to manage an existing installp image source. The lppmgrcommand performs the following functions on an existing installp image source (also knownas an lpp_source resource in the NIM environment):

• Remove duplicate updates ( –u flag).

• Remove duplicate base levels ( –b flag).

• Eliminate update images that are the same level as base images of the same fileset.Such update images can create conflicts that lead to installation failure ( –u flag).

• Remove message and locale filesets other than the language you specify ( –k flag).

• Remove superseded filesets ( –x flag).

• Remove non–system images from a NIM lpp_source resource ( –X flag).

By default, lppmgr lists all images filtered by the preceding routines. The –r flag can be usedto remove the filtered images and the –m flag can be used to move the images to anotherlocation.

The lppmgr command does not replace the bffcreate command, perform installations, orwork with installed filesets. Before using the –X flag, it is recommended that you have agood understanding of NIM, system images (known as SIMAGES in NIM), and the workingsof a NIM lpp_source resource.

To list all duplicate and conflicting updates in the /myimages image source directory, type:

# lppmgr –d /myimages –u

To remove all duplicate and conflicting updates in the /myimages image source directory,type:

# lppmgr –d /myimages –u –r

For more information about the lppmgr command, refer to the AIX 5L Version 5.2Commands Reference.

Software Service ManagementThe Software Service Management menu generates comparison reports to manage filesetsinstalled on a system, filesets contained in a repository, and filesets available from theESCALA support Web site. The Software Service Management menu also provides a wayfor you to clean up and rename software images in a repository. The following options areavailable:

• Comparison Reports

• Rename Software Images in Repository

• Clean Up Software Images in Repository

You can perform these actions using either the SMIT service_software fast path or by usingcommands directly from the command line. The following sections briefly describe how todo each action using SMIT or a command.


Comparison ReportsThe Comparison Reports menu allows you to generate several comparison reports to verifythat the filesets for a particular fix or preventive maintenance package are installed bycomparing filesets installed on a system to another source. This source could be a fixrepository, such as an lpp_source or a directory of fixes, or a downloaded list from theESCALA support Web site.

If you want to verify that your lpp_source is up to date, you can also compare a fixrepository to a downloaded list.

You can perform these actions in the SMIT compare_report fast path or using thecompare_report command.

Compare Installed Software to Fix RepositoryThe Compare Installed Software to Fix Repository menu allows you to compare the filesetsinstalled on a system to a fix repository. The following report lists are generated:

• Filesets on the system that are back–level ( lowerlevel.rpt)

• Filesets on the system that are at a later level ( higherlevel.rpt)

• Filesets in the fix repository that are not installed on the system ( notinstalled.rpt)

• Filesets installed on the system that are not in the fix repository ( no_update_found.rpt)

The Compare Installed Software to Fix Repository option is available using the SMITinstofix_compare fast path or the compare_report command with the following options:

compare_report –s –i FixDir {[ –l ] [ –h ] [ –m ] [ –n ]} \

[ –t ReportDir –Z | –v ]

Compare Installed Software to List of Available UpdatesThe Compare Installed Software to List of Available Updates menu allows you to comparethe filesets installed on a system to a downloaded list of available updates from theESCALA service Web site. The following report lists are generated:

• Filesets on the system that are back–level from the latest ( lowerthanlatest1.rpt)

• Filesets on the system that are at a later level from the latest maintenance level (higherthanmaint.rpt)

• Filesets on the system that are back–level from the latest maintenance level (lowerthanmaint.rpt)

The Compare Installed Software to List of Available Updates option is available using theSMIT instolist_compare fast path or the compare_report command with the followingoptions:

compare_report –s –r ServiceReport {[ –l ] [ –h ]} [ –t ReportDir –Z

| –v ]

Compare Fix Repository to List of Available UpdatesThe Compare Fix Repository to List of Available Updates menu allows you to compare thefilesets in a fix repository, such as a fix directory or lpp_source, to a downloaded list ofavailable updates from the ESCALA service Web site. The report list that is generatedcontains information on filesets in the fix directory that are back–level from latest (lowerthanlatest2.rpt).

The Compare Fix Repository to List of Available Updates option is available using the SMITfixtolist_compare fast path or the compare_report command with the following options:

compare_report –i FixDir –r ServiceReport [ –t ReportDir –Z | –v ]


Compare a List of Installed Software on a Base System to Another SystemYou can also compare a list of installed software on a base system to another system. Thisoption allows you to compare the filesets installed on a system to another system. The lslpp–Lc output from one system is saved to a file and compared with the lslpp –Lc output fromanother system. The following report lists are generated:

• A list of base system installed software that is at a lower level ( baselower.rpt)

• Filesets not installed on the base system, but installed on the other system (otheronly.rpt)

• A list of base system installed software that is at a higher level ( basehigher.rpt)

• Filesets installed on the base system that are not installed on the other system (baseonly.rpt)

To compare a list of installed software on a base system to another system use thecompare_report command with the following options:

compare_report –b BaseList –o OtherList {[ –l ] [ –h ] [ –m ] [ –n ]} [

–t ReportDir –Z | –v ]

Rename Software Images in RepositoryThe Rename Software Images in Repository option allows you to rename updates that haveFIX ID numbers for names, to more meaningful fileset names like those generated whenupdates are copied to hard disk for future installation. This action renames all filesets in theindicated directory with the same format. This option is available using the SMITrename_software fast path.

You can also use the bffcreate command to rename software images in a directory. Torename software images in a directory using the bffcreate command, use the –c flag and the–d flag for the directory containing the filesets. For example, to rename filesets in the/usr/sys/inst.images directory, type:

# /usr/sbin/bffcreate –cd /usr/sys/inst.images

You can also create a log file containing a mapping between the old names and new names,using the –s logfile option, as shown in the following example:

# /usr/sbin/bffcreate –cd /usr/sys/inst.images –s

/usr/sys/inst.images/names.log

This example creates a /usr/sys/inst.images/names.log file that contains content formattedas follows:

old_fileset_name:new_fileset_name

This option is also available in SMIT Rename Software Images in Repository menu as theLOG software name changes (location of log file) option.

Clean Up Software Images in RepositoryThe Clean Up Software Images in Repository option allows you to remove unneeded orduplicate software images from a local software–image repository. You can removeduplicate software, superseded updates, and language software:

• The Remove Duplicate software option allows you to remove duplicate base and updateimages from the specified directory.

• The Remove Superseded updates option allows you to remove superseded filesets fromthe specified directory. This action applies only to update images.

• The Remove Language software option allows you to remove language and localefilesets that are not needed on your system. This option removes all language and localefilesets from the specified directory, except the language specified in the PRESERVElanguage field. By default, the value of the LANG environment variable for the system isused to determine the language to preserve.


• The Save Removed files option allows you to save all removed files to the locationspecified in the DIRECTORY for storing saved files field. Select true in this field if youwant to move the images to another location instead of removing them from the harddrive.

This option is available using the SMIT cleanup_software fast path.

InstallShield MultiPlatform Packaged InstallationsSome products that are distributed for installation on AIX are packaged and installed withInstallShield MultiPlatform (ISMP). Unlike installp or RPM Package Manager (RPM)installations which only provide nonprompted or silent installations of a product,ISMP–packaged products provide both interactive and silent interfaces for installing anduninstalling a product.

Similar to products packaged and installed with installp and RPM, ISMP–packaged productscan be installed using the AIX system management tools, including SMIT and Web–basedSystem Manager. These tools use the geninstall command to install or uninstall productsthat are packaged and installed with installp, RPM, or ISMP. As expected, the geninstallcommand can be used directly to install, list, or uninstall ISMP–packaged products.

For instructions for installing or uninstalling a specific product packaged and installed withISMP, consult the product’s documentation.

This section provides information about the following topics:

• Installing an InstallShield MultiPlatform Product

• Uninstalling an InstallShield MultiPlatform Product

• Silent Installations and Using Response Files

• Using Response Files with NIM

Installing an InstallShield MultiPlatform ProductYou install an InstallShield MultiPlatform product using SMIT, Web–based System Manager,the geninstall command, or the files provided by the product.

• Use the SMIT install_software fast path to install ISMP products without knowledge ofthe exact location of the product installation files. For information on installing optionalsoftware using SMIT, see Installing Optional Software Products and Service Updates onpage 12-3. Use the F4 key on the SOFTWARE to install field to select the product youwant to install. ISMP products are displayed in the list similar to installp packages orRPM packages. Select the ISMP products, and press Enter to begin the installation.

By default, ISMP product installations launched through SMIT is silent or nonpromptedinstallations. To perform an interactive installation, use the Web–based System Manager,the geninstall command, or the instructions provided with the product documentation.

Although SMIT has a preview option, this option is not available for ISMP installations. Ifyou select the preview option, a message instructs you to launch an interactiveinstallation using Web-based System Manager or the command line, which allows you toview the preinstallation summary panel before completing the product installation.

• Use the Software Application in the Web-based System Manager to launchISMP–packaged product installations. For information on installing optional softwareusing the Web–based System Manager, see Installing Optional Software Products andService Updates on page 12-3. When you press the Browse button to list products onthe media, ISMP–packaged products are displayed in the list.

Note: If you select the preview option, but proceed through the entireinstallation wizard, the product is installed. Most ISMP products includea preinstallation summary panel that provides preview information aboutthe installation, including space requirements and file system expansion.


If you do not want to proceed with the installation after viewing thisinformation, press the CANCEL button to exit the wizard.

• Use the geninstall command to install an ISMP–packaged product. To perform aninteractive installation, specify the device or directory containing the product installationfiles with the –d flag and specify the product name. The product name is the same as thesubdirectory name containing the product installation files. For example, if we have aproduct called MyProduct, and the product installation files are in the/usr/sys/inst.images/ismp/ppc/MyProduct/ directory, use the following command for aninteractive installation:

/usr/sbin/geninstall –d /usr/sys/inst.images MyProduct

OR

/usr/sbin/geninstall –d /usr/sys/inst.images J:MyProduct

Use the J: prefix to inform the geninstall command that the product is an ISMP package.The geninstall command recognizes the ismp/ppc subdirectory, just as it recognizesRPMS/ppc for RPM packages and installp/ppc for installp packages, so it is onlynecessary to pass the /usr/sys/inst.images base directory. You can also use the directorythat contains the installation files. In this example, specify the directory as follows:

/usr/sbin/geninstall –d /usr/sys/inst.images/ismp/ppc/MyProduct

J:MyProduct

If you want to launch a silent or nonprompted installation with geninstall, include the –Zflag:

/usr/sbin/geninstall –d /usr/sys/inst.images –Z J:MyProduct

For more information about silent installations, see Silent Installations and UsingResponse Files on page 12-16.

• You can use the installation files provided by the product developer to install anISMP–packaged product. The product developer might provide a script or executablethat can be used to launch an ISMP–packaged product installation. For moreinformation, refer to the documentation provided with the product.

Uninstalling an InstallShield MultiPlatform ProductYou uninstall an ISMP product using SMIT, Web–based System Manager, the geninstallcommand, or the files provided by the product’s developer.

• You can use the SMIT remove fast path to uninstall an ISMP–packaged product. If youuse the F4 key to list the installed software for the SOFTWARE to remove field, theISMP–packaged product is displayed in the list. You can also type the name of theproduct in the field.

By default, uninstallation processes performed in SMIT are silent or nonprompted. Toperform an interactive uninstallation, use Web–based System Manager, the geninstallcommand, or the instructions provided with the product documentation.

In SMIT, the preview option is not available for the ISMP product uninstallationprocedure. If you attempt to preview the uninstallation, a message instructs you tolaunch an interactive uninstallation using Web-based System Manager or the commandline. This allows you to view the pre–unstallation summary panel before completing theproduct uninstallation.

• You can use the Software Application in Web-based System Manager to uninstallISMP–packaged products.

Note: If you select the preview option, but proceed through the entireuninstallation wizard, the product is uninstalled. Most ISMP productsinclude a pre–uninstallation summary panel that provides previewinformation about the uninstallation. If you do not want to proceed withthe installation after viewing this information, press the CANCEL buttonto exit the wizard.


• You can use the geninstall command to perform an uninstallation for an ISMP–packagedproduct. To perform the uninstallation interactively, specify the –u flag for uninstallation,and the product name. For example, to uninstall the MyProduct product, type thefollowing:

/usr/sbin/geninstall –u MyProduct

OR

/usr/sbin/geninstall –u J:MyProduct

To speed processing, use the J: prefix to inform the geninstall command that you areuninstalling an ISMP–packaged product.

To perform a silent or nonprompted uninstallation with the geninstall command, use the–Z flag, as follows:

/usr/sbin/geninstall –Zu J:MyProduct

• You can use installation files provided by the product developer to uninstall anISMP–packaged product. The product developer might provide instructions forperforming an ISMP–packaged product uninstallation. For more information, see thedocumentation provided with the ISMP product.

Silent Installations and Using Response FilesThe section provides information on how to perform silent installations for ISMP–packagedproducts using response files.

A response file contains predetermined responses for an installation. By default, thegeninstall command searches on the product media in the ISMP–product subdirectory forresponse files for each ISMP product. For example, the MyProduct ISMP productsubdirectory is similar to the following:

/ basedir /ismp/ppc/MyProduct/

The geninstall command searches in the ISMP–product subdirectory for each ISMP productspecified in the install list or bundle for a *.response file. If multiple *.response files arefound, the file named Product.response is used. If a *.response file does not exist, awarning message is displayed and the installation of the ISMP product is skipped.

The –t ResponseFileLocation option allows you to specify an alternate location for responsefiles or response file templates. The ResponseFileLocation can either be a file or directoryname. If the ResponseFileLocation is a directory, it must already exist. If theResponseFileLocation is not an existing directory, it is assumed that a file name is specified.

To use response files with ISMP products, the following methods are available:

• Create a response file template. To create an ISMP response file template in the defaultlocation, use the geninstall command with the –T flag. The –T flag creates an ISMPresponse file template in the default location, which is the directory containing theproduct installation files. The resulting template can be used to create a response file forfuture installations of the same product with the desired options. Creation of theresponse file template does not result in installation of the ISMP product.

To create an ISMP response file template for the MyProduct ISMP product using theproduct installation files in the /usr/sys/inst.images/ismp/ppc/MyProduct/default directory, do the following:

/usr/sbin/geninstall –d /usr/sys/inst.images –T J:MyProduct


The MyProduct.template response file template that is generated is similar to thefollowing:

#######################################################################

#

# InstallShield Options File Template

#

# Wizard name: Setup

# Wizard source: setup.jar

# Created on: Tue Jun 25 10:59:55 CDT 2002

# Created by: InstallShield Options File Generator

#

# This file can be used to create an options file (i.e., response file) for the

# wizard ”Setup”. Options files are used with ”–options” on the command line to

# modify wizard settings.

#

# The settings that can be specified for the wizard are listed below. To use

# this template, follow these steps:

#

# 1. Enable a setting below by removing leading ’###’ characters from the

# line (search for ’###’ to find settings you can change).

#

# 2. Specify a value for a setting by replacing the characters <value>.

# Read each settings documentation for information on how to specify its

# value.

#

# 3. Save the changes to the file.

#

# 4. To use the options file with the wizard, specify –options <filename>

# as a command line argument to the wizard, where <filename> is the name

# of this options file.

#

#####################################################################

#####################################################################

#

# My Product Install Location

#

# The install location of the product. Specify a valid directory into which the

# product is installed. If the directory contains spaces, enclose it in

# double–quotes. For example, to install the product to C:\Program Files\My

# Product, use

#

# –P installLocation=”C:\Program Files\My Product”

#

### –P installLocation=<value>

Although the preceding is a simple example, products often have manyuser–configurable options that might be set in the response file. Each of these options ispresented in the template with an explanation of the expected value for that option.

• Create a response file recording. To create a response file recording, use the geninstallcommand with the –E flag. The –E flag creates an ISMP response file recording in thedefault location, which is the directory containing the product installation files. This optionrequires running the ISMP installation interactively and completely. The resultingresponse file can be used with the –R flag to select the same options on futureinstallations of the same product. Creation of the response file recording will also resultin installation of the ISMP product.

To record the MyProduct.response response file with the MyProduct ISMP productand the product installation files in the/usr/sys/inst.images/ismp/ppc/MyProduct/ default directory, do thefollowing:

/usr/sbin/geninstall –d /usr/sys/inst.images –E J:MyProduct

This starts the interactive installation wizard. It is necessary to run the wizard tocompletion to successfully create the response file recording. When completed, amessage similar to the following displays:

Options record mode enabled – run the wizard to completion to create

the options file response.file


The resulting file MyProduct.response response file is similar to the following:

################################################################

#

# InstallShield Options File

#

# Wizard name: Setup

# Wizard source: setup.jar

# Created on: Tue Jun 25 11:05:34 CDT 2002

# Created by: InstallShield Options File Generator

#

# This file contains values that were specified during a recent execution of

# Setup. It can be used to configure Setup with the options specified below when

# the wizard is run with the ”–options” command line option. Read each setting’s

# documentation for information on how to change its value.

#

# A common use of an options file is to run the wizard in silent mode. This lets

# the options file author specify wizard settings without having to run the

# wizard in graphical or console mode. To use this options file for silent mode

# execution, use the following command line arguments when running the wizard:

#

# –options ”record.txt” –silent

#

################################################################################

################################################################################

#

# My Product Install Location

#

# The install location of the product. Specify a valid directory into which the

# product is installed. If the directory contains spaces, enclose it in

# double–quotes. For example, to install the product to C:\Program Files\My

# Product, use

#

# –P installLocation=”C:\Program Files\My Product”

#

–P installLocation=”/opt/MyProduct”

The –P installLocation value has been completed according to the response given whilerunning the wizard. In the preceding example, the /opt/MyProduct directory was specifiedas the installation location in the wizard. The response file generated by this action canbe used directly to launch a silent installation with the chosen installation location.

• Use a response file for a silent installation. You can use a response file generated by thetwo methods mentioned previously or one provided with the product to perform a silentinstallation with the desired options.

To use a response file for a silent installation with the geninstall command, theMyProduct product, and the installation files and response file in the/usr/sys/inst.images/ismp/ppc/MyProduct/ default directory, do the following:

/usr/sbin/geninstall –Zd /usr/sys/inst.images –R J:MyProduct

To use a response file for a silent installation with the geninstall command, MyProductproduct, installation files in /usr/sys/inst.images/ismp/ppc/MyProduct/directory, and the /tmp/MyProduct/MyProduct.response response file, do thefollowing:

/usr/sbin/geninstall –Zd /usr/sys/inst.images –R \

–t /tmp/MyProduct/MyProduct.response J:MyProduct


Using Response Files with NIMIf you are using NIM to install an ISMP–packaged product on one or more NIM clients, youcan create and use a separate response file for each client. This is useful when there areproperties of the installation operation that must be configured differently for each client. Inorder to install multiple clients, you must name each response fileCLIENT_NAME.response. These response files must be located in the default location (thesame location as the product installer files).

For example, to install the MyProduct ISMP–packaged product located in an lpp_sourceresource in the /export/lpp_source/lpp_source1/ismp/ppc/MyProduct directory on theCLIENT1 and CLIENT2 clients, do the following:

1. Create a CLIENT1.response and CLIENT2.response response file.

2. Place the response files in the /export/lpp_source/lpp_source1/ismp/ppc/MyProductdirectory.

3. Create the correct responses for each client in the corresponding response file.

4. When you run the NIM cust operation to install the MyProduct ISMP–packaged producton CLIENT1 and CLIENT2, the response files are used automatically and appropriatelyfor each client.

If you want to use the same response file for all clients, name the response filePRODUCT_NAME.response and place in the same default location as the ISMP–packagedproduct (the product location in the lpp_source resource). For example, create a responsefile called MyProduct.response in the /export/lpp_source/lpp_source1/ismp/ppc/MyProduct/directory. If there are no client response files when you perform the NIM cust operation, theMyProduct.response file is used automatically.

Emergency Fix ManagementThe emergency fix (efix) management solution allows users to track and manage efixes ona system. You might get an efix package as an emergency fix, debug code, or test code.The efix package might contain commands, library archive files, or scripts that run when theefix is installed.

The efix management solution consists of: the efix packager (epkg) command and the efixmanager (emgr) command.

The epkg command creates efix packages that can be installed by the emgr command. Theemgr command installs, removes, lists, and verifies system efixes.

Note: In this section when the term package is used, installp ’s reference is theterm fileset.

This section includes the following information:

• Installing and Managing Emergency Fixes on page 12-29

• Additional Emergency Fix Information on page 12-25

• Packaging Emergency Fixes on page 12-29


Installing and Managing Emergency FixesThe emgr command installs, removes, lists, and verifies system efixes. The emgr commandinstalls and manages packages created with the epkg command, and maintains a databasewith efix information on the system. The emgr command performs the following operations:

• Package Installation Operation

• Removal Operation

• Listing Operation

• Checking Operation

• Mount Installation Operation

• Mounting and Unmounting Operations

• Display Package Locks Operation

• Force Removal Operation

Package Installation OperationThe emgr command installs efix packages that are created with the epkg command. Thefollowing example shows how to install an efix package:

emgr –e efix pkg | –f input file [–w dir ] [–bkpIqmFX]

The efix package installation operation consists of the following phases:

1. Installation Preview Phase on page 12-20

2. Installation Phase on page 12-20

3. Summary and Cleanup Phase on page 12-21

Installation Preview Phase

During the installation preview phase, the following steps occur:

1. The efix manager initializes all commands and libraries, and extracts the efix metadatafrom the efix package.

2. The efix attributes and description are listed.

3. The emgr command performs a lock checking procedure by checking the installed efixdata if the target files that are being delivered by this efix package already have existingefixes installed. If one or more efix files that are delivered by this efix package arelocked, the emgr command does not allow the installation or installation previewoperation to proceed.

4. The emgr command performs prerequisite verification. If the user supplied an installpprerequisite file, the emgr command checks the prerequisites at this stage. If one ormore of the prerequisites is not met, the emgr command does not allow the installationor installation preview operation to proceed.

5. The emgr command checks for space requirements by checking if the target file systemscontain adequate space for the installation of the efix package. This includes space forunpacking the efix files, creating database entries, saving replaced files, installing efixfiles, creating efix mounts when using the –m flag, archiving library members, and othermiscellaneous tasks. The emgr command also adds a small buffer to the various spacecalculations to account for file metadata and other factors.

If the user specifies the auto–expand flag using the –X flag, then the emgr commandattempts to expand the file system to the required size. If space requirements can not beultimately met, the emgr command halts the installation.

If the user specifies a preview installation operation using the –p flag, then the emgrcommand only reports the space statistics without attempting expansion. Also, if the user


specifies a a preview installation operation using the –p flag, the emgr command doesnot perform the efix installation phase and skips to the summary and cleanup phase.

Installation Phase

During the installation phase, the following steps occur:

1. During the efix installation setup step, the entire efix package is unpacked and theinstallation tools are initialized.

2. If a pre_install script is specified, it is run. If the pre_install script returns a failure, theemgr command halts the installation. If the pre_install script succeeds, the emgrcommand proceeds with the installation and sets the efix state to INSTALLING.

3. Any files that are replaced by efix files in the efix package are saved to a secureddirectory. If the efix package does not deliver any files, this step is skipped.

From this point forward, any major failure causes the emgr command to run afailure–cleanup procedure, which attempts to clean up the failed installation. If thisprocess fails, the efix is placed into the BROKEN state.

4. All efix files are installed to their target locations. If the installation is a mount installationoperation using the –m flag, then the emgr command creates a unique mount file withinthe parent directory of the target file. The target file is then over–mounted by the efixmount point. For more information about the mount installation operation, see MountInstallation Operation on page 12-24.

5. Package locking occurs. The efix package locks are then processed. If the installer forwhich the efix package is created supports efix package locking, the emgr commandlocks the package associated with the efix files installed in step 4. For example, theinstallp command supports efix locking, so an efix created for an installp package willsupport efix package locking.

6. If a post_install script is specified it is then run. If the post_install script returns a failure,the emgr command halts the installation.

7. Reboot processing occurs. If the efix package specifies that a reboot operation isrequired, the emgr command issues a message to the user and makes any necessarychanges to the boot image. The emgr command does not reboot the systemautomatically.

8. At this point, all installation steps have succeeded and the emgr command changes theefix state to STABLE for a standard installation operation, or MOUNTED for a mountinstallation operation.

Summary and Cleanup Phase

During the summary and cleanup phase, the following steps occur:

1. The emgr command displays a summary of all operations and results. If more than oneefix package was specified with an input file using the –f flag, the emgr commandprovides a report for each efix package.

2. The emgr command cleans up any temporary directories and files. It also unloads anymemory modules that have been loaded into memory.

Removal OperationThe efix removal operation removes an installed efix. You can specify an individual efix byusing one of the efix identification methods or specifying several individual efixes by using alist file. For more information about the efix identification methods, see ReferencingEmergency Fixes.

The syntax for removing an installed efix is as follows:

emgr –r –L label | –n efix num | –u VUID | –f lfile [–w dir ]

[–bkpIqX]


The efix package removal operation consists of the following phases:

1. Removal Preview Phase

2. Removal Phase

3. Summary and Cleanup Phase

Removal Preview Phase

During the removal preview phase, the following steps occur:

1. The efix manager initializes all commands and libraries, and loads efix metadata fromthe efix database.

2. Listing of efix attributes and description.

3. Space requirements are checked. The emgr command checks if the target file systemscontains adequate space to restore the saved files. This includes space changingdatabase entries, restoring saved files, archiving library members, and othermiscellaneous tasks. The emgr command also adds a small buffer to the various spacecalculations to account for file metadata and other factors.

If the user specifies the auto–expand flag using the –X flag, the emgr command attemptsto expand the file system to the required size. If space requirements can not beultimately met, the emgr command halts the remove operation. If the user specifies apreview installation operation using the –p flag, then the emgr command only reports thespace statistics without attempting expansion.

If the user specifies a preview installation using the –p flag, the emgr command does notperform the efix removal and skips to the summary and cleanup phase.

Removal Phase

Any failure in the removal phase causes the efix state to change to BROKEN. During theremoval phase, the following steps occur:

1. The emgr command initializes all remove utilities and changes the efix state toREMOVING.

2. Package unlocking occurs. All packages that are locked by the efix being removed areunlocked. Because it is possible that a single package may be locked by multiple efixes,the emgr command only unlocks a package if this efix is the last (or the only) efix stillholding a lock on the given package.

3. If a pre_remove script is specified, it is run. If the pre_remove script returns a failure, theemgr command halts the remove operation.

4. The efix is removed. If the efix was installed with a standard installation operation, theemgr command replaces the current efix files with the previously saved original files. Ifthe installation was a mount installation operation, the emgr command unmounts the efixfiles and removes them from the system.

5. If a post_remove script is specified, it is run. If the post_remove script returns a failure,the emgr command halts the installation.

6. Reboot processing occurs. If the efix package specified that a reboot is required, theemgr command issues a message to the user and make any necessary changes to theboot image. The emgr command does not reboot the system automatically.

7. At this point, all remove steps have succeeded and the emgr command removes theremaining efix data from the database and save directories.


Summary and Cleanup Phase

During the summary and cleanup phase, the following steps occur:

1. The emgr command issues a summary of all operations and results. If more than oneefix package was specified with an input file using the –f flag, the emgr command reportsfor each efix package.

2. The emgr command cleans up any temporary directories and files. It also unloads anymemory modules that have been loaded.

Listing OperationThe emgr command lists data on installed efixes with various levels of verbosity. The syntaxfor listing efixes is as follows:

emgr –l [ –L label | –n efix num | –u VUID ] [–v{1–3}X]

By default, the emgr command reports data on all installed efixes. You can specify anindividual efix by using one of the efix identification methods. For information about the efixidentification methods, refer to Referencing Emergency Fixes on page 12-25.

The default level of verbosity is 1. You can specify up to level 3 with the –v flag. Theverbosity levels include the following information:

LEVEL 1 Lists one efix per line with the following information:

. efix ID

. efix state

. Install time

. efix abstract

LEVEL 2 Lists the following information:

. All LEVEL 1 information

. VUID

. Number of efix files

. Location for each efix file

. Package for each efix file

. Installer for each efix File

. mount installation ( yes or no ) for each efix file

LEVEL 3 Lists the following information:

. All LEVEL 2 information

. Reboot requirement ( yes or no )

. Prerequisite files needed

. Pre–install script

. Post–install script

. Pre–remove script

. Post–remove script

. File type for each efix file

. File size for each efix file

. Checksum for each efix file

. Access ownership and modes for each efix file

. Prerequisite information


. efix description

. Archive member name for each efix file

. If this is a mount installation operation, then display the mount status for each efixfile

Checking OperationThe emgr command checks the status of installed efixes. The syntax for efix checking is asfollows:

emgr –c [ –L label | –n efix num | –u VUID | –f lfile ]

[ –w dir ] [–v{1–3}X]

By default the emgr command verifies all installed efixes. You can specify an individual efixby using one of the efix identification methods or specify several individual efixes by using alist file. For information about the efix identification methods, refer to ReferencingEmergency Fixes.

The default level of verification is 1. You can specify up to level 3 with the –v flag. Theverification levels include the following checks:

LEVEL 1 Checks the following information:

. efix data and state

. If this is a mount installation operation, then check the efix mount status for all files

Note: If the efix file is unmounted, the emgr command changes the efixstate to UNMOUNTED

. efix checksum for all efix files or archive members


. All LEVEL 1 checks

. efix ownership and mode for all efix files or archive members


. All LEVEL 2 checks

. All prerequisites

Mount Installation OperationIf the –m flag is specified during efix installation, the emgr command performs a mountinstallation operation of the efix package. This means that the existing files that are beingfixed are not removed from their present locations. Instead they are over–mounted by theefix files. This approach has both advantages and disadvantages. One advantage is that asystem reboot unmounts all of the efixes. This means that any efix that created a seriousproblem is not mounted after a reboot. The disadvantages are that the administrator mustmonitor the mount status of efixes and some efixes may not be removed without a reboot.

The mount installation operation is not supported with efix packages that deliver new files.

Mounting and Unmounting OperationsThe emgr command mounts or unmounts efixes that have been installed using the mountinstallation operation. The syntax for efix checking is as follows:

emgr –M | –U [ –L label | –n efix num | –u VUID | –f lfile ]

[ –w dir ] [X]

By default, the emgr command applies the mount or unmount operation to all installedefixes. You can specify an individual efix by using one of the efix identification methods orspecify several individual efixes by using a list file. For information about the efixidentification methods, refer to Referencing Emergency Fixes.


Using the mount operation with the –M flag, the emgr command attempts to mount all efixfiles that are unmounted. If all efix files are successfully mounted, and the previous efixstate was UNMOUNTED, then the emgr command changes the efix state to MOUNTED.

Using the unmount operation with the –U flag, the emgr command attempts to unmount allefix files that are mounted. If at least one efix file is successfully unmounted, and theprevious efix state was MOUNTED, then the emgr command changes the efix state toUNMOUNTED.

Display Package Locks OperationThe display package–locks operation displays all packages that are locked by efix manager,their installer, and the locking label or labels. The syntax for the display package–locksoperation is as follows:

emgr –P [ Package ] [X]

By default, the emgr command lists all locked packages. The user can specify an individualpackage as an argument to the –P flag.

Force Removal OperationThe force removal operation removes efix data. This operation also unlocks all efixpackages associated with the efix label without removing the actual efix files, executing anyremoval scripts, or boot processing. The force removal operation can only be run on oneefix at a time, and the efix label is required to identify the target efix. The syntax forperforming a force removal operation is as follows:

emgr –R efix label [–w dir ] [X]

Note: The force removal operation must be considered an as emergencyprocedure. It must only be run if all other methods to remove the efix havefailed. This method may create inconsistencies on the target system.

Additional Emergency Fix InformationAdditional information about emergency fixes includes the following topics:

• Referencing Emergency Fixes on page 12-25

• Using a List File on page 12-26

• Emergency Fix States on page 12-26

• Emergency Fix Logging on page 12-27

• Failure Cleanup on page 12-27

• Considerations for Systems Using the Trusted Computing Base on page 12-27

• Emergency Fix Manager Command Paths on page 12-27

Referencing Emergency FixesEmergency fixes can be referenced as follows:

Reference by LabelEach efix that is installed on a given system has its own unique efix label.This is called the unique key that binds all of the different database objects.To reference an efix by label, pass the label as an argument to the –L flag.For example, to run a check operation on an efix with label ABC123, typethe following:

# emgr –cL ABC123

Reference by efix IDEach efix that is installed on a given system has its own efix ID. This is theorder number in which the efix is listed in the efix database. Using thisoption may be convenient if performing operations on efixes based on efixlistings. The emgr command converts the efix ID into an efix label before


performing the given operation. To reference an efix by ID, pass the ID asan argument to the –n flag. For example, to run a check operation on thefirst efix with an ID equal to 1, type the following:

# emgr –cn1

Note: Emergency fix IDs are ephemeral and change as efixes are removedand added. Always verify the current efix ID number by listing the efixusing the –l flag.

Reference by VUIDThe VUID (Virtually Unique ID) is used to differentiate packages that havethe same label. Unlike APARs (Authorized Program Analysis Reports),which are officially tracked, emergency fixes are not tracked by anyorganization, so it is possible to have two efix packages with the samelabel. However, the emgr command does not allow the installation of morethan one efix with the same label. The emgr command converts the VUIDinto an efix label before performing the given operation. For example, to listan installed efix with VUID equal to 000775364C00020316020703, typethe following:

# emgr –l –u 000775364C00020316020703

The VUID is also displayed in the preview section of the efix installation and removaloperations, and when using the listing operation with verbosity level 2 or greater.

Using a List FileYou can perform operations on a set of efixes by specifying a list file. For the installationoperation, the list file must contain one efix package location per line. For the removaloperation and the mount and unmount operations, the list file must have one efix label nameper line. The emgr command ignores any blank lines, or lines where the first non–whitespace character is the # character.

Emergency Fix StatesThe emgr command maintains a state for each installed efix, as follows:

STABLE The efix was installed with a standard installation, and successfullycompleted the last installation operation. To verify the efix details, run acheck operation on the given efix or efixes.

MOUNTED The efix was installed with a mount installation operation, and successfullycompleted the last installation or mount operation. A state of MOUNTEDdoes not mean all efixes are currently mounted. For example, the efixesmight have been manually unmounted. This state represents the emgrcommand’s previous actions and determination of the mount status. Toverify the efix details, including mount status, run a check operation on thegiven efix or efixes.

UNMOUNTED The efix was installed with a mount installation operation and one or moreefix files were unmounted in a previous emgr command operation. Thestate of UNMOUNTED does not mean that all efixes are currentlyunmounted. For example, the efixes might have been manually mounted orpartially mounted. This state represents the emgr command’s previousactions and determination of the mount status. To verify the efix details,including mount status, run a check operation on the given efix or efixes.

BROKEN An unrecoverable error occurred during an installation or removaloperation. The status of the efix is unreliable. You can attempt to removethis efix and reinstall it from the efix package.

INSTALLING The efix is in the process of installing. Normally, this state occurs only for abrief time during efix installation. However, if an efix installation is suddenlyinterrupted (such as in a sudden power loss or a system crash), and the


emgr command is unable to clean up the failed installation, an efix might beleft in the INSTALLING state. You can attempt to remove this efix andreinstall it from the efix package.

REMOVING The efix is in the process of being removed. Normally, this state occursonly for a brief time during efix removal. However, if an efix installation issuddenly interrupted (such as in a sudden power loss or a system crash),and the emgr command is unable to clean up the failed installation, an efixmight be left in the REMOVING state. You can attempt to remove this efixand reinstall it from the efix package.

Emergency Fix LoggingThe following operations are logged to the /var/adm/ras/emgr.log emgr log file:

• Installation

• Removal

• Checking

• Mounting

• Unmounting

• Force Removal

Failure CleanupThe failure–cleanup procedure is run when an efix installation operation fails after theinstallation preview (and pre_install script, if specified). The failure–cleanup procedureattempts to reverse any of the changes that have already been made by the installationprocess. The failure–cleanup procedure is similar to the removal phase of the efix removaloperation. The failure–cleanup procedure sets the EMGR_UNDO global environmentvariable to 1. This allows packaging to take different paths in the pre_remove andpost_remove scripts.

Considerations for Systems Using the Trusted Computing BaseThe emgr command automatically detects if a system is enabled with the TrustedComputing Base (TCB). If TCB is enabled, the emgr command registers all installed efixeswith the efix database. When the efixes are removed, the emgr command restores theprevious TCB data. Because mount installation operations can create variations in fileattributes when efix files are mounted and unmounted, mount installation operations are notsupported on a TCB enabled system and are blocked by the emgr command.

If you do not want the emgr command to automatically manage TCB data, then export theEMGR_IGNORE_TCB variable and set this variable to any value that is not null. When theEMGR_IGNORE_TCB variable is set, the emgr command behaves as if the system is notTCB enabled. If the EMGR_IGNORE_TCB variable is set on a TCB enabled system, youmight be required to manually manage efix files within TCB.

To check if TCB is enabled on your system, run the /usr/bin/tcbck command. If you get ausage statement, then TCB is enabled. Otherwise, you receive a message indicating thatTCB is not enabled.

Emergency Fix Manager Command PathsThe emgr command calls one or more of the following UNIX commands:

• ar

• awk

• cat

• chmod

• chown


• compress

• cp

• date

• df

• diff

• du

• egrep

• fuser

• id

• ksh

• ln

• ls

• mkdir

• mount

• mv

• printf

• ps

• rm

• rmdir

• sed

• sleep

• sort

• sum

• tail

• tar

• tee

• touch

• umount

• uname

• vi

• wc

• zcat

The emgr command calls one or more of the following AIX commands:

• aclget

• aclput

• bosboot

• lslpp

• odmchange

• odmget


• slibclean

• tcbck

The emgr command looks for the UNIX and AIX commands mentioned in the following pathorder:

1. /usr/emgrdata/bin

2. /usr/bin

3. /usr/sbin

4. /bin

5. /sbin

6. /usr/local/bin

7. /usr/local/sbin

The /usr/emgrdata/bin directory is a secured directory that is created the first time the emgrcommand is run.

If you are attempting to install or remove an efix for one of the commands that the emgrcommand uses, you might not be able to successfully complete the operation. To solve thisproblem, do the following:

1. Manually install the efix file into the /usr/emgrdata/bin directory.

2. Perform the emgr operation.

3. Remove the manually installed efix file from the /usr/emgrdata/bin directory.

Using this method, the efix is registered and tracked with efix manager and all other emgrcommand processing takes place.

If the efix file is the /usr/bin/ksh file and the problem it fixes prevents the emgr command’soperations from succeeding, then do the following:

1. Back up the original /usr/bin/ksh file.

2. Manually install the /usr/bin/ksh efix file to /usr/bin/ksh.

3. Perform the emgr command installation or remove operation.

Packaging Emergency FixesIf you need to create your own efix and package it for distribution, use the epkg command topackage the efix. The epkg command can be run in two different modes: interactive andtemplate–based. The interactive method prompts the user with several questions andconstructs the efix package based on the answers. The template–based method uses anefix control file that is pre–filled with default answers that are then asked in interactivemode. The efix package can then be installed by the emgr command.


By using an efix control file as a template, efix packages can be created noninteractively.The following is an example of a completed efix control file:

# efix control file example

ABSTRACT=This is a test of epkg.

PRE_INSTALL=/tmp/pre_install

POST_INSTALL=.

PRE_REMOVE=/tmp/pre_remove

POST_REMOVE=.

REBOOT=yes

PREREQ=.

DESCRIPTION=/tmp/description

EFIX_FILES=2

EFIX_FILE:

EFIX_FILE_NUM=1

SHIP_FILE=/home/test/ls

TARGET_FILE=/usr/bin/ls

TYPE= 1

INSTALLER= 1

ACL= DEFAULT

AR_MEM=.

EFIX_FILE:

EFIX_FILE_NUM=2

SHIP_FILE=/home/test/mystrcat.o

TARGET_FILE=/usr/ccs/lib/libc.a

TYPE= 2

INSTALLER= 1

ACL= root:system:555

AR_MEM=strcat.o

User–Specified efix Package ComponentsThe following efix control–file components are part of the overall efix package and are notrelated to specific files:

ABSTRACT Briefly describes the efix package. The abstract is limited to 38 bytes.

PRE_INSTALL This script is run after an installation preview and before any efix files areinstalled. Failure in the pre_install script causes the efix package installationto be aborted. This script is useful for doing any preinstallation checking orwork. Because the emgr command does not call a failure–cleanupprocedure for preinstallation failures, this script performs failure cleanup(related to the script) before it exits. This component is optional.

POST_INSTALLThis script is run after all efix files have been successfully installed. A failurein the post_install script causes the installation to fail and causes efixmanager to run a failure–cleanup procedure. This component is optional.For more information about the post_install script, refer to Installing andManaging Emergency Fixes.

PRE_REMOVE This script is run after the removal preview and before any efix files areremoved during a remove operation and in the first stage of afailure–cleanup procedure. A failure in the pre_remove script causes thegiven operation to fail. In the case of a failure–cleanup procedure, the emgrcommand sets an EMGR_UNDO global environment variable to 1. Ifnecessary, the EMGR_UNDO variable is used to take different actions forremoval as opposed to a failure–cleanup. This component is optional.

POST_REMOVEThis script is run after efix files are removed during a remove operation anda failure–cleanup procedure. A failure in the post–remove script causes thegiven operation to fail. In the case of a failure–cleanup procedure, the emgrcommand sets an EMGR_UNDO global environment variable to 1. The


EMGR_UNDO variable is used to take different actions for removal asopposed to a failure–cleanup (if necessary). This component is optional.

REBOOT This variable indicates whether a reboot operation is required for this efix. Ifthis variable is set to yes, the emgr command makes any necessarychanges to the boot image and issues a message instructing the user toreboot after installation.

PREREQ This is a file that contains installp prerequisites. This component isoptional.

. The file has one prerequisite per line.

. The format of the prerequisite entry is as follows:

Fileset Min Level Max Level Type

Fileset The name of the installp fileset requisite.

Min Level The minimum level for the requisite fileset. Thespecification of NONE indicates no minimum level.

Max Level The maximum level for the requisite fileset. Thespecification of NONE indicates no maximum level.

Type The following types are supported: PREREQ andIFREQ. PREREQ is the default type and requires that therequisite fileset meets all criteria. IFREQ requires thatrequisite fileset meet all criteria only if it is installed.

. Blank lines or lines that start with # are ignored, as shown in thefollowing examples:

# Require that abc.xyz is installed at any level:

abc.xyz NONE NONE

# Require that bos.rte.lvm is installed at level 5.1.0.10 or above:

bos.rte.lvm 5.1.0.10 NONE

# Require bos.mp be between 5.1.0.0 and 5.1.0.40 if it is

installed:

bos.mp 5.1.0.0 5.1.0.40 IFREQ

DESCRIPTION This is a file that contains a detailed description of the efix package that isbeing installed.

File ComponentsThe following efix control–file components are related to specific files. The maximumnumber of efix files for each efix that the epkg and emgr commands support is 200.

EFIX_FILE_NUMThe number of the given file (1 – 200).

SHIP_FILE The local file location that the epkg command is archiving into the efixpackage. Specify either an absolute or relative path to this file. The ship fileis the efix that is delivered.

TARGET_FILE This is the target file location where the SHIP_FILE is installed. Thislocation is located on the system where the efix package is installed.Specify the absolute path to this file. If this file is part of a registeredpackage, such as an RPM or installp package, you must specify the trackedlocation.

INSTALLER This variable represents the type of installer that owns the efix package.Valid integer choices are as follows:

1 Tracked by installp

2 Tracked by RPM


3 Tracked by ISMP

4 Tracked by another installer

5 New file that will be tracked by installp

6 New file that will be tracked by RPM

7 New file that will be tracked by ISMP

8 New file that will be tracked by another installer

9 Not tracked by any installer

TYPE This is the type of file that is being installed. The valid choices are asfollows:

1 Standard file or executable file

2 Library or archive member An example of TYPE 1 is the/usr/bin/ls file or the /usr/bin/rm file. An example of TYPE 2is the shr.o archive member as a member of the libc.alibrary.

ACL Specifies the access attributes (mode and ownership) for a given file. If thisattribute is set to DEFAULT, the emgr command maintains the currentpermissions of the file to be replaced. However, if the target file is a new fileor the user wants to specify permissions using the –v flag, the ACL attributecan be entered with the syntax Owner:Group:OctalModes, similar to thefollowing:

ACL= root:system:555

AR_MEM Specifies the name of the archive member. This option is only valid ifTYPE=2. In this case, SHIP_FILE represents the local location of thearchive member that is being shipped, TARGET_FILE represents the targetarchive, and ACL applies to the archive member. For example, the followingattributes ship the myshr.o local file to the shr.o member in the/usr/ccs/lib/libc.a target archive:

TYPE=2

SHIP_FILE=/home/myshr.o

TARGET_FILE=/usr/ccs/lib/libc.a

AR_MEM=shr.o

Automatic Common ComponentsThe following components are part of the overall efix package and are not related to specificfiles. These components are automatically determined by the epkg command. Typically, theuser does not set the following components:

DATE Date and time that the backup was made.

INSTWORK Amount of space (in 512 byte–blocks) required for unpacking the efixmetadata.

VUID Virtually Unique ID. A combination of time and cpuid, this ID can be used todifferentiate fixes that are otherwise identical.

QNEXT and QORDERInternal trackers for interactive mode. If you are using an efix control file innonprompted mode, make sure QNEXT and QORDER are not set, or set toQEND.

Automatic File ComponentsThe following components are related to specific files. These components are automaticallydetermined by the epkg command. Typically, the user does not set these components.

CKSUM File checksum for the given file


SIZE Size for the given file

Interactive ModeBy default, the epkg command is run in interactive mode. The only required parameter is theefix label. If the user interrupts a running epkg session, the efix control file is saved. If theuser starts a new session with the same efix label, they are asked whether they want tokeep working with the previous efix control file, and the user can use the –u flag to answerthis question.

The epkg command maintains a record of the question order and allows the user tonavigate between questions by using subcommands. Also, the epkg command remembersthe previous answer the user provided and sets that answer as the default answer. Theepkg subcommands are the following:

b! Returns to the previous question.

s! Shows the current efix control file.

q! Quits without saving efix control file (using the Ctrl–C key sequence willprompt).

h! Displays help information for the current question.


The epkg command asks the following questions, one at a time:

1. Enter efix abstract [38 bytes maximum]:

** If ”–s” flag is specified, go to question #3 ***

2. Does this efix deliver one or more files ? (yes/no):

** If ”no”, go to question #9 **

3. Enter the local ship file location for efix file number 1:

4. Enter target location for efix file number 1:

5. Select file type for efix file number 1:

1) Standard (file or executable)

2) Library member

3) Other

6. Select the installer which tracks the file that is being fixed by efix

file number 1:

1) Currently tracked by installp.

2) Currently tracked by RPM.

3) Currently tracked by ISMP.

4) Currently tracked by another installer.

5) This is a NEW file that will be tracked by installp.

6) This is a NEW file that will be tracked by RPM.

7) This is a NEW file that will be tracked by ISMP.

8) This is a NEW file that will be tracked by another installer.

9) Not tracked by any installer.

*** If ”–m flag” and not new go to #7.1 ***

*** If new, go to #7.2 ***

*** Else, go to #8 ***

7.1 Enter the ACL for file 1 in the format of <owner>:<group>:<octal modes>.

For example to make the user=”root”, the group=”system”, and the modes ”444”,

you would enter root:system:444. Enter ”.” if you want to keep the default

(i.e. current) permissions on the existing target file.

7.2 Enter the ACL for file 1 in the format of <owner>:<group>:<octal modes>.

For example to make the user=”root”, the group=”system”, and the modes ”444”,

you would enter root:system:444.

8. Are there more efix files ? (yes/no):

** If ”yes”, increment file and go to question #3 **

** If ”no” and ”–s” flag, go to #14 **

** If ”no” go to question #9 **

9. Enter the local location for the pre–install script or ”.” to skip.

10. Enter the local location for the post–install script or ”.” to skip.

11. Enter the local location for the pre–remove script or ”.” to skip.

12. Enter the local location for the post–remove script or ”.” to skip.

14. Is a reboot required after installing this efix ? (yes/no):

15. Enter the local location for the installp prerequisite file or ”.” to skip.

*** This question is skipped if –p flag ***

16. Enter the local location for the efix description file or ”.” to compose it

in an editor:

*** This question is skipped if ”–d” flag is specified ***

*** If the description file is not specified, the user will be ***

*** put into an editor to compose it. The user can specify ***

*** which editor to use by setting the EDITOR global environment ***

*** variable. The default editor is /usr/bin/vi. ***

After all of the questions are answered, the epkg command verifies the efix control file andcreates a compressed tar package that can be installed by using the emgr command.


Related Information• For information about developing software products that are installed using the installp

command, refer to Packaging Software for Installation in AIX 5L Version 5.2 GeneralProgramming Concepts: Writing and Debugging Programs.

• For information about creating a new backup of your system, refer to Creating SystemBackups on page 14-2.

• Read the readme files that were shipped with the operating system. Any additionalsoftware you installed also might have associated readme files with late–breaking news.For information about how to view readme files, refer to Viewing Readme Files on pageiii.

• For additional release information, see the AIX 5.2 Release Notes.


13-1AIX Online Documentation

Chapter 13. AIX Online Documentation

The AIX online documentation is delivered on the following CD-ROM: – 86 X2 03EG: Hypertext Library. Full Set for AIX 5.2

Instructions for installing the Hypertext Library are contained in the CD-ROM booklet and must bescrupulously followed.

The Hypertext Library comes with a set of tools called The Hypertext Library Utilities. This set of toolscontains a Search function allowing to search for information through the entire Library and a Multi-Printcapability allowing to print several documents with a single click in the Search Results window, plus featuresallowing to create and manage notes through the entire Library and to add (or remove) user documentationto the Library.

The Hypertext Library and the Hypertext Library Utilities have both a graphical and character interface.

The contents of the Hypertext Library and the Hypertext Library Utilities are described in the HypertextLibrary home page.

More information can be found in the leaflet: ”About the Documentation CD-ROM”.


14-1Creating and Installing System Backups

Chapter 14. Creating and Installing System Backups

This chapter provides information on creating and installing system backups. The chapterincludes the following sections:

• Creating System Backups on page 14-2

• Installing System Backups on page 14-15 Notes:

1. References to CD in this chapter also apply to DVD.

2. AIX 5.2 provides the cdromd CD and DVD automount facility, which is included in thebos.cdmount fileset. To determine if the cdromd daemon is enabled on your system,run the following command:

# lssrc –s cdromd

The cdromd daemon can interfere with scripts, applications, or instructions that attemptto mount the CD or DVD device without first checking to see if the device is alreadyenabled. A resource or device busy error occurs in such a condition. Use the cdumountor cdeject command to unmount the device. Then mount the device as specified in theprogram or instructions. Alternatively, use the cdcheck –m or mount command todetermine the current mount point of the device. For further information, see the cdromd command documentation in the AIX 5L Version 5.2 Commands Reference.

The installation code allows for this automatic mounting. If cdromd is enabled and themkcd command is run, the CD–R or DVD–RAM is ejected after the image is completed.If you do not want to have the media ejected, then the cdromd daemon should be put inthe inoperative state with the following command:



Creating System Backups

This section describes how to create and verify a bootable backup copy, or mksysb image,of your root volume group and how to make separate backup copies of user volume groups.

The root volume group is a hard disk or group of disks that contains:

• Startup files

• Base Operating System (BOS)

• System configuration information

• Optional software products

A user volume group, also called the nonroot volume group, typically contains data files andapplication software.

A system backup does the following:

• Contains a working copy of your system. In the event your system data becomescorrupted, you can use this information to restore your system to working order.

• Allows you to transfer installed and configured software from one system to others. Youcan use the Web-based System Manager or SMIT to make a backup image of the rootvolume group or user volume groups.

A backup transfers the following configurations from the source system to the target system:

• rootvg volume group information

• Paging space information

• Logical volume information

• Placement of logical partitions (if creating map files has been selected in the Web-basedSystem Manager or SMIT).

Note: The use of map files is not recommended if you plan to reinstall the backup totarget systems other than the source system, or the disk configuration of the sourcesystem is to be changed before reinstalling the backup.

Using the Web-based System Manager or the SMIT backup menu lets you preserveconfiguration information, thus avoiding some of the configuring tasks normally requiredafter restoring a system backup. A backup preserves the configuration if the following aretrue:

• The target system has the same hardware configuration as the source system.

AND

• The target disk has enough space to hold the backup image.

The Web-based System Manager and SMIT both use the mksysb command to create abackup image, stored either on CD, DVD, tape, or in a file. If you choose CD, DVD, or tape,the backup program by default writes a boot image, which makes the medium suitable forinstalling. For more information, see System Backup to CD–R, DVD–R, or DVD–RAM onpage 14-6.

Install All Device and Kernel Support Before the Backup is CreatedIn AIX 5.2, all devices and kernels are installed by default when performing a baseoperating system installation. This allows you to create a system backup that contains alldevices and kernel types. Because the system backup contains all the devices and kernelsupport, the system backup can be used to install another system without the need for theAIX product media. This option is available in the Install Options menu in the BOS


installation menus.If you change the default (yes) to no, only the devices and kernel type foryour system configuration will be installed.

This value is read from the ALL_DEVICES_KERNELS field in the/var/adm/ras/bosinst.data file on the product media that you used to boot the system.

After the system is installed, you can check if all the devices and kernel types have beeninstalled on the system as follows:

# grep ALL_DEVICES_KERNELS bosinst.data



For more information about the bosinst.data file, refer to Customized BOS Installations.

Prerequisites for Creating BackupsBefore creating system backups, complete the following prerequisites:

• Be sure you are logged in as root user.

• Consider altering passwords and network addresses if you use a backup to make mastercopies of a source system. Copying passwords from the source to a target system cancreate security problems. Also, if network addresses are copied to a target system,duplicate addresses can disrupt network communications.

• Mount all file systems you want to back up. The mksysb command backs up mountedJFS (journaled file systems) and JFS2 (enhanced journaled file systems) in the rootvg.Refer to the mount command for details.

Note: The mksysb command does not back up file systems mounted across an NFSnetwork.

• Unmount any local directories that are mounted over another local directory.

This backup procedure backs up files twice if a local directory is mounted over anotherlocal directory in the same file system. For example, if you mount /tmp over /usr/tmp,the files in the /tmp directory are then backed up twice. This duplication might exceedthe number of files a file system can hold, which can cause a future installation of thebackup image to fail.

• Use the /etc/exclude.rootvg file to list files you do not want backed up.

• Make at least 8.8 MB of free disk space available in the /tmp directory. The mksysbcommand requires this working space for the duration of the backup.

Use the df command, which reports in units of 512–byte blocks, to determine the freespace in the /tmp directory. Use the chfs command to change the size of the file system,if necessary.

For example, the following command adds 12 MB of disk space to the /tmp directory of asystem with 4 MB partitions:

chfs –a size=+24000 /tmp

• All hardware must already be installed, including external devices, such as tape andCD–ROM drives.

• The bos.sysmgt.sysbr fileset in the BOS System Management Tools and Applicationssoftware package must be installed. The bos.sysmgt.sysbr fileset is automaticallyinstalled in AIX 5.2. To determine if the bos.sysmgt.sysbr fileset is installed on yoursystem, type:

lslpp –l bos.sysmgt.sysbr


If your system has the bos.sysmgt.sysbr fileset installed, continue with one of thefollowing procedures:

– Creating a Root Volume Group Backup to Tape or File on page 14-4

– System Backup to CD–R, DVD–R, or DVD–RAM on page 14-6

– User Volume Group Backup on page 14-11

If the lslpp command does not list the bos.sysmgt.sysbr fileset, install it beforecontinuing with the backup procedure. Refer to Optional Software Products and ServiceUpdates on page 12-1 for instructions, or enter the following command:

installp –agqXd device bos.sysmgt.sysbr

where device is the location of the software; for example, /dev/cd0 for CD–ROMdrive.

Creating a Root Volume Group Backup to Tape or File

You can use either the Web-based System Manager or SMIT to create a system backup tobe stored to tape or in a file.

For instructions on how to back up to CD or DVD, see System Backup to CD–R, DVD–R, orDVD–RAM.

To create a root volume group backup:

• Use the Web-based System Manager Backup and Restore application and select Backup the system.

OR

• Use the following SMIT procedure:

1. Enter the smit mksysb fast path.

2. In the Back Up the System menu, make the following selections:

. Select which medium you want to use in the Backup DEVICE or File field. If youwant to create a bootable backup, the medium must be tape or CD. See SystemBackup to CD–R, DVD–R, or DVD–RAM for more information. Then, select theappropriate option below:

TAPE Press the F4 key to list available devices and highlight the devicename.

FILE Enter a full path and file name in the entry field.

. If you want to create map files, select yes in the Create Map Files? field.

Map files match the physical partitions on a drive to its logical partitions. Wheninstalling from a backup image, the BOS installation program uses map files toposition the logical volumes on the target drive in the same partitions they were onin the source system. If you do not create map files, the installation program relieson the logical volume manager (LVM) to determine placement for the logicalvolumes. For more information, see Using Map Files for Precise Allocation in AIX5L Version 5.2 System Management Concepts: Operating System and Devices.

Note: If you plan to reinstall the backup to target systems other than the sourcesystem, or if the disk configuration of the source system might change beforereinstalling the backup, do not create map files.

. To exclude certain files from the backup, select yes in the Exclude Files field, thencreate an /etc/exclude.rootvg file with an ASCII editor, and enter the file namesthat you do not want included in your system backup image. You can use patternsfor the file names that conform to the pattern matching conventions of the grep


command. For example, to exclude all the contents of the directory calledscratch, put the following line in the exclude file:

/scratch/

For another example, exclude the contents of the directory called /tmp and avoidexcluding any other directories that have /tmp in the pathname by adding thefollowing line to the exclude file:

^./tmp/

Note: All files are backed up relative to the current working directory. Thisdirectory is represented by a. (dot character). To exclude any file or directory forwhich it is important to have the search match the string at the beginning of theline, use a ^ (caret character) as the first character in the search string,followed by a. (dot character), and then followed by the file name or directory tobe excluded.

If the file name or directory being excluded is a substring of another file nameor directory, use ^. (caret character followed by dot character) to indicate thatthe search should begin at the beginning of the line and/or use $ (dollar signcharacter) to indicate that the search should end at the end of the line.

. To list each file as it is backed up, select yes in the List files as they are backedup? field. Otherwise, you see a percentage–completed progress message whilethe backup is created.

. If you modified the image.data file and do not want a new one created, select nofor Generate new /image.data file?. (The image.data file contains informationabout the sizes of all the file systems and logical volumes in your rootvg.)

. If you are creating a bootable tape and you want to expand the system /tmp filesystem (if required by the backup program), select yes for EXPAND /tmp ifneeded?.

. If the tape drive you are using provides packing (or compression), set the Disablesoftware packing of backup? field to yes.

. If you chose tape as the backup medium, either leave the default in the Number ofBLOCKS to write in a single output field or enter a different number.

. If you chose file as the backup medium, press Enter. If you chose tape as thebackup medium, insert the first blank backup tape into the drive and press Enter.

3. The COMMAND STATUS screen displays, showing status messages while thesystem makes the backup image.

If you chose tape as the backup medium, the system might prompt you to insert thenext tape during the backup by displaying a message similar to the following:

Mount next Volume on /dev/rmt0 and press Enter.

If this message displays, remove the tape and label it, including the BOS versionnumber. Then insert another tape and press Enter.

When the backup process finishes, the COMMAND: field changes to OK.

4. When the backup completes, press F10 to exit SMIT.

5. If you selected tape as the backup medium, remove the last tape and label it.Write–protect the backup tapes.

6. Record any backed–up root and user passwords. Remember that these passwordsbecome active if you use the backup to either restore this system or install anothersystem.

You have created the backup of your root volume group (rootvg). If you created bootabletapes, you can use these tapes to start your system if for some reason you cannot bootfrom hard disks.


System Backup to CD–R, DVD–R, or DVD–RAM

Creating a backup on CD–R, DVD–R, or DVD–RAM media is similar to making a backuptape for your personal use, but with some noticeable differences. For DVD media, thefollowing formats for creating backups are available:

• ISO9660 CD format, which is available for DVD–R/DVD–RAM media.

• Universal Disk Format (UDF), which is available for DVD–RAM media. For informationabout creating a backup to DVD–RAM using UDF, see DVD–RAM and Universal DiskFormat on page 14-9.

Note: For information about CD–R, DVD–R, or DVD–RAM drives and CD–R, DVD–R, orDVD–RAM creation software, refer to the following readme file:

/usr/lpp/bos.sysmgt/mkcd.README.txt

Both Web-based System Manager and SMIT use the mkcd command, which calls themksysb or savevg command, if needed.

For system backups, the CDs or DVDs can be created as:

• Non–bootable CDs or DVDs

• Bootable CDs or DVDs

In AIX 5.2, a bootable system backup contains the chrp boot image and all the device andkernel packages necessary to install a system. A backup CD or DVD can be used to install(clone) a large number of machines, which is convenient when each machine in the systemenvironment needs to have the same image installed.

Note: It is possible that a backup CD or DVD would not boot all machines of thesame type because not every machine has the same hardwareconfiguration. Depending on what packages were made available duringthe creation of the backup, the backup might not have all the necessarypackages to boot an individual system. Most required packages for systemsare present on the BOS AIX 5.2 media.

Web-based System Manager and SMIT interfaces are available for the mkcd command.Online help can guide you through the required steps.

Hardware and Software RequirementsThe mkcd command requires that you already have the software installed to create aCD/DVD file system in Rock Ridge format and to burn or write the CD/DVD. The GNUversions of the cdrecord and mkisofs commands are installed with a BOS installation.Hardware and software that has been tested with this command includes the following:

Software Hardware

GNU and Free Software Foundation, Inc.

readcd command version 1.9mkisofs command version 1.13

Matsushita LF–D291 DVD–RAM

Using the mkcd CommandTo run the mkcd command, you need extra working space. A separate file system ordirectory is required for each of the following:

• Storing a mksysb or savevg image

• Storing the CD or DVD file system contents

• Storing the CD or DVD images before they are recorded


The mkcd command creates the following file systems if they are not already present or ifalternative file systems or directories have not been specified:

/mkcd/mksysb_imageSpace requirement depends on the size of the mksysb image that is to becreated. The mkcd command attempts to calculate this space and verifythat adequate space is available before starting to create the mksysbimage.

Note: When the mkcd command calculates the spacerequirements needed for the /mkcd/mksysb_imagedirectory, it also adds the space used by the excluded files(/etc/exclude.rootvg). It is therefore possible that themkcd command might not be able to create the/mkcd/mksysb_image directory.

/mkcd/cd_fs Requires 645 megabytes (up to 4.38 GB for DVD)

/mkcd/cd_imagesRequires at least 645 megabytes (up to 4.38 GB for DVD) of space. If the–R or –S flags are used to specify not removing the images and there aremultiple volumes required, more space must be provided.

The space used in these file systems is only temporary (unless the –R or –S flag is specifiedto save the images). If the mkcd command creates the file systems, it also removes them.Each file system or directory might require over 645 megabytes (up to 4.38 GB for DVD).

If your machine does not have sufficient space, you can use NFS to mount some spacefrom another server system; however, the file systems must be writable. You can create a/mkcd file system that is very large (1.5 GB for CD or 9 GB for DVDs). The /mkcd filesystem can then be mounted onto the clients when they want to create a backup CD orDVD for their systems. When creating very large backups (larger than 2 GB) with the mkcdcommand, the file system must be large–file enabled and the ulimit values must be set tounlimited.

The mkcd command with the –L flag allows the creation of ISO9660 DVD–sized images.The mkcd command with the –U flag allows the creation of UDF DVD images.

Creating a Root Volume Group Backup on CD or DVD with the ISO9660 FormatYou can use Web-based System Manager or SMIT to create a root volume group backup onCD or DVD with the ISO9660 format, as follows:

• Use the Web-based System Manager Backup and Restore application and selectSystem backup wizard method. This method lets you create bootable or non–bootablebackups on CD–R, DVD–R, or DVD–RAM media.

OR

• To create a backup to CD, use the smit mkcd fast path.

• To create a backup to DVD, use the smit mkdvd fast path and select ISO9660 (CDformat).

The following procedure shows you how to use SMIT to create a system backup to CD.(The SMIT procedure for creating a system backup to an ISO9660 DVD is similar to the CDprocedure.)

1. Type the smit mkcd fast path. The system asks whether you are using an existingmksysb image.

2. Type the name of the CD–R device. (This can be left blank if the Create the CD now?field is set to no.)

3. If you are creating a mksysb image, select yes or no for the mksysb creation options,Create map files? and Exclude files?. Verify the selections, or change as appropriate.


The mkcd command always calls the mksysb command with the flags to extend /tmp.

You can specify an existing image.data file or supply a user–defined image.data file.See step 16.

4. Enter the file system in which to store the mksysb image. This can be a file system thatyou created in the rootvg, in another volume group, or in NFS–mounted file systemswith read–write access. If this field is left blank, the mkcd command creates the filesystem, if the file system does not exist, and removes it when the command completes.

5. Enter the file systems in which to store the CD or DVD file structure and final CD or DVDimages. These can be file systems you created in the rootvg, in another volume group,or in NFS–mounted file systems. If these fields are left blank, the mkcd commandcreates these file systems, and removes them when the command completes, unlessyou specify differently in later steps in this procedure.

6. If you did not enter any information in the file systems’ fields, you can select to have themkcd command either create these file systems in the rootvg, or in another volumegroup. If the default of rootvg is chosen and a mksysb image is being created, themkcd command adds the file systems to the exclude file and calls the mksysbcommand with the –e exclude files option.

7. In the Do you want the CD or DVD to be bootable? field, select yes to have a bootimage created on the CD or DVD. If you select no, you must boot from a product CD atthe same version.release.maintenance level, and then select to install the systembackup from the system backup CD.

8. If you change the Remove final images after creating CD? field to no, the file systemfor the CD images (that you specified earlier in this procedure) remains after the CD hasbeen recorded.

9. If you change the Create the CD now? field to no, the file system for the CD images(that you specified earlier in this procedure) remains. The settings that you selected inthis procedure remain valid, but the CD is not created at this time.

10.If you intend to use an Install bundle file, type the full path name to the bundle file. Themkcd command copies the file into the CD file system. You must have the bundle filealready specified in the BUNDLES field, either in the bosinst.data file of the mksysbimage or in a user–specified bosinst.data file. When this option is used to have thebundle file placed on the CD, the location in the BUNDLES field of the bosinst.data filemust be as follows:

/../usr/sys/inst.data/user_bundles/ bundle_file_name

11.To place additional packages on the CD or DVD, enter the name of the file that containsthe packages list in the File with list of packages to copy to CD field. The format ofthis file is one package name per line.

If you are planning to install one or more bundles after the mksysb image is restored,follow the directions in the previous step to specify the bundle file. You can then use thisoption to have packages listed in the bundle available on the CD. If this option is used,you must also specify the location of installation images in the next step.

12.Enter the location of installation images that are to be copied to the CD file system (ifany) in the Location of packages to copy to CD field. This field is required if additionalpackages are to be placed on the CD (see the previous step). The location can be adirectory or CD device.

13.You can specify the full path name to a customization script in the Customization scriptfield. If given, the mkcd command copies the script to the CD file system. You must havethe CUSTOMIZATION_FILE field already set in the bosinst.data file in the mksysbimage or else use a user–specified bosinst.data file with the CUSTOMIZATION_FILEfield set. The mkcd command copies this file to the RAM file system. Therefore, the pathin the CUSTOMIZATION_FILE field must be as follows:

/../ filename


14.You can use your own bosinst.data file, rather than the one in the mksysb image, bytyping the full path name of your bosinst.data file in the User supplied bosinst.datafile field.

15.To turn on debugging for the mkcd command, set Debug output? to yes. The debugoutput goes to the smit.log.

16.You can use your own image.data file, rather than the image.data file in the mksysbimage, by typing the full path name of your image.data file for the User suppliedimage.data file field.

DVD–RAM and Universal Disk FormatThis section provides information on the Universal Disk Format (UDF) and how to createsystem backups using DVD–RAM media and UDF.

UDF allows you to manipulate files directly on the DVD–RAM media. The system backupimage is an archived file composed of many files that cannot be manipulated. However, theinstallation packages and any files that are not contained in the backup image, can bedirectly manipulated on the DVD–RAM. After the DVD is mounted the files can be changedby using an editor or new files can be copied to the DVD using the various copy and restorecommands such as the cp, mv, restore commands.

With UDF and DVD–RAM, system space is only needed for the backup image. A high–leveldescription of the UDF backup process is as follows:

1. Create a backup of a volume group to a file (archive) on a hard disk containing enoughspace to hold the backup image.

2. Populate UDF with files needed to boot and install a system.

3. Copy backup to DVD–RAM media.

The mkcd command with the –U flag is used to create a UDF file system on the DVD–RAM.

UDF allows for the possibility of changing files directly on the DVD–RAM media, such as abosinst.data file and image.data or vgname.data file. Without UDF for example, to add auser–defined bosinst.data file to a backup image, you must restore the backup image to alocation, add the file, and then back up the files again.

Or, you had to create a supplemental diskette containing the changed bosinst.data file, anduse the supplemental diskette in conjunction with the backup. However, some systemconfigurations might not provide diskette drives, making this procedure more difficult.

Creating a Root Volume Group Backup on DVD–RAM with Universal Disk Format

To create a root volume group backup on DVD–RAM with UDF, do the following:

• Use the Web-based System Manager Backup and Restore application and selectSystem backup wizard method. This method lets you create bootable or non–bootablebackups on DVD–RAM media.

OR

• Use SMIT to create a backup to DVD–RAM with UDF, as follows:

1. Enter the smit mkdvd fast path. The system asks whether you are using an existingmksysb image.

2. Select UDF (Universal Disk Format).

3. Enter the name of the DVD–RAM device.

4. If you are creating a mksysb image, select yes or no for the mksysb creationoptions. The options are as follows:

. Create map files?

. Exclude files?


The mkcd command always calls the mksysb command with the flags to extend/tmp.

You can specify an existing image.data file or supply a user–defined image.data.

5. Enter the file system or directory in which to store the mksysb image. This can be afile system you created in the rootvg, in another volume group, or in NFS mountedfile systems with read–write access. If left blank, the mkcd command creates the filesystem and removes it when the command completes.

6. If you did not enter information in the file system field, you can select to have themkcd command either create these file systems in the rootvg, or in another volumegroup. If the default of rootvg is chosen and a mksysb image is being created, themkcd command adds the file systems to the exclude file and calls the mksysbcommand with the exclude files option –e.

7. Do you want the DVD to be bootable? If you select no, you must boot from a productCD at the same version.release.maintenance level, and then select to install thesystem backup from the system backup DVD.

8. If you intend to use an Install bundle file, enter the full path name to the bundle file.The mkcd command copies the file into the DVD file system. You must have thebundle file already specified in the BUNDLES field, either in the bosinst.data file ofthe mksysb image or in a user–specified bosinst.data file. When this option is usedto have the bundle file placed on the DVD, the location in the BUNDLES field of thebosinst.data file must be as follows:

/../usr/sys/inst.data/user_bundles/ bundle_file_name

9. Additional packages can be placed on the CD by entering the name of the file thatcontains the packages list in the File with list of packages to copy to DVD field.The format of this file is one package name per line.

If you are planning to install one or more bundles after the mksysb image is restored,follow the directions in the previous step to specify the bundle file. You can then usethis option to have packages listed in the bundle available on the DVD. If this option isused, you must also specify the location of installation images in the next step.

10.Enter the location of installation images that are to be copied to the CD file system (ifany) in the Location of packages to copy to DVD field. This field is required ifadditional packages are to be placed on the DVD (see the previous step). Thelocation can be a directory or DVD device.

11.You can specify the full path name to a customization script in the Customizationscript field. If given, the mkcd command copies the script to the CD file system. Youmust have the CUSTOMIZATION_FILE field already set in the bosinst.data file inthe mksysb image or use a user–specified bosinst.data file with theCUSTOMIZATION_FILE field set. The mkcd command copies this file to the RAMfile system. Therefore, the path in the CUSTOMIZATION_FILE field must be asfollows:

/../ filename

12.You can use your own bosinst.data file, rather than the one in the mksysb image, byentering the full path name of your bosinst.data file in the User suppliedbosinst.data file field.

13.To enable debugging for the mkcd command, set Debug output? to yes. The debugoutput goes to the smit.log.

14.You can use your own image.data file, rather than the image.data file in the mksysbimage, by entering the full path name of your image.data file for the User suppliedimage.data file field.


User Volume Group BackupThe savevg command provides the ability to create a user–volume group backup to a CD,DVD, tape, or file. The savevg command finds and backs up all files belonging to aspecified volume group. The volume group must be varied–on, and the file systems must bemounted.

This user backup contains a copy of a non–rootvg volume group, and is useful for volumegroups that contain user data.

The savevg command uses a data file created by the mkvgdata command. The data filecreated is as follows:

/tmp/vgdata/ vgname / vgname .data

The vgname.data file contains information about a user volume group. The savevgcommand uses this file to create a backup image that can be used by the restvg commandto re–create the user volume group.

The savevg command with the –r flag is used to back up only a user–volume group’slogical volume structure information. The data needed to list backup properties is alsobacked up. The –r flag runs the mkvgdata command for the volume group specified tocreate a vgname.data file. The –r flag backs up only the vgname.data file, any map files,and the backup.data file. The backup image that is created is used with the restvg –rcommand option to create only the volume group, logical volumes, and file systeminformation contained in the file, without restoring any data. For example, to back up onlythe paul user volume group’s structure information to the /vg_backup/paul_vg_datafile, type the following:

savevg –r –f /vg_backup/paul_vg_data paul

You can also use the mkcd command to create a user volume group backup to CD or DVD.The mkcd command saves one volume group at a time to a CD or DVD.

The mkcd command with the –L flag allows the creation of ISO9660 DVD sized images.The mkcd command with the –U flag allows the creation of UDF DVD images.

If your rootvg image and savevg image are small enough to fit on one CD, you can savethem both by using the –l (stacklist) and –z (customization_script) flags. The –l flag gives alist of images to copy to the CD. The –z flag lets you create a script to restore savevgbackups. For example, if you make a copy of a non–rootvg volume group ahead of time,and then write a script that calls the restvg command, your non–rootvg volume group wouldbe restored to hdisk2 at the end of the installation of rootvg, as shown by the followingcommand:

restvg –d /SPOT/installp/ppc/ savevg_image hdisk2

This procedure is recommended only if you know you want to restore the non–rootvgvolume group every time you install. Otherwise, you might just want to store it on theCD/DVD, then use restvg to restore it after reboot. The restvg command can restore fromCD or DVD if the name of the image is savevg_image. If you save the non–rootvg backupon a CD or DVD with a different file name, you can insert that CD or DVD and use the fullpath to the file name as the device for the restvg command.

Use either Web-based System Manager or SMIT to back up user volume groups to CD orDVD.

Creating a User Volume Group Backup Using Web-based System Manager

Use Web-based System Manager and select System backup wizard method. You cancreate a non–bootable CD or DVD that contains only a volume group backup image of auser volume group.


Creating a User Volume Group Backup Using SMITUse SMIT to create a backup image of a user volume group, as follows:

1. To back up a user volume group to tape or file using SMIT, type smit savevg on thecommand line. Back up a user volume group to CD by typing smit savevgcd on thecommand line. Back up a user volume group to DVD by typing smit savevgdvd onthe command line.

2. When the Save a Volume Group screen displays, use the steps for backing up the rootvolume group as a guide for backing up user volume groups. There is one exception tothis procedure. If you want to exclude files in a user volume group from the backupimage, create a file named /etc/exclude. volume_group_name, wherevolume_group_name is the name of the volume group you want to backup.

3. If you exclude files, edit the /etc/exclude. volume_group_name file and enter thepatterns of file names that you do not want included in your backup image. The patternsin this file are input to the pattern–matching conventions of the grep command todetermine which files are excluded from the backup.

Backup OptionsAfter you have a system backup or a user volume group backup, you may want to verify thebackup or list information about the backup image. This section provides information on theoperations you can perform on a backup image. The commands used to perform theseoperations are the lsmksysb command for system backups, and the lssavevg commandfor user volume groups. Using the lsmksysb command or the lssavevg command, you canperform the following operations:

• Preview Information About a Backup on page 14-12

• Verifying a System Backup on page 14-13

• View the Backup Log on page 14-13

• List Information About Filesets in a System Image on page 14-13

• List Files in a System Image on page 14-14

Preview Information About a BackupThe preview option allows you to view volume group information, the date and time thebackup was made, and the level of AIX.

You can use the lsmksysb command or the lssavevg command with the –l option topreview a backup image. For example, to preview a system backup file called/tmp/mybackup, type the following:

# lsmksysb –l –f /tmp/mybackup



VOLUME GROUP: rootvg

BACKUP DATE/TIME: Mon Jul 29 22:03:27 CDT 2002

UNAME INFO: AIX va08 2 5 000974AF4C00

BACKUP OSLEVEL: 5.2.0.0

none

MAINTENANCE LEVEL: none

BACKUP SIZE (MB): 1408

SHRINK SIZE (MB): 1242

rootvg:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

hd5 boot 1 1 1 closed/syncd N/A

hd6 paging 16 16 1 open/syncd N/A

hd8 jfs2log 1 1 1 open/syncd N/A

hd4 jfs2 1 1 1 open/syncd /

hd2 jfs2 21 21 1 open/syncd /usr

hd9var jfs2 1 1 1 open/syncd /var

hd3 jfs2 1 1 1 open/syncd /tmp

hd1 jfs2 1 1 1 open/syncd /home

hd10opt jfs2 1 1 1 open/syncd /opt

fslv00 jfs2 31 31 1 open/syncd /export/nim

fslv01 jfs2 1 1 1 open/syncd /tftpboot

To preview a backup image in the SMIT, use the lsbackupinfo fast path.

Verifying a System Backup

To list the contents of a mksysb image on tape or CD, you can use either Web-basedSystem Manager (type wsm on the command line, then choose the Backup and Restoreapplication) or SMIT (type smit lsmksysb on the command line). The listing verifies mostof the information on the tape or CD, but does not verify that the backup media can bebooted for installations. The only way to verify that the boot image(s) on a mksysb tape orCD function properly is by booting from the media.

View the Backup LogYou can view the backup log that is created each time a volume group is backed up. The logfile contains information on previous volume group and system backups.

You can use the lsmksysb command or the lssavevg command with the –B option to viewthe backup log file. Type:

# lsmksysb –B


#Device;Command;Date;Shrink Size;Full Size;Maintenance Level

/export/mksysb/generic_sysb;”mksysb –X –e /export/mksysb/generic_sysb”;M

on Jul 29 22:11:17 CDT 2002;1242;1408;

/export/mksysb/generic_sysb;”mksysb –X –e /export/mksysb/generic_sys

b”;Tue Jul 30 16:38:31 CDT 2002;2458;2720;

To view the backup log in the SMIT, select View the Backup Log in the System BackupManager menu.

List Information About Filesets in a System ImageYou can view the filesets installed in a system backup using the lsmksysb command withthe –L option. For example, to view the filesets installed in a system backup, type thefollowing:

# lsmksysb –L –f generic_sysb



Fileset Level State Description

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Path: /usr/lib/objrepos

IMNSearch.bld.DBCS 2.4.0.0 COMMITTED NetQuestion DBCS Buildtime

Modules

.

.

.

bos.terminfo.wyse.data 5.2.0.0 COMMITTED Wyse Terminal Definitions

bos.txt.spell.data 5.2.0.0 COMMITTED Writer’s Tools Data

bos.txt.tfs.data 5.2.0.0 COMMITTED Text Formatting Services Data

To view the filesets installed in a system backup in SMIT, use the lslppbackup fast path.

List Files in a System ImageYou can list all the files and file sizes in a backup using the lsmksysb command or thelssavevg command. For example, to view the files and file sizes in a system backup, typethe following:

# lsmksysb –f generic_sysb


.

.

.

353218 ./smit.log

252 ./smit.script

0 ./tftpboot

0 ./tmp

5 ./u

21 ./unix

The total size is 629313078 bytes.

To view the files and file sizes in a user–volume group backup that contains only theuser–volume group’s structure information, type the following:

# lssavevg –f /vg_backup/paul_vg_data –l


VOLUME GROUP: paul

BACKUP DATE/TIME: Fri Feb 28 12:30:34 CST 2003

UNAME INFO: AIX va06 2 5 000917184C00

BACKUP OSLEVEL: 5.2.0.10

MAINTENANCE LEVEL: 52010

BACKUP SIZE (MB): 0

SHRINK SIZE (MB): 0

VG DATA ONLY: yes

paul:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

To view the files and file sizes in a system backup in SMIT, use the lsmksysb fast path.


Installing System Backups

This chapter describes how to install the Base Operating System (BOS) using a systembackup image, also called a mksysb image. You can use a system backup to restore acorrupted operating system. But installing a system from a backup can also reduce (or eveneliminate) repetitive installation and configuration tasks. For example, you can use a backupto transfer optional software installed on the source system (the machine from which youcreated the backup copy), in addition to the basic operating system. Also, the backup imagecan transfer many user configuration settings to the target system (a different machine onwhich you are installing the system backup).

The procedure you use to install from a system backup depends on whether you areinstalling on the source or target system and which interface you want to use:

• Cloning a System Backup on page 14-16 contains the procedure to install a systembackup on a target machine to propagate a consistent operating system, optionalsoftware, and configuration settings.

• Installing a System Backup on the Source Machine on page 14-16 contains theWeb–based System Manager and SMIT procedures to reinstall an operating systemonto the same machine from which you created the backup.

You can install a system from a backup image that is stored on tape or CD, or in a file. If youwant to install a backup stored in a directory on your network installation server, refer toUsing a mksysb Image to Install the Base Operating System (BOS) on a NIM Client(mksysb Installation) on page 23-12.

The procedures to install from backup operate either in prompted or nonprompted mode,depending on conditions set in the /bosinst.data file and on compatibility between thebackup image and the installed machine. See Customized BOS Installations on page 10-1for information on how to modify the bosinst.data file to preset installation parameterswhen you create a system backup.

When installing the backup image, the system checks whether the target system hasenough disk space to create all the logical volumes stored on the backup. If there is enoughspace, the entire backup is recovered. Otherwise, the installation halts and the systemprompts you to choose additional destination hard disks.

File systems are created on the target system at the same size as they were on the sourcesystem, unless the backup image was created with SHRINK set to yes in the image.datafile (or you set it to yes in the BOS Install menus). An exception is the /tmp directory, whichcan be increased to allocate enough space for the bosboot command. For informationabout setting variables, refer to the image.data file in AIX 5L Version 5.2 Files Reference.

After installing the backup image, the installation program reconfigures the Object DataManager (ODM) on the target system. If the target system does not have exactly the samehardware configuration as the source system, the program might modify device attributes inthe following target system files:

• All files in /etc/objrepos beginning with Cu

• All files in the /dev directory

The settings in the bootlist of the target system are not restored. After a system backuprestore, the bootlist is reset to the primary boot device.


Cloning a System BackupWith a mksysb image, you can clone one system image onto multiple target systems.However, the target systems might not contain the same hardware devices or adapters, orrequire the same kernel (uniprocessor or microprocessor) as the source system. Beginningin AIX 5.2, all devices and kernels are automatically installed during a BOS installation. As aresult, when you create a system backup, the mksysb image contains all the device andkernel support. For example, you can create a system backup from System_A and installSystem_A ’s mksysb image onto System_B without having to use product media to bootSystem_B. For more information on installing all devices and kernels, see Install All Deviceand Kernel Support Before the Backup is Created.

Beginning in AIX 5.2, if you are performing a clone installation, device information will not berestored to the target system. During a clone installation, the BOS installation processverifies that the mksysb image is from the system you are trying to install. If the targetsystem and the mksysb image are different, the device is not recovered.

If the source system does not have the correct passwords and network information, you canmake modifications on the target system now. Also, some products (such as graPHIGS)ship device–specific files. If your graphics adapter is different on the target system, verifythat the device–specific filesets for graphics–related LPPs are installed.

Installing a System Backup on the Source Machine, ”networkinstallation”

You can use Web–based System Manager or SMIT to restore an operating system onto thesame machine from which you created the backup. For either interface, the followingconditions must be met before beginning the procedure:

• All hardware must already be installed, including external devices, such as tape andCD/DVD–ROM drives.

• Obtain the system key for the lock (if present) on your system unit.

• Obtain your system backup image from one of the following sources:

CD or DVD BOS CDs, created in one of the following ways:

• Using the Web–based System Manager Backup and Restoreapplication. Select System backup to writable CD.

• Using the SMIT Back Up This System to CD menu.

• From the command line, using the mkcd command.

Tape BOS tapes, created in one of the following ways:

• Using the Web–based System Manager Backup and Restoreapplication. Select Back up the system.

• Using the SMIT Back Up the System to Tape/File menu.

• From the command line, using the mksysb –i Target command.

Network The path to your backup image file. For information about installinga backup across a network, refer to Using a mksysb Image toInstall the Base Operating System (BOS) on a NIM Client (mksysbInstallation) on page 23-12.

Note: Before you begin, select the tape or CD/DVD–ROM drive as the primary bootdevice. For additional information, refer to the section in your hardware documentationthat discusses system management services.

To use Web–based System Manager:

1. Start the Web–based System Manager by typing wsm on the command line as root user.

2. Expand Software in the Navigation Area, select Overview and Tasks, then selectReinstall Operating System.


3. Choose the installation device:

– Network

If you choose this option, your machine must either be a configured NIM client, orhave access to a NIM environment. If your machine is not a NIM client, the ReinstallBase Operating System wizard leads you through the process. For more informationon setting up a NIM environment, see Using Installation Images to Install the BaseOperating System (BOS) on a NIM Client on page 23-10.

– Tape or CD/DVD–ROM

4. Choose Install a system backup image (mksysb) as the installation type.

5. Follow the wizard prompts to complete the procedure.

To use SMIT:

1. Verify that your system is shut down. If your machine is currently running, you mustpower it off now by following these steps:


b. Enter the following command:

shutdown –F

c. If your system does not automatically power off, place the power switch in the Off ( 0 )position.

Attention: Do not turn on the system unit until Step 5 on page 14-18 .

2. Turn on all attached external devices. These include:

– Terminals

– CD or DVD drives

– Tape drives

– Monitors


Turning on the external devices first is necessary so that the system unit can identifythem during the startup (boot) process.

3. Insert the installation media into the tape or CD or DVD drive.

You might find that on certain tape drive units, the tape drive door does not open whilethe system is turned off. If you have this problem, use the following procedure:

a. Turn on the system unit.

b. Insert the boot installation tape (insert Volume 1 if you received more than onevolume).

c. Turn off the system unit and wait for 30 seconds.

4. If you are not using an ASCII terminal, skip to Step 6. If you are using an ASCII terminal,use the following criteria to set the communications, keyboard, and display options.

Note: If your terminal is an IBM 3151, 3161, or 3164, press the Ctrl+Setup keys todisplay the Setup Menu and follow the onscreen instructions to set these options. Ifyou are using some other ASCII terminal, refer to the appropriate documents forinformation about how to set these options. Some terminals have different optionnames and settings than those listed here.


Communication Options

Option Setting

Line Speed (baud rate) 9600

Word Length (bits per character) 8

Parity no (none)

Number of Stop Bits 1

Interface RS–232C (or RS–422A)

Line Control IPRTS

Keyboard and Display Options

Option Setting

Screen normal

Row and Column 24x80

Scroll jump

Auto LF (line feed) off

Line Wrap on

Forcing Insert line (or both)

Tab field

Operating Mode echo

Turnaround Character CR

Enter return

Return new line

New Line CR

Send page

Insert Character space

5. Turn the system unit power switch from Off ( 0 ) to On ( | ). The system begins bootingfrom the backup media. If your system is booting from tape, it is normal for the tape tomove back and forth. If your system has an LED display, the three–digit LED shoulddisplay c31.

Note: You can boot from production media (tape or CD) if your backup media fails toboot. The initial Welcome screen includes an option to enter a maintenance mode inwhich you can continue the installation from your backup media. Refer toTroubleshooting an Installation from a System Backup on page 17-2 for moreinformation.

If you have more than one console, each terminal and directly attached display device(or console) might display a screen that directs you to press a key to identify your systemconsole. A different key is specified for each terminal displaying this screen. If thisscreen is displayed, then press the specified key only on the device to be used as thesystem console. (The system console is the keyboard and display device used forinstallation and system administration.) Press a key on only one console.

Note: If the bosinst.data file lists a valid display device for the CONSOLE variable,you do not manually choose a system console. Read Customized BOS Installationson page 10-1 for more information about the bosinst.data file.


6. The type of installation that begins is determined by the settings of the PROMPT field inthe control_flow stanza of the bosinst.data file. Use the following criteria to determinethe type of installation you will be using:

PROMPT = no Nonprompted Installation. This installation method is used if thebackup image is configured to install automatically, without havingto respond to the installation program. Go to step 8.

PROMPT = yes Prompted Installation. This installation method is used if you needto use menu prompts to install the backup image. Also, use thisinstallation method if a nonprompted installation halts and theWelcome to Base Operating System Installation and Maintenancescreen displays. Go to step 9.

7. A successful nonprompted installation requires no further instructions because theinstallation is automatic.

Note: If the backup image holds source system–configuration information that isincompatible with the target system, the nonprompted installation stops and aprompted installation begins.

The Installing Base Operating System screen displays before the installation starts. Thenonprompted installation pauses for approximately five seconds before beginning. Afterthis time, the non–prompted installation continues to completion.

However, if you decide to interrupt the automatic installation and start a promptedsession, type 000 (three zeros) at the terminal and follow the remaining steps in thisprocedure.

8. The Welcome to the Base Operating System Installation and Maintenance screendisplays.

Note: You can view Help information at each screen of this installation process bytyping 88.

Choose the Change/Show Installation Settings and Install option.

9. The System Backup Installation and Settings displays. This screen shows currentsettings for the system. An ellipsis follows the disk listed in the first line if there is morethan one disk selected.

10.Either accept the settings or change them. For more information on using map files, seeCreating System Backups on page 14-2.

To accept the settings and begin the installation, skip to step 16.

To change the settings, continue with step 11.

11.Type 1 in the System Backup Installation and Settings screen to specify disks whereyou want to install the backup image. The Change Disk(s) Where You Want to Installscreen displays. This screen lists all available disks on which you can install the systembackup image. Three greater–than signs (>>>) mark each selected disk.

Type the number and press Enter for each disk you choose. Type the number of aselected disk to deselect it. You can select more than one disk.

Note: You can also specify a supplemental disk by typing 66 and pressing the Enterkey for the Disks not known to Base Operating System Installation option. Thisoption opens a new menu that prompts for a device support media for thesupplemental disk. BOS installation configures the system for the disk and thenreturns to the Change Disk(s) Where You Want to Install screen.


12.After you have finished selecting disks, press the Enter key.

The screen that displays after you press the Enter key is dependent on the availability ofmap files for all of the selected disks. The criteria for this is as follows:

– If one or more selected disks have no maps, BOS installation returns directly to theSystem Backup Installation and Settings screen. Skip to step 15.

– If all selected disks have maps, the Change Use Maps Status screen displays, whereyou choose whether to use maps for installation. Continue with step 14.

To preserve the placement of files during a future restoration of the backup, you cancreate map files before backing up a system. Map files, stored in the/tmp/vgdata/rootvg directory, match the physical partitions on a drive to its logicalpartitions. Create map files either with the SMIT Backup the System menu, usingWeb–based System Manager, or using the –m option when you run the mksysbcommand.

For more information about map files, see Using Map Files for Precise Allocation in AIX5L Version 5.2 System Management Concepts: Operating System and Devices.

13.Type either 1 or 2 in the Change Use Maps Status screen to specify whether theinstallation program is to use maps.

When you complete this choice, BOS installation returns to the System BackupInstallation and Settings screen.

14.Decide whether BOS installation is to shrink file systems on the disks where you installthe system. When you choose this option, the logical volumes and file systems within avolume group are re–created to the minimum size required to contain the data. Thisreduces wasted free space in a file system.

File systems on your backup image might be larger than required for the installed files.Press the 2 key to toggle the Shrink File Systems option between Yes and No in theSystem Backup Installation and Settings screen. The default setting is No.

Note: Shrinking the file system disables the use of maps.

15.Type 0 to accept the settings in the System Backup Installation and Settings screen.

The Installing Base Operating System screen displays the rate of completion andduration.

If you specified a supplemental disk in step 12, an untitled screen temporarily replacesthe Installing Base Operating System screen. When this screen displays, it prompts youto place the device–support media in the drive and press the Enter key. BOS installationreconfigures the supplemental disk, then returns to the Installing Base Operating Systemscreen.

The system reboots automatically when the installation completes.

15-1Alternate Disk Installation

Chapter 15. Alternate Disk Installation

Alternate disk installation lets you install the operating system while it is still up and running,which reduces installation or upgrade downtime considerably. It also allows large facilities tobetter manage an upgrade because systems can be installed over a longer period of time.While the systems are still running at the previous version, the switch to the newer versioncan happen at the same time.

Alternate disk installation can be used in the following ways:

• Installing a mksysb image on another disk. For further information, see Alternatemksysb Disk Installation on page 15-1.

• Cloning the current running rootvg to an alternate disk. For further information, seeAlternate Disk rootvg Cloning on page 15-2.

• Using the Network Installation Management (NIM) environment to perform a alternatedisk migration installation of a NIM client. For further information, see Alternate DiskMigration Installation on page 15-4.

Filesets to InstallAn alternate disk installation uses the following filesets:

bos.alt_disk_install.boot_images Must be installed for alternate disk mksysbinstallations.

bos.alt_disk_install.rte Must be installed for rootvg cloning andalternate disk mksysb installations.

Alternate mksysb Disk InstallationAlternate mksysb installation involves installing a mksysb image that has already beencreated from a system, onto an alternate disk of the target system. The alternate disk ordisks cannot contain a volume group. The mksysb image is created on a system that eitherwas the same hardware configuration as the target system, or had all the device and kernelsupport installed for a different machine type or platform, or different devices. The installeddevice and kernel support would be as follows:

• devices.*

• bos.mp

• bos.up

• bos.mp64, if necessary

Note: Beginning in AIX 5.2, all device and kernel support is automaticallyinstalled during a base operating system installation.

When the alt_disk_install command is run, the image.data file from the mksysb image isused by default (unless a customized image.data is given) to create the logical volumesand file systems. The prefix alt_ is added to the logical volume names, and the file systemsare created with a prefix of /alt_inst. For example, hd2 would be created as alt_hd2, andits file system, /usr, would be created as /alt_inst/usr. These names are changed back totheir original names at the end of the alternate disk installation process.


The mksysb image is then restored into the alternate file system. A prepopulated bootimage is then copied to the boot logical volume of the altinst_rootvg, and the boot recordof the boot disk is modified to allow booting from the disk.

At this point, a script can be run to allow for any customization before the system isrebooted. The alternate file systems are still mounted as /alt_inst/ real_file_system (forexample: /alt_inst/usr, /alt_inst/home). Files can be accessed at this point, but nothing canbe installed into the alternate file system because the kernels and libraries of the mksysbimage may not match those of the running system.

After the optional script is run, the file systems are unmounted, and the logical volume andfile system names are changed to match the image.data file’s names (for example,alt_inst_hd6 is changed to hd6 in the volume group descriptor area). The logical volumesare exported from the Object Data Manager (ODM), but the altinst_rootvg is only variedoff. It is left in the ODM as a placeholder so the disk is not accidentally overwritten. Thedefault action of the alt_disk_install command is to set the bootlist so that the next time thesystem boots, it boots from this newly installed volume group. This default action can beturned off. If specified, the system reboots at this point, and the system reboots from thenew rootvg. The boot process proceeds to a certain point, with the new rootvg ’s filesystems mounted, and the bosboot command is called to rebuild a ”normal” boot logicalvolume. The system then reboots.

After rebooting from the new alternate disk, the former rootvg volume group is contained inan lspv listing as old_rootvg, and includes all disk(s) in the original rootvg. This formerrootvg volume group is set to not varyon at reboot and should only be removed with the–X flag. For example:

alt_disk_install –X old_rootvg

If a return to the original rootvg is necessary, the bootlist command is used to change thebootlist to reboot from the original rootvg.

If it is unclear which disk is the boot disk for a specific volume group, use the –q flag todetermine the boot disk. This flag can be useful when a volume group comprises multipledisks and a change in the bootlist is necessary.

Alternate Disk rootvg CloningCloning the rootvg to an alternate disk has many advantages. One advantage is having anonline backup available, in case of a disk crash. Keeping an online backup requires an extradisk or disks to be available on the system. Another benefit of rootvg cloning occurs whenapplying new maintenance levels or updates. A copy of the rootvg is made to an alternatedisk, then updates are applied to that copy. The system runs uninterrupted during this time.When it is rebooted, the system boots from the newly updated rootvg for testing. If updatescause problems, the old_rootvg can be retrieved by resetting the bootlist and thenrebooting.

By default, calling the alt_disk_install command does the following:

1. Creates an /image.data file based on the current rootvg ’s configuration. A customizedimage.data file can be used.

2. Creates an alternate rootvg (altinst_rootvg).

3. Creates logical volumes and file systems with the alt_inst prefix.

4. Generates a backup file list from the rootvg, and if an exclude.list file is given, thosefiles are excluded from the list.

5. Copies the final list to the altinst_rootvg ’s file systems.

6. If specified, the installp command installs updates, fixes, or new filesets into thealternate file system.

7. The bosboot command creates a boot logical volume on the alternate boot disk.


8. If a customization script is specified, it runs at this point.

9. The file systems are then unmounted, and the logical volumes and file systems arerenamed.

10.The logical volume definitions are exported from the system to avoid confusion withidentical ODM names, but the altinst_rootvg definition is left as an ODM placeholder.

11.By default, the bootlist is set to the new cloned rootvg for the next reboot.

Phased Alternate Disk InstallationFor AIX 4.3.1 and later, alternate disk installation can be performed in stages. Theinstallation itself is broken down into three phases. The default is to perform all three phasesin the same invocation. The phases are as follows:

Phase 1 Creates the altinst_rootvg volume group, the alt_ logical volumes,and the /alt_inst file systems. Also restores the mksysb or rootvgdata.

Phase 2 Runs any specified customization script. For cloning only, installsupdates, new filesets, fixes, or bundles. Also copies a resolv.conffile (if specified) and necessary files to remain a NIM client (ifspecified).

Phase 3 Unmounts the /alt_inst file systems, renames the file systems andlogical volumes, removes the alt_ logical volume names from ODM,and varies off the altinst_rootvg. It also sets the bootlist andreboots (if specified).

As an alternative to running all three phases, the phases can be completed by one of thefollowing methods:

• Each phase separately

• Phases 1 and 2 together

• Phases 2 and 3 together (Phase 2 can be run multiple times before Phase 3 is run.)

You must run Phase 3 to obtain a usable rootvg. Running Phases 1 and 2 leave the/alt_inst file systems mounted. Any time during the phase process and before rebooting,the altinst_rootvg can be removed, and disk cleanup occurs using the following command:

alt_disk_install –X


Alternate Disk Migration InstallationAlternate disk migration installation allows the user to create a copy of rootvg to a free disk(or disks) and simultaneously migrate it through Network Installation Management (NIM) toa new release level. Using alternate disk migration installation over a conventional migrationprovides the following advantages:

• Reduced downtime (the migration is performed while the system is up normally andthere is no need to boot from any media).

• Quick recovery in case of migration failure.

• High degree of flexibility and customization.

Reduced downtime. The migration is performed while the system is up and functioning.There is no requirement to boot from install media, and the majority of processing occurs onthe NIM master.

Quick recovery in the event of migration failure. Because you are creating a copy ofrootvg, all changes are performed to the copy (altinst_rootvg). In the event of seriousmigration installation failure, the failed migration is cleaned up, and there is no need for theadministrator to take further action. In the event of a problem with the new (migrated) levelof AIX, the system can be quickly returned to the premigration operating system by bootingfrom the original disk.

High degree of flexibility and customization in the migration process. This is done withthe use of optional NIM customization resources: image_data, bosinst_data,exclude_files, premigration script, installp_bundle, and post–migration script.

RequirementsAlternate disk migration installation has the following requirements:

• Configured NIM master running AIX 5.1 or later with AIX recommended maintenancelevel 5100–03 or later.

• The NIM master must have bos.alt_disk_install.rte installed in its rootvg and theSPOT which will be used.

• The level of the NIM master rootvg, lpp_source, and SPOT must be at the same level.

• The client (the system to be migrated) must be at AIX 4.3.3 or later.

• The client must have a disk (or disks) large enough to clone the rootvg and anadditional 500 MB (approximately) of free space for the migration. The total amount ofrequired space will depend on original system configuration and migration customization.

• The client must be a registered NIM client to the master.

• The nim master must be able to execute remote commands on the client using the rshdprotocol.

• The client must have a minimum of 128 MBs of memory.

• A reliable network, which can facilitate large amounts of NFS traffic, must exists betweenthe NIM master and the client.

• The client’s hardware should support the level it is migrating to and meet all otherconventional migration requirements.

Note: If you cannot meet the alternate disk migration installation requirements1–10, perform a conventional migration. For information on the conventionalmigration installation method, see Migration Installation. If you cannot meetrequirement 11, no migration installation is possible.

Before performing an alternate disk migration installation, you are required to agree to allsoftware license agreements for software to be installed. You can do this by specifying the


–Y flag as an argument to the alternate disk migration command or setting theADM_ACCEPT_LICENSES environment variable to yes.

LimitationsThe following limitations apply to alternate disk migration installation:

• If the client’s rootvg has the Trusted Computing Base option enabled, either disable it(permanently) or perform a conventional migration. TCB must access file metadata thatis not visible over NFS.

• All NIM resources used must be local to the NIM master.

• During the migration, the client’s active rootvg may experience a small performancedecrease due to increased disk I/O, nfsd activity, and some CPU usage associated withalt_disk_install cloning.

• NFS tuning may be required to optimize performance.

Alternate Disk Migration Installation UsageThe syntax for the alternate disk migration installation command is the following:

nimadm –l lpp_source –c NIMclient –s SPOT –d Targetdisks

[ –a PreMigrationScript ] [ –b installp_bundle] [ –z PostMigrationScript]

[ –e exclude_files] [ –i image_data ] [ –m NFSMountOptions ] [ –o bosinst_data]

[–P Phases] [–Y ] [ –F ] [ –D ] [ –E ] [ –V ] [ { –B | –r } ]

Use the nimadm command to target the aix1 NIM client, using the spot1 NIM SPOTresource, the lpp1 NIM lpp_source resource, and hdisk1 and hdisk2 target disks, by typingthe following:

nimadm –c aix1 –s spot1 –l lpp1 –d ”hdisk1 hdisk2” –Y

Use the –Y flag to agree to all required software license agreements for the software beinginstalled

Alternate Disk Migration Installation ProcessThe nimadm command performs a migration in 12 phases. Each phase can be executedindividually using the –P flag. Before performing a migration in phases, the user shouldhave a good understanding of the nimadm process. The nimadm phases are as follows:

1. The master issues the alt_disk_install command to the client, which makes a copy ofthe rootvg to the target disks (this is Phase 1 of the alt_disk_install process). In thisphase, altinst_rootvg (alternate rootvg) is created.

2. The master runs remote client commands to export all of the /alt_inst file systems to themaster. The file systems are exported as read/write with root access to the master.

3. The master NFS mounts the file systems exported in Phase 2.

4. If a premigration script resource has been specified, it is executed at this time.

5. System configuration files are saved. Initial migration space is calculated and appropriatefile system expansions are made. The bos image is restored and the device database ismerged (similar to a conventional migration). All of the migration merge methods areexecuted and some miscellaneous processing takes place.

6. All system filesets are migrated using installp. Any required RPM images are alsoinstalled during this phase.

7. If a post–migration script resource has been specified, it is executed at this time.

8. The bosboot command is run to create a client boot image, which is written to theclient’s boot logical volume (hd5).

9. All mounts made on the master in phase 3 are removed.

10.All client exports created in phase 2 are removed.


11.The alt_disk_install command is called again (phase 3 of alt_disk_install) to makefinal adjustments and put altinst_rootvg to sleep. The bootlist is set to the target disk(unless the –B flag is used).

12.Cleanup is executed to end the migration. The client is rebooted, if the –r flag isspecified.

Note: The nimadm command supports migrating several clients at the sametime.

For more information about the nimadm command, refer to the AIX 5L Version 5.2Commands Reference.

Data Access Between the Original rootvg and the NewAlternate Disk

You can initiate data access between the original rootvg and the new alternate disk. Avolume group ”wake–up” can be accomplished, on the non–booted volume group. The”wake–up” puts the volume group in a post alt_disk_install Phase 1 state. For example,the /alt_inst file system is then mounted.

The volume group that experiences the ”wake–up” is renamed altinst_rootvg. When dataaccess is no longer needed, the volume group can be ”put to sleep.”

Notes:

1. The running operating system’s version must be greater than or equal to the versionof the volume group that undergoes the ”wake–up.” This might mean that it isnecessary to boot from the altinst_rootvg and ”wake–up” the old_rootvg. Forexample, an alternate disk is created from an alt_disk_install AIX 5.2 mksysb, on aAIX 4.3.0 system. It is then necessary to boot from the AIX 5.2 alternate disk and”wake–up” the AIX 4.3.0 old_rootvg volume group to access data between the twovolume groups.

This limitation is caused by a journaled file system (JFS) log entry incompatibility. It ispossible to ”wake–up” a volume group that contains a more recent version, but thevolume group cannot have ever been the system rootvg. If this was true, the volumegroup would have made JFS log entries that could not be interpreted by an olderversion rootvg, when the volume group was experiencing a ”wake–up.”

The alt_disk_install command does not allow a ”wake–up” to occur on a volumegroup with a more recent version, unless the FORCE environment variable is set toyes.

2. The volume group that experiences a ”wake–up” must be put to sleep before it can bebooted and used as the rootvg.

Attention: If a FORCE ”wake–up” is attempted on a volume group that contains a morerecent version of the running operating system, and the ”waking” volume group has beena system rootvg, errors occur.

Installing to an Alternate Disk using Web–based SystemManager

The graphical interface provides access to Web–based System Manager options forinstalling a mksysb to an alternate disk and for cloning a rootvg to the alternate disk. At anytime during the following procedures, you can view extended help by selecting Contentsfrom the Help menu.

To install a mksysb to an alternate disk, do the following:

1. Start the Web–based System Manager by typing wsm on the command line.


2. Select the Software container.

3. From the pulldown, select Alternate Disk Install––>Install Mksysb on an AlternateDisk.

To clone the rootvg to an alternate disk, do the following:

1. Start the Web–based System Manager by typing wsm on the command line.

2. Select the Software container.

3. From the pulldown, select Alternate Disk Install––>Clone the Rootvg to an AlternateDisk.

Running Alternate Disk Installation Using SMITTo run alternate disk mksysb installation, do the following:

1. At the system prompt, type the smit alt_mksysb fast path.

2. Type or select values in the entry fields. Press Enter after making all desired changes.

To run alternate disk rootvg cloning, do the following:

1. At the system prompt, type the smit alt_clone fast path.

2. Type or select values in the entry fields. Press Enter after making all desired changes.

Alternate Disk Installation and Dynamic Logical PartitioningOn a system that supports dynamic logical partitioning (DLPAR), you can dynamically addan adapter with disks to a running logical partition (LPAR). You can then install a new rootvgvolume group to these newly added target disks using the alt_disk_install command witheither the clone or mksysb option. If you are running the alt_disk_install command withdynamically added target disks on an LPAR system, the following flags might be used:

–O If the target disk will be used to boot an LPAR other than the one where theoperation is being executed, use the –O flag to reset the device information.

–B This flag prevents the bootlist command from being run. A generallimitation of dynamically added disks is that you can not specify them as aboot device (before an initial reboot operation). If you are attempting to bootan LPAR from dynamically added disks, set the boot list in the systemmanagement services (SMS) menus.

–g This flag causes the alt_disk_install command to run without checking ifthe disk is bootable. Dynamically added disks do not appear bootable toAIX until after a reboot operation. The user will need to verify that the newlyadded adapter and disks are bootable.

Examples1. To clone the rootvg running 4.3.2.0 to hdisk1 and update that clone with the latest

maintenance level 4.3.3.0 that is on cd0, run the following command:

alt_disk_install –C –b update_all –l /dev/cd0 hdisk1

In SMIT, use the smit alt_clone fast path and select hdisk1 from the listing for TargetDisk(s) to install, select the update_all bundle from the listings in the Bundle to Installfield, and /dev/cd0 from the listing in the Directory or Device with images field.


2. To clone the rootvg running 4.3.2 to hdisk3, then update to the latest fixes that aremounted from another system on /433fixes, and run a customized script named/tmp/finish_alt_install, run the following command:

alt_disk_install –C –b update_all –l /433fixes \

–s /tmp/finish_alt_install hdisk3

In SMIT, use the smit alt_clone fast path and select hdisk3 from the listing for TargetDisk(s) to install, select the update_all bundle from the listings in the Bundle to Installfield, type /433fixes in the Directory or Device with images field, and type/tmp/finish_alt_install in the Customization script field.

3. To install an AIX 5.2 mksysb tape that was created from a machine with the samehardware configuration as the target, to hdisk1, run the following command:

alt_disk_install –d /dev/rmt0 hdisk1

In SMIT, use the smit alt_mksysb fast path and select hdisk1 from the listing for TargetDisk(s) to install field and select /dev/rmt0 from the listing for Device or image namefield.

4. To install an AIX 5.2 mksysb image that is NFS mounted on file system /mksysbs to thealternate disk hdisk2 using a customized image.data file and an exclude filecontaining ^./tmp/, type the following command:

alt_disk_install –d /mksysbs/my_52_mksysb –i /mksysbs/my_52_image.data \

–e /mksysbs/my_exclude_file hdisk2

Using the ^./tmp/ pattern does not backup files in the /tmp directory, but does backupfiles in the /var/tmp directory.

Note: All files are backed up relative to the current directory. This directory isrepresented by a. (dot character). If it is important that the search match the string atthe beginning of the line when excluding a file or directory, it is necessary to use a ^.(caret followed by a dot character) as the first part of the search string, followed bythe filename or directory to be excluded. The form is as follows:

^./ filename

If the file name or directory being excluded is a substring of another file name ordirectory, use a ^. (caret followed by a dot character) for the search to start at thebeginning of the line and the $ (dollar symbol) to have the search finish at the end ofthe line.

In SMIT, use the smit alt_mksysb fast path and select hdisk2 in the Target Disk(s) toinstall field. Next, type /mksysbs/my_52_mksysb in the Device or image name field,/mksysbs/my_52_image.data in the image.data file field, and/mksysbs/my_exclude_file in the Exclude list field.

5. To ”wake–up” an original rootvg, after booting from the new alternate disk, run thefollowing command:

alt_disk_install –W hdisk0

The following example illustrates the output that might display when running thecommand discussed above:

# lspv

hdisk0 000040445043d9f3 old_rootvg

hdisk1 00076443210a72ea rootvg

# alt_disk_install –W hdisk0

# lspv

hdisk0 000040445043d9f3 altinst_rootvg


At this point, the altinst_rootvg volume group is varied–on and the /alt_inst file systemsare mounted.


6. To ”put–to–sleep” a volume group that had experienced a ”wake–up,” type the followingcommand:

alt_disk_install –S

The following example illustrates the output that might display when running thecommand previously discussed:

# lspv



# alt_disk_install –S

# lspv



The altinst_rootvg is no longer varied on and the /alt_inst file systems are no longermounted. If necessary for the altinst_rootvg volume group name to be changed back toold_rootvg, do this task with the –v flag.


16-1Software Product Packaging Concepts

Chapter 16. Software Product Packaging Concepts

This chapter discusses concepts regarding additional software product packaging. Thischapter includes information on the following topics:

• Software Package Formats on page 16-1

• Fileset Installation Packaging on page 16-2

• Creating Software Packages on page 16-2

• Bundle Packaging on page 16-3

Software Package FormatsBeginning in AIX 5.1, you can install RPM Package Manager (RPM) and InstallShieldMutliPlatform (ISMP) formatted packages in addition to installp formatted packages. Usethe Web–based System Manager, SMIT, or the geninstall command to install and uninstallthese types of packages. The geninstall command can detect the format type of a specifiedpackage and run the appropriate installation command.

Beginning in AIX 5.1, the AIX product media contains installp packages and RPMpackages that are installed during a base operating system (BOS) installation. The installppackages are located in the following path:

/ mount_point /installp/ppc

The RPM packages are located in the following path:

/ mount_point /RPMS/ppc

If you have media that contains ISMP packages for AIX 5.1 and later, the ISMP packagesare located in the following path:

/ mount_point /ISMP/ppc

If you are using the geninstall command to install RPM or ISMP packages, use the prefixtype to indicate to the geninstall command the type of package that you are installing. InAIX 5.1, the package prefix types are the following:

I: installp format

R: RPM format

J: ISMP format

For example, to install the cdrecord RPM package and the bos.games installp package,type the following:

# geninstall –d/dev/cd0 R:cdrecord I:bos.games

The geninstall command detects that the cdrecord package is an RPM package type andruns the rpm command to install the cdrecord package. The geninstall command thendetects that bos.games is an installp package type and runs the installp command toinstall the bos.games package. The process for uninstallation is similar to the installationprocess.

In Web-based System Manager and SMIT, if you are selecting the packages from asoftware list, you need not specify the prefix type.


Fileset Installation PackagingThe installation packaging of each fileset in a product can be divided into three parts. Theseparts include the usr, root, and share parts. Although this can add further complexity to theunderstanding of the packaging, this parceling of a software product is necessary for theproduct to be used by diskless and dataless clients in AIX 5.1 and later. Because they areparceled, a product can be installed on one machine (called the server) and then be usedremotely by other machines on a network (called the clients).

Note: The usr and root parts of a product are packaged in the same installable package.

usr part The usr part of a software product contains the part of the product thatcan be shared by machines that have the same hardware architecture.Most of the software that is part of a product usually falls into thiscategory.

In a standard system, the usr parts of products are stored in the /usrfile tree. For example, the ls command would be in the /usr/bin/ls file.

root part Every product has a usr part. The root part of a software productcontains the part of the product that cannot be shared. The root part ofa product is optional because many products may not have any filesthat need to be specific to each individual machine.

In a client/server environment, these are the files for which there mustbe a unique copy for each client of a server. Most of the root softwareis associated with the configuration of the machine or product.

In a standard system, the root parts of a product are stored in the root(/) file tree. The /etc/objrepos directory contains the root part of aninstallable software product’s vital product data (VPD).

share part The share part of a software product contains the part of the productthat can be shared among machines, even if they have differenthardware architectures, which can include nonexecutable text or datafiles. For example, the share part of a product might containdocumentation written in ASCII text or data files containing specialfonts.

The share part of a product is optional because many products mightnot have any files that can be shared among different hardwareplatforms. The share part of a product is always packaged in aseparately installable package.

In a standard system, the share parts of products are usually stored inthe /usr/share file tree. For example, a dictionary database might bestored in the /usr/share/dict/words file.

Creating Software PackagesThe mkinstallp command is a tool that allows users to create their own software packagesfor AIX. Packages created with the mkinstallp command are in installp format and areinstalled or removed with the installp command.

Files to be packaged by the mkinstallp command must be in a directory structure such thatthe location of the file relative to the root build directory is the same as the destination of thefile after installation. For example, if the /usr/bin/ somecommand command is to beinstalled by a mkinstallp package, the somecommand parameter must be in the buildroot/usr/bin directory when the mkinstallp command is invoked.

When the contents of a package are in the correct directory structure, the mkinstallpcommand prompts for basic package data through the command line. This data includes thepackage name, requisites, descriptions of files to be packaged, and more. The mkinstallp

16-3Software Product Packaging Concepts

command then generates a template file based on responses given by the user. To preventcommand line prompting when using a template file, create and edit the template file directlyand use the mkinstallp command with the –T flag.

For example, to package the /usr/bin/foo command using the /tmp/packages directory asthe build root, make sure the following directory structure exists by typing the following atthe command line:

mkdir /tmp/packages

touch /tmp/packages/usr/bin/foo

Then type the following:

mkinstallp –d /tmp/packages

For more examples, refer to the /usr/lpp/bos/README.MKINSTALLP file.

Bundle PackagingThe Web-based System Manager and the SMIT Install application look for bundles in/usr/sys/inst.data/sys_bundles and in /usr/sys/inst.data/user_bundles. Thesys_bundles location is typically reserved for system–defined bundles (those which comewith AIX). Users can create their own bundle files in the user_bundles directory.

The bundle definition file name must end in.bnd, because the AIX installation interfaces thatprocess bundles recognize only bundle files that end in .bnd . Use any editor to createbundle files, which can contain comments and fileset names. Lines beginning with thepound sign (#) are recognized as comments and are ignored by the bundle processingcode. When you have completed your list of filesets, save the file and make sure the file hasthe appropriate read permission. Invoking a bundle installation interface displays yourbundle without the.bnd extension.

The following are examples of the predefined bundles:

• Server Bundle. A collection of software packages for machines running AIX in amultiuser standalone or networked environment. This bundle emphasizes functionalityover disk utilization.

• Graphics Bundle. A collection of software packages that provides support of graphicalenvironments. Graphical support may be automatically installed on some systems duringBOS installation.

• Migration Bundle. This bundle is created when there was not enough disk spaceavailable to complete a migration installation during the BOS installation process. Thebundle consists of a collection of software packages that must be installed to completeyour migration. You must install this bundle to complete the migration installation. Installthe bundle using the smit update_all fast path.

You may also need to install the Graphics Bundle.

Some system bundles might refer to installation images that are spread across multiplemedia. If you see errors indicating that filesets could not be found on the media you areusing, insert the media containing the missing filesets and retry the bundle installation.

The system bundles are located in the /usr/sys/inst.data/sys_bundles directory. To list thesystem bundles, type the following:

ls /usr/sys/inst.data/sys_bundles/*.bnd

You can also use the SMIT list_bundle fast path to list the system bundles.

Beginning in AIX 5L Version 5.2 with the 5200–01 Recommended Maintenance package,the geninstall and gencopy commands handle multiple software sources to be specifiedwhen a bundle file is used. This is accomplished by grouping software images togetherunder #MEDIA= headings in the bundle file. Any images listed under such a heading mustreside on the specified media. Media can be specified as the name of a CD (such as Base


Install Media Volume 1 or AIX Linux Toolbox CD) or as a local directory (such as the/usr/sys/inst.images directory).

The #MEDIA= heading is used to designate the location of the filesets or packages in thebundle. For example, the BaseAndLinuxCD Bundle might contain the following information:

# BaseAndLinuxCDBundle contains packages on volume 1 of base media and on

the AIX

# Linux Toolbox CD

#MEDIA=Base Install Media Volume 1

I:bos.adt.prof

#MEDIA=AIX Linux Toolbox CD

R:mtools

R:vim–common

When the geninstall and gencopy commands prompt for the additional media, they usethe words provided in the #MEDIA= line. In the previous examples, the geninstall and thegencopy commands display a message informing you that the bos.adt.prof installppackage is located on Base Install Media Volume 1, and the mtools and vim–commonRPM packages are located on the AIX Linux Toolbox CD.

The #MEDIA= heading can also be used to indicate a directory. For example, theCD_Directory Bundle might contain the following information:

# CD_DirectoryBundle contains packages on volume 1 of base install media

# and in /usr/sys/inst.images

#MEDIA=/usr/sys/inst.images

I:bos.games

#MEDIA=Base Install Media Volume 1

I:bos.adt.prof

R:cdrecord–1.9–4

This informs the geninstall and the gencopy commands that the bos.games installppackage is located in the /usr/sys/inst.images directory, and the bos.adt.prof installppackage and the cdrecord–1.9–4 RPM package are located on Base Install Media Volume1.

17-1Troubleshooting Operating System and Optional Software Installation

Chapter 17. Troubleshooting Operating System andOptional Software Installation

This chapter provides problem–determination tactics and solutions for installation andconfiguration problems. Topics include:

• Troubleshooting an Installation from a System Backup on page 17-2

• Troubleshooting a Migration Installation on page 17-4

• Troubleshooting an Alternate Disk Installation on page 17-6

• Troubleshooting After an Installation on page 17-7

• Accessing a System That Does Not Boot on page 17-8

• Troubleshooting a Full /usr File System on page 17-11

• Viewing BOS Installation Logs on page 17-12

• Handling System and Error Messages on page 17-13.


Troubleshooting an Installation from a System BackupThis section describes solutions for common problems when installing from a system imagecreated with the mksysb command.

Bootup FailureIf a backup tape fails to boot, you can still install by using a mksysb image stored on thetape.

Boot the machine from the product media (Volume 1 if there is more than one volume), theninstall the backup from Maintenance mode. For instructions on booting, refer to Introductionto Base Operating System Installation. Follow the instructions to the point when theWelcome to the Base Operating System Installation and Maintenance screen displays.

Booting from the Product CD–ROMComplete the following steps when the Welcome screen is displayed:

1. Choose the Start Maintenance Mode for System Recovery option.

2. Choose the Install from a System Backup option.

3. Choose the drive containing the backup tape.

The system reads the tape and begins the installation.

4. Do not remove the CD from the CD–ROM drive.

The system installs the kernel and device support required on the target system from theCD.

5. Return to step 8 on page 14-19 in the Installing a System Backup on the SourceMachine procedure and continue the instructions for installing the backup.

Note: The Use Maps option is not supported in Maintenance Mode. For moreinformation on the maps options in Maintenance Mode, refer to Installing a SystemBackup on the Source Machine on page 14-16.

Problems with mksysb Image Configuration on System Backup TapesBootable mksysb tapes comprise the following images:

• Boot image

• BOS Installation/Maintenance image

• Table of contents image

• System backup image

The system backup image is the actual backup of the files in the rootvg in all JFS–mountedfile systems.

The boot image, BOS Installation/Maintenance image, and the table of contents image mustbe created with a tape block_size value of 512. The mksysb command ensures that theblock size is 512 when these images are created. There are no restrictions on the block sizeused for the fourth (system backup image) on the tape. The block size of the system, beforeit was temporarily set to 512, is used for the fourth image on the tape.

The value of the block size must be saved in the /tapeblksz file in the second image on thetape. The second and fourth images are stored in backup/restore format. Again, mksysbensures the correctness of the tapes created by using the mksysb command.

If there are problems with the bosinst.data file, the image.data file, or the tapeblksz file,these files can be restored from the second image on the tape and checked. These files, as


well as commands necessary for execution in the RAM file system (when running inmaintenance mode after booting from the tape), are stored in the second image.

Restoring a File from the Second Image or TapeTo restore a file from the second image, follow these steps:

1. Be sure the tape block size is 512 by entering the following command:

# lsattr –E –l rmt0

If the block size is not correct, use the following command to set it to 512:

# chdev –l rmt0 –a block_size=512

2. Make sure the tape is rewound. If the tape is not rewound, enter the following command:

# tctl –f /dev/rmt0 rewind

3. Extract the necessary files by entering:

# restore –xvq –s2 –f /dev/rmt0.1 . filename

Note: The filename should be the full path, and always preceded with a . (dotcharacter), such as./tapeblksz.

4. Rewind the tape by entering:

# tctl –f /dev/rmt0 rewind

5. Change the block size back to its original value, if necessary.

Troubleshooting Reported Problems with mksysb Backup InstallationsThe following troubleshooting tips apply to reported problems with installations from amksysb image:

• Check that you have sufficient free blocks in the file systems to write temporary files.

• Check that each file system has at least 500 blocks free when the mksysb backupimage is made. The system needs work space in each file system when installing from amksysb backup image.

• Check that you are using the correct tape type for the density setting that you selected.

• Check that the tape is not write–protected.

• Clean the tape drive at the recommended intervals and use only approved data–gradetapes (not video tapes for 8 mm).

• Check that 7206 4–mm Digital Audio Tape (DAT) tape drives are using only DAT tapesmarked with the Dataphone Digital Services (DDS) symbol. Any other DAT tapes (forexample, voice grade) cannot be used.

• Check the /smit.log file for any errors from SMIT.

• Check that your mksysb backup image contains an image.data file. If you create themksysb backup image through Web-based System Manager or SMIT, it is doneautomatically. If you run mksysb from the command line, you must either run themkszfile command first, or use the –i flag with the mksysb command.


Troubleshooting a Migration InstallationThe following sections offer solutions for problems that can occur during a migrationinstallation.

Boot Logical Volume Not Large EnoughIf you receive errors indicating the boot logical volume is not large enough, see HandlingSystem and Error Messages.

Insufficient Disk Space for MigrationAt the beginning of a migration installation, the system verifies that there will be enoughspace to attempt the migration. If there is not enough disk space, a message explains howmuch is needed. You must now reboot the machine from the media containing your currentversion of AIX, and make more space available in the rootvg volume group. After you dothis, attempt the migration again.

You can use the following options for adding additional disk space for the migrationinstallation:

• Add another disk to the rootvg volume group, using either the SMIT smit extendvg fastpath or the extendvg command.

• Move any user–data logical volumes from the rootvg volume group to another volumegroup. You can use either the SMIT smit cplv fast path or the cplv command to moveindividual logical volumes to another volume group’s disk. It is a good idea to have onlysystem logical volumes in the rootvg, and have user–data logical volumes in othervolume groups.

After you use the cplv command, you must remove the original logical volumes with thermlv command. If the moved logical volume contains a file system, you must modify itscorresponding entries in the /etc/filesystems file to reflect the new logical volume name.

For more detailed information about manipulating logical volumes and volume groups,refer to Logical Volumes in AIX 5L Version 5.2 System Management Guide: OperatingSystem and Devices.

• Remove unneeded logical volumes (and file systems) from the rootvg. Run the lsvg –lrootvg command to see all the logical volumes in the rootvg volume group. The onlylogical volumes that must be in the rootvg are: hd2, hd3, hd4, hd5, hd6, hd8, andhd9var. The hd1 (/home) logical volume can be located in another volume group ifnecessary.

Beginning in AIX 5.1, the hd7 (system dump) logical volume is not needed because thepaging space logical volume ( hd6 ) is used. The migration code automatically removesthis logical volume if space is needed, but you can remove it ahead of time with thefollowing commands:

sysdumpdev –P –p /dev/hd6

rmlv –f hd7

• If you cannot find extra space in your rootvg, you might have to do a preservationinstallation instead of a migration installation to AIX. A preservation installation saves allthe ”non–system” logical volumes and file systems (for example, /home), but removesand re–creates the following logical volumes: hd2, hd3, hd4, hd5 and hd9var.

If you do a preservation installation, you must reinstall any applications that wereinstalled in your rootvg after the preservation installation has completed. You must alsoreconfigure devices, as well as re–create users and groups. For more information abouta preservation installation, see Introduction to Base Operating System Installation onpage 5-1.


After you have released enough space, reboot from your installation media, and try themigration installation again. You must have at least 8 MB of free disk space to complete themigration installation.

If there is insufficient space to complete the migration installation during the BOS installationprocess, a message similar to the following is displayed at the end of the installation:

An error occurred while migrating packages.

Some packages have not been installed.

Please see /var/adm/ras/devinst.log for details or perform an overwrite or

preservation install.

If space limitations prevent the migration of all software that is usually automaticallymigrated, the installation program attempts to install the software that is usually installed fora Preservation or Overwrite installation. If there is still not enough disk space available, theminimum set of software required to support the use of the system is installed.

If there is not enough space to migrate all of the usually migrated software, a collection ofsoftware called a Migration Bundle will be available when you install additional softwarelater. If the minimum set of software is installed, or if the installation is not performed from agraphics console, a Graphics_Startup Bundle is created. Before installing either of thesebundles, create additional disk space on the machine you want to install. For moreinformation about installing software bundles and migrating or installing optional softwareproducts, refer to Optional Software Products and Service Updates on page 12-1.

Maintaining Optional Software Products and Service Updates on page 12-7 describes howto remove software from the system to release disk space.


Troubleshooting an Alternate Disk InstallationIf you receive either of the following error messages, see Handling System and ErrorMessages on page 17-13.

• 0505–113 alt_disk_install: No target disk name provided.

• 0505–117 alt_disk_install: Error restoring image.data file from

mksysb image.

Other ProblemsSymptom: You have run the alt_disk_install command or used the SMIT menus to eitherclone or install a mksysb image on an alternate disk. However, you now want to remove thedefinition so you can use the disk to run the alt_disk_install command again or use thedisk for another purpose.

Action: Do not run the exportvg command. The exportvg examines the logicalvolumes on the disk (now called by their rootvg names: hd1, hd2, hd3, and so on) andtries to remove their corresponding entries from the /etc/filesystems file. This actionremoves the real file system stanzas from your running system and causes bootproblems if you reboot with the missing stanzas.

Use the alt_disk_install –X command to remove the altinst_rootvg name from thedatabase. This removes only the ODM information from the CuDv database, so the lspvcommand shows the disk(s) as no longer belonging to altinst_rootvg. It also resets yourbootlist to the boot disk on which the hd5 boot logical volume resides. You can still bootfrom the altinst_rootvg, because the volume group, logical volume, and file systeminformation remain on the disk. However, you must set your bootlist to thealtinst_rootvg boot disk.


Troubleshooting After an InstallationIf your system was installed by a network installation server, Configuration Assistant orInstallation Assistant will not display when the BOS installation program completes.

Configuration Assistant and Installation Assistant do not contain the tasks needed toconfigure your machine as a server. If you need to configure your system for a specificresource, refer to the documentation pertaining to that resource.

If your terminal type is not set, the first menu displayed by the ASCII Installation Assistantrequires you to enter your terminal type (tty). If you enter a terminal type that is not valid,this menu redisplays until a valid type is entered.

If you enter a valid terminal type that does not match your terminal, the next screendisplayed may be unreadable. In this case, press the break key sequence to return to theSet Terminal Type screen. For most terminal types, the break key sequence is Ctrl–C.


Accessing a System That Does Not Boot

This section describes how to access a system that will not boot from the hard disk. If amksysb backup tape fails to boot, read Troubleshooting an Installation from a SystemBackup on page 17-2 for instructions.

This procedure enables you to get a system prompt so that you can attempt to recover datafrom the system or perform corrective action that will enable the system to boot from thehard disk.

Notes:

1. This procedure is intended only for experienced administrators who have knowledgeof how to boot or recover data from a system that is unable to boot from the harddisk. Most administrators should not attempt this procedure but instead should followlocal problem–reporting procedures.

2. This procedure is not intended for administrators who have just completed a NewInstallation, because the system will not contain data that needs to be recovered. Ifyou are unable to boot from the hard disk after completing a New Installation, followyour local problem–reporting procedures.

The following steps summarize the procedure for accessing a system that will not boot.

1. Boot the system from Volume 1 of the BOS CD–ROM or a bootable tape.

2. Select Maintenance Options.

3. Recover data or perform corrective action using the system prompt.

PrerequisitesBefore continuing with the procedure, confirm the following prerequisites have been met:

• Your system cannot be booted from the hard disk.

• All hardware is installed.

• AIX Base Operating System (BOS) is installed.

• Your system unit is set to Off.

Accessing the System

Use this procedure if you are unable to boot from the hard disk. The beginning of thisprocedure is similar to the one you used to install the Base Operating System. You will,however, use the maintenance screens instead of the installation screens to complete thisprocedure.

1. Turn on all attached external devices, such as terminals, CD–ROM drives, tape drives,monitors, and external disk drives before turning on the system unit. Do not turn on thesystem unit until step 5. Turning on the external devices first is necessary so that thesystem unit can identify them during the startup (boot) process.

– If you are booting from a network device, refer to Appendix A. Network Boot on pageA-1.

– If you are not booting from a network device, go to step 3.

2. Insert Volume 1 of the installation media into the tape or CD–ROM drive. SomeCD–ROM drives have a removable disc caddy, while others have a sliding drawer. If theCD–ROM drive on your system has a sliding drawer, place the CD–ROM in the drawerand push the drawer in. If the CD–ROM drive on your system does not have a sliding


drawer, insert the CD–ROM into the disc caddy and then insert the caddy into theCD–ROM drive.

Notes:

a. You may find that on specific hardware, the tape drive door will not open while thesystem unit is turned off. If you have trouble opening the tape drive door duringinstallation, use the following procedure:

i. Turn the system unit on.

ii. Insert the BOS tape (insert Volume 1 if you received more than one volume).

iii. Turn the system unit off and wait 30 seconds.

b. On some models that have a door to the tape drive, there may be a waiting periodof up to three minutes before the tape drive door opens after you have pressed thebutton to open the tape drive. Some models also require that the button for thetape drive door be held in the pressed position for a few seconds before the tapedrive door will open.

c. On some models, the eject button must be pressed for at least 2 seconds to ejecta CD–ROM that is already in the disc caddy.

3. If you are not using an ASCII terminal, skip to step 5. If you are using an ASCII terminal,set the communications options as follows:

– Line Speed (baud rate) = 9600

– Word Length (bits per character) = 8

– Parity = no (none)

– Number of Stop Bits = 1

– Interface = RS–232C (or RS–422A)

– Line Control = IPRTS Set the keyboard and display options as follows:

– Screen = Normal

– Row and Column = 24x80

– Scroll = jump

– Auto LF (line feed) = off

– Line Wrap = on

– Forcing Insert = line (or both)

– Tab = field

– Operating Mode = echo

– Turnaround Character = CR

– Enter = return

– Return = new line

– New Line = CR

– Send = page

– Insert Character = space

Note: If your terminal is an IBM 3151, 3161, or 3164, press the Ctrl+Setup keys todisplay the Setup Menu and follow the onscreen instructions to set these options. Ifyou are using some other ASCII terminal, refer to the appropriate documentationfor information about how to set these options. Some terminals have differentoption names and settings than those listed here.


4. Turn the system unit power switch to the On position. The system begins booting fromthe installation media. If your system is booting from tape, it is normal for the tape tomove back and forth. After several minutes, c31 is displayed in the LED.

If you have more than one console, each terminal and directly attached display device(or console) might display a screen that directs you to press a key to identify your systemconsole. A different key is specified for each terminal displaying this screen. If thisscreen is displayed, then press the specified key on the device to be used as the systemconsole. The system console is the keyboard and display device used for installation andsystem administration. Press a key on only one console.

5. Type 3 to select Start Maintenance Mode for System Recovery from the Welcome tothe Base Operating System Installation and Maintenance screen when it displays.

Note: If you customized the bosinst.data file in your installation media to specify anonprompted installation, the installation and maintenance screens are not displayed.The system instead reboots from the installation media using the settings alreadydefined in the bosinst.data file. To access the installation and maintenance screens,override the nonprompted mode. You can do this when three zeros are displayed onthe screen. When you observe the three zeros, type 000 (zeros) and press Enter atthe terminal.

You can select 88 to display help on this or any subsequent screen.

After you have selected the Start Maintenance Mode for System Recovery option, theMaintenance screen displays.

6. Select option 1, Access a Root Volume Group, from the Maintenance screen. TheWarning screen displays.

7. Read the information displayed on the Warning screen. When you are ready to continue,type 0 and press Enter. The Access a Root Volume Group screen displays.

8. Select the option for the root volume group whose logical volume information you want todisplay. The Access a Root Volume Group screen lists all of the volume groups (root andotherwise) on your system. After entering your selection, the Volume Group Informationscreen displays.

Note: Reviewing the disk and location code information on the Volume GroupInformation screen enables you to determine whether the volume group you selectedwas the root volume group. You can return to the Access a Root Volume Groupscreen if the choice you made was not the root volume group. If you have not chosena root volume group, you cannot continue beyond the Volume Group Informationscreen.

9. Select one of the options from the Volume Group Information screen and press Enter.Each option does the following:

Choice 1 Access this volume group and start a shell. Selecting thischoice imports and activates the volume group and mounts thefile systems for this root volume group before providing you with ashell and a system prompt.

Choice 2 Access this volume group and start a shell before mountingfile systems. Selecting this choice imports and activates thevolume group and provides you with a shell and system promptbefore mounting the file systems for this root volume group.

Choice 99 Typing 99 returns you to the Access a Root Volume Groupscreen.

After you select either choice 1 or 2, a shell and system prompt display.

10.Take appropriate measures to recover data or take action (such as using the bosbootcommand) to enable the system to boot normally.


Troubleshooting a Full /usr File SystemTo release space in a full /usr file system, complete one or more of the following tasks:

• Type installp –c all to commit all updates and release space in the /usr file system.

• If the system is not a Network Installation Management (NIM) system serving a SharedProduct Object Tree (SPOT), enter /usr/lib/instl/inurid –r to remove clientinformation for root file system installations. For information about NIM and SPOTs, seeSPOT (Shared Product Object Tree) Resource on page 27-28 in the NIM Resourcessection.

• Remove software that you do not need. See Maintaining Optional Software Products andService Updates on page 12-7.


Viewing BOS Installation LogsInformation saved in BOS installation log files may help you determine the cause ofinstallation problems. To view BOS installation log files, type cd /var/adm/ras and viewthe files in this directory. One example is the devinst.log, which is a text file that can beviewed with any text editor or paged.

Viewing Logs with SMITTo view some logs in the /var/adm/ras directory, you can use the following SMIT fast path:

smit alog_show

The resulting list contains all logs that are viewable with the alog command. Select from thelist by pressing the F4 key.

Viewing Logs with the alog CommandTo view some logs in the /var/adm/ras directory, type:

alog –o –f bosinstlog


Handling System and Error MessagesThis section lists messages that can appear during the installation of AIX 5.1 and later.Information about most messages is provided in the following format:

System Message The system message is displayed in bold type.

Explanation Describes what is likely to have caused the system message to bedisplayed.

System Action Describes what the system does after the message is displayed.

User Action Suggests a possible resolution to the problem suggested by thesystem message.

Note: Multiple messages can have the same explanation, system action, and useraction.

0516–404 allocp: Not enough resources available to fulfill allocation. Either notenough free partitions or not enough physical volumes to keep strictness. Try againwith different allocation characteristics.

0516–788: extendlv: Unable to extend logical volume

0503–008 installp: There is not enough free disk space in file system /usr (506935more 512–byte blocks are required.) An attempt to extend this file system wasunsuccessful. Make more space available, then retry this operation.

Explanation There is not enough space to complete the installation.

System Action The installation cannot begin until the problem is resolved.

User Action You have several options:

• Select fewer filesets than the number originally selected forinstallation.

OR

• Extend the root volume group to another disk. Type: extendvgrootvg hdiskNumber, where Number is the number of thespecified disk.

OR

• Remove user–defined file systems to release space in the rootvgfile system.

OR

• Follow the instructions in Troubleshooting a Full /usr File Systemon page 17-11.

BOS Install: After saving all the data from the previous system into /tmp, it wasdiscovered that there will not be enough free space in /tmp to make the boot image.Please reboot in normal mode and increase the size of /tmp or reduce the number offiles to save as listed in the /etc/preserve.list file.


Explanation During a preservation installation, files listedin the /etc/preserve.list file were copied tothe /tmp file. After doing so, there was notenough room in /tmp to create the bootimage.

System Action Installation cannot continue.

User Action Reboot in normal mode and increase thesize of /tmp or reduce the number of files tobe saved.

BOS Install: You chose to create logical volumes mapped exactly as they were on theprevious disks, but there are no map files specified in the image.data file.

Explanation On system backup restore, EXACT_FIT =yes was specified in the image.data file,but no map files were specified in theimage.data file.

System Action Nonprompted mode is terminated. The useris prompted.

User Action Run the mkszfile command with the –moption before creating the system backuptape.

OR

Do not specify EXACT_FIT = yes in theimage.data file.

The boot logical volume ( hd5 ) must be at least 12 MB. The system you are installinghas a boot logical volume smaller than this, and the system does not have enoughfree contiguous physical partitions on diskname to increase the size of the bootlogical volume. Please reboot in normal mode and correct this problem, or restart theinstallation and choose an overwrite install. Use the lspv –M diskname command tosee the current allocation map of the disk.

OR

Error: No space available to create a larger boot logical volume. In order to proceedwith this installation the size of the boot logical volume ( hd5 ) must be increased to12 MB. At this time there are not N contiguous physical partitions available on theboot disk ( diskname ) for recreating the larger boot logical volume. You must free upthis space by removing or relocating one or more logical volumes or file systemsfrom diskname. Use lspv –M diskname to see its current partition allocation map.


Explanation Starting with AIX 5.2, the boot logical volume (blv), logical volumehd5, must be greater than 12 megabytes. If your system had disksless than 4 gigabytes in size in the root volume group, or wasoriginally installed with a version of AIX earlier than AIX 4.3.2 yourboot logical volume may only be 4 megabytes. You might experiencethis failure during preservation or migration installations. Overwriteinstallations create the boot logical volume with a minimum size of12 megabytes. If free partitions contiguous to hd5 are available or ifanother location on the disk contains hd5 is identified, theinstallation process increases the size of hd5 and continues. Onlythe disk that currently contains the boot logical volume is checked foradditional partitions in order to increase the size of the boot logicalvolume. Other disks in the rootvg are not checked.

System Action You will be prompted to reboot in normal mode from the existingrootvg and increase the boot logical volume, or restart the installationand choose an overwrite install.

User Action Only a system administrator with root authority should attempt toincrease the boot logical volume. To increase the boot logicalvolume, follow the process described below:

If you received this error, then your partition size is less than 8megabytes, and you must increase the number of partitions in hd5(boot logical volume). You can check your partition size as follows:


# lsvg rootvg

2. Look for the field: PP SIZE:

3. Obtain the current number of partitions in hd5, as follows:

# lslv hd5

4. Look for the field: LPs:

5. Your boot logical volume must contain enough partitions suchthat:

– PP SIZE multiplied by LPs is greater than or equal to 8.

– The partitions for the boot logical volume must be contiguous.

If there were free partitions available next to hd5 or at some otherlocation on the disk that contains hd5, the installation process wouldhave increased the size of hd5, and continued.

To view the current allocation map (free and used partitions) of adisk, use the command:

# lspv –M diskname


User Action,continued

If there are not enough contiguous free partitions, you must increasethe size of the boot logical volume ( hd5 ) using one of the optionsdescribed below, and rerun the installation. The options forincreasing the boot logical volume size are as follows:

• If a user–created logical volume or file system follows hd5 on thedisk (check the allocation map), and has free partitions, you canback up, remove, re–create, and restore the logical volume.

• If there is another disk in the rootvg, that has enough contiguousfree partitions, then you could move hd5 to the other disk withthe following steps:

1. Verify that the disk you plan to move hd5 to is bootable by usingthe command:

bosinfo –B diskname

. If 1 is returned, the disk is bootable.

. If 0 is returned, the disk is not bootable.

2. Find the free contiguous partitions you need on the other disk byviewing the allocation map with the command:

lspv –M diskname

3. Create a map file to use when re–creating hd5. For example, ifyou want to re–create hd5 on hdisk2, on partitions 88 and 89,use the command:

echo ”hdisk2:88–89” > your_MAP_file

4. Remove the existing hd5:

rmlv –f hd5

5. Create the new hd5:

mklv –y hd5 –t boot –m your_MAP_file rootvg 2

The 2 represents the number of partitions and can vary asneeded.

Note: If the mklv command moves hd5 to a new location,you must run the following command:

echo ”: C : C : C ” |

/usr/lpp/bosinst/blvset –d /dev/ hdiskN

Where C is the message, locale, and keyboard (respectively)and hdiskN is the disk that contains hd5.

6. Run the mkboot command to clear the boot record from the diskthat previously contained hd5 (boot logical volume). Forexample, if hd5 was previously on hdisk0, use the command:

mkboot –d /dev/hdisk0 –c

7. Use the bosboot command to re–create the boot image andboot record on the new disk. For example, if hd5 wasre–created on hdisk2, use the command:

bosboot –a –d /dev/hdisk2


User Action,continued

8. Change the bootlist of your system to boot from the new disk. Tosee the current bootlist, use the command:

bootlist –m normal –o

OR

If your previous hd5 was on hdisk0, the output might be:

hdisk0

To change the bootlist to use hdisk2, use the command:

bootlist –m normal hdisk2

If there were additional items in your bootlist, add them afterhdisk2, with spaces separating each item.

9. If there were no errors, reboot your system.

10.If you encountered this error when installing a mksysb on asystem other than the system it was created on (cloning), thenyou might be able to use a customized image.data file toincrease the size of hd5.

The vg_data stanza contains the size of the physical partitions inthe PPSIZE field. Use this information to determine how manypartitions are needed for hd5. The lv_data stanza for hd5contains the fields for the number of logical partitions ( LPs ), thenumber of physical partitions ( PP ), and the minimum number oflogical partitions required for the logical volume ( LV_MIN_LPS ).These fields must be set to the number of partitions needed.

See Create and Use a Supplementary Diskette on page 10-3 forinformation on putting an image.data file on diskette and abosinst.data file.

If the source machine had no free partitions, and the targetmachine has the same disk size, then you might need to installusing the shrink option, as well as the customized image.data file.

BOS Install: Could not create boot image.

Explanation The bosboot command failed.

System Action The boot image was not created.

User Action Check the /var/adm/ras/bosinst.log file for errors (alog –o –fbosinst.log | pg). This log is updated by appending, so make sureyou check the last entry.

The bosinst.data file does not specify any bootable disks.

Explanation The bosinst.data file does not specify any bootable disks.

System Action Nonprompted mode is terminated. The user is prompted.

User Action When the system prompts, select bootable disks to install on.

OR

Add a bootable disk to the bosinst.data file target_disk_datastanzas.

The bosinst.data file specified doing a migration install, but there is no existing rootvolume group of level 4.2, 4.3, or 5.1.


Explanation A BOS installation method of migration was specified in thebosinst.data file, but the existing volume group is at level 3.1 or 5.2.

System Action This error only occurs during a nonprompted BOS installation. Theinstallation menus are displayed.

User Action Respond to the menu prompts to complete the installation.

The bosinst.data file specified doing either a migration or a preservation install, butthere is no existing root volume group.

Explanation A BOS installation method of migrate or preserve was specified inthe bosinst.data file, but no root volume group was found.

System Action This error only occurs during a nonprompted BOS installation. Theinstallation menus are displayed.

User Action Respond to the menu prompts to complete the installation.

The data file did not specify enough disk space to contain the operating system.

Explanation Nonprompted mode was specified, and there were not enough disksspecified in the bosinst.data file to hold the operating system.


User Action When the system prompts, select disks to install on.

OR

Add more target_disk_data stanzas to bosinst.data file.

Duplicate lv_data stanzas specified in the image.data file. The installation cannotcontinue because data may be lost.

Explanation An lv_data stanza was duplicated in the image.data file.


User Action Correct the problem and try the installation again.

Duplicate fs_data stanzas specified in the image.data file. The installation cannotcontinue because data may be lost.

Explanation An fs_data stanza was duplicated in the image.data file.


User Action Correct the problem and try the installation again.

The following disks failed the preliminary diagnostic tests: <disk name>

bosset: No hard disks can be accessed.

Explanation The listed disks failed pretest.

System Action The system initiated a diagnostic pretest on the specified disk.

User Action Run full diagnostics on the specified disks.

Disks specified in bosinst.data do not define a root volume group.


Explanation Nonprompted mode was specified. The install method was set topreserve or migrate, and the disks specified in bosinst.data do notdefine a root volume group.


User Action When the system prompts, select a root volume group to install on.

OR

Specify disks in the bosinst.data file that define a root volumegroup.

Encountered an unrecoverable error.

Explanation The menus subsystem encountered an unrecoverable error.

System Action The menu is restarted.

User Action None

The image.data file contains no vg_data stanza for rootvg. The installation cannotcontinue.

Explanation The image.data file is incomplete.


User Action Use the default image.data file supplied with product media.

image.data has invalid logical volume data. Cannot continue.

Explanation The system could not parse the logical volume data stanzas in theimage.data file.



image.data has invalid file system data. Cannot continue.

Explanation The system detected invalid file system data stanzas in theimage.data file.



0516–366 putlvodm: Volume group rootvg is locked. Try again.

0516–788: extendlv: Unable to extend logical volume.

Explanation You interrupted the installation of your optional software.

System Action When an installation is interrupted, the system sometimes locks theroot volume group.

User Action Unlock the root volume group. Then attempt the installationprocedure again.

To unlock a root volume group:

1. Log in with root authority.

2. Type chvg –u rootvg

3. Type smit_install and attempt to install your optionalsoftware products again.

installp: An error occurred during bosboot processing.


Please correct the problem and rerun.

0301–52 bosboot: not enough file space to create: /tmp/disk.image.

OR

0301–152 bosboot: not enough file space to create: /tmp/unix.

Explanation The bosboot command was unable to finish processing because ofinsufficient space in /tmp.

System Action The bosboot process is interrupted. The error message, the amountof disk space required, and the available disk space are displayed.The disk space displayed indicates the number of 1024 KB blocksrequired.

User Action Release space in the /tmp file system or extend the /tmp file system.Continue or restart the installation process.

To resize the /tmp file system and complete the installation, do thefollowing:

1. Note the error message preceding this one. Either the messagebosboot verification starting or bosboot processstarting will precede this message.

2. Change directories to /tmp. List the files and determine whichfiles can be deleted. If there is sufficient space available, go tostep 6. If you need to expand the /tmp file system, continue withthis procedure.

3. Type smit chfs

4. Select the /tmp file system from the displayed list.

5. Add the additional block space required. The smit chfscommand requires disk space to be defined in 512–KB blocks.Double the required disk space displayed in the systemmessage.

6. If the message installp: An error occurred duringbosboot processing was displayed after the messagebosboot verification starting, rerun the installationprocedure.

OR

If the message installp: An error occurred duringbosboot processing was displayed after the messagebosboot process starting, enter installp –C.

7. Continue the installation process.

installp: An error occurred during bosboot processing.

Please correct the problem and rerun.

301–155 bosboot: Invalid or no boot device specified.


Explanation A device specified with the bosboot –d command is not valid. Thebosboot command was unable to finish processing because it couldnot locate the required boot device. The installp command calls thebosboot command with /dev/ipldevice. If this error does occur, it isprobably because /dev/ipldevice does not exist. /dev/ipldevice is alink to the boot disk.

System Action The bosboot process is interrupted.

User Action Determine if the link to the boot device is missing or incorrect,correct the error and complete the installation process.

To identify the boot device and complete the installation:

1. To identify the boot disk, enter lslv –m hd5. The boot diskname displays.

2. Create a link between the boot device indicated and the/dev/ipldevice file. Enter:

ln /dev/ boot_device_name /dev/ipldevice

(An example of boot_device_name is rhdisk0.)

3. If the message installp: An error occurred duringbosboot processing was displayed after the messagebosboot verification starting, rerun the installationprocedure.

OR

If the message installp: An error occurred duringbosboot processing was displayed after the messagebosboot process starting, enter installp –C. Continuethe installation process.

Missing image.data file. The tape does not contain a valid install image.

Explanation The system could not find an image.data file.


User Action The most likely cause of this error is the tape is bad. Try a differenttape.

0512–0016 mksysb: Attempt to create a bootable tape failed: bosboot –d /dev/device–a failed with return code xxx.

OR

0512–0016 mksysb: Attempt to create a bootable tape failed: mkinsttape /dev/devicefailed with return code xxx.


Explanation The xxx return code indicates the error:

5 OR 1

Not enough space in one or more of three file systems:

. / must have at least 500 1KB blocks.

. /tmp must have at least 7400 1KB blocks.

. /usr must have at least 4000 1KB blocks.

11 Defective tape.

42 OR 45

Either the /usr/lib/boot/unix file is corrupted (may be 0 length) orthe link to /unix is missing.

48

Cannot write to the tape drive or cannot read /dev/blv. This isprobably caused by an incorrect density setting for the tape drive.It could also be caused by either a hardware problem with the tapedrive or by dirty heads on the drive.

System Action The mksysb command failed to make a bootable tape.

User Action The return code xxx indicates the action required:

5 OR 1

Check the /, /tmp, and /usr file systems and create more space asrequired.

11

Replace the defective tape.

42 OR 45

Either restore the /usr/lib/boot/unix file from the original tape orcreate the missing link.

48

Check the tape drive settings and clean the heads.

There are no disks available on this system.


Explanation No hard disks are configured on the system. Consequently, the onlyfunctioning menu option is the maintenance option.

System Action Installation cannot begin until the problem is resolved.

User Action You have several options:

• Select Maintenance (option 3) from the Welcome to BaseOperating System Install Menu, and select the Limited FunctionMaintenance Shell. Verify that no disks were configured byentering the following command:

lsdev –Cc disk

To determine if there were configuration errors, enter thecommand:

cfgmgr –v 2>1 | tee /tmp/cfgmgr.out

You can use the cat command to view the /tmp/cfgmgr.out file,and look specifically for errors in configuration of disks. The filecan be copied to diskette media using either the dd or paxcommands, and moved to a running system for ease of viewing.

OR

• Turn off the system and check the following on systems withSCSI devices:

– Check all SCSI devices to ensure that all SCSI addresses areunique.

– Make sure the SCSI cards are properly terminated.

– If external SCSI devices are in use, make sure that the SCSIchain is terminated and that the devices are turned on.

– Check the SCSI cabling and connections.

– Reboot and attempt the installation again.

OR

• Turn off the system and check the following on systems with IDEdevices:

– Check all IDE devices to ensure that all IDE master and slavesettings are unique per controller. If only one IDE device isconnected to a controller, it must be set to master. If an ATAdevice (disk) and an ATAPI device (CD–ROM or tape) areconnected to the same controller, the ATA device must be set tothe master device and the ATAPI device must be set as the slavedevice.

– Check the IDE cabling and connections.

– Reboot and attempt the installation again.

OR

• Boot from the diagnostics and check the hard disks.

OR

• Follow your local problem–reporting procedures.

There are no disks on this system which can be booted.


Explanation The system could not find any bootable disks on the system.


User Action Some third–party disks are not bootable. If a disk should be bootablebut is not, run diagnostics.

You chose to install only onto disks in the existing root volume group and those notin any volume group. There are not enough of those disks to contain the mksysbimage.

Explanation The EXISTING_SYSTEM_OVERWRITE field in bosinst.data wasset to yes, and prompt was set to no, and there were not enoughdisks on the system that contained the root volume group orcontained no volume group.


User Action Use target_disk_data stanzas to specify the disks to install on, setSHRINK to yes in the image.data file, or at the BOS Install promptset the EXISTING_SYSTEM_OVERWRITE in the bosinst.data fileto any. This allows any disks to be used for the installation.

Attention: If EXISTING_SYSTEM_OVERWRITE is set to any,user volume groups might be overwritten.

OR

When the system prompts, select disks on which to install or selectto shrink the file systems.

You chose to install only onto disks which are not contained in a volume group, butthere are not enough of those disks to contain the mksysb image.

Explanation The EXISTING_SYSTEM_OVERWRITE field in bosinst.data wasset to no, and prompt was set to no, and there were not enoughdisks on the system that contained a volume group.


User Action If you want the system to select the disk to install on, use thetarget_disk_data stanzas to specify the target disks and set theappropriate setting for EXISTING_SYSTEM_OVERWRITE, leaveEXISTING_SYSTEM_OVERWRITE blank in the bosinst.data file, orset SHRINK to yes in the image.data file and retry the installation.

OR

When the system prompts, select disks on which to install.

0505–113 alt_disk_install: No target disk name provided.

Explanation This message is displayed in the following situations:

• You did not enter a target disk.

• The disk that was specified as the target disk has a volume groupalready associated with it. Running the lspv command shouldshow the word None by disks that do not have a volume groupassociated with them, which is what the alt_disk_installcommand checks.

• The target disk (or disks) specified are not bootable. Thealt_disk_install command runs bootinfo –B disk_name on eachdisk specified in the target disk list. If any one bootinfo –Bcommand returns a 0 , then the disk is not bootable, and it cannotbe used as a target disk for the alt_disk_install operation.


0505–117 alt_disk_install: Error restoring image.data file from mksysb image.

Explanation This message is displayed when you are trying to install a mksysbimage from tape.

The alt_disk_install command first checks the second image on thetape for a./tapeblksz file, which contains the block size in which themksysb image was created. The mksysb command creates this fileand puts it in the second image on the tape. The first three images ofa mksysb tape are always created at a 512–byte block size. Themksysb image (the fourth image on the tape) can be created atanother block size.

If the alt_disk_install command cannot restore the./tapeblksz filefrom the second image, the block size will remain what it was whenthe alt_disk_install command was started. It will attempt to restorethe./image.data file from the mksysb image. If this block size doesnot match the block size in which the mksysb image was created,the restore fails, and the alt_disk_install command produces thiserror.


18-1Network Installation

Chapter 18. Network Installation

Part 3 provides information about installing and configuring AIX in a networked environmentusing the Network Installation Management (NIM) environment.


19-1Network Installation Management Introduction

Chapter 19. What’s New in Network InstallationManagement (NIM)?

This chapter provides an overview of the new features in the Network InstallationManagement (NIM) interface for AIX 5.2.

Working with EZNIMThe SMIT EZNIM menu helps the system administrator by organizing the commonly usedNIM operations and simplifies frequently used advanced NIM operations.

Features of SMIT EZNIM include:

• Task–oriented menus

• Automatic resource naming that includes the level of the software used to create NIMresources.

• The user can review what steps will take place before executing a task, wheneverpossible.

For information about EZNIM, see EZNIM.

Creating Resources SimultaneouslyPreviously, when NIM ran a process that calculated and consumed file system space, suchas creating a SPOT, lpp_source and mksysb resource, it would lock a server for theduration of the process. Because these operations calculate free space and enlarge the sizeof a file system, NIM limited servers to one of these operations at a time. Other operationscould occur on the locked server that did not interfere with the operation that was calculatingfree space and enlarging a file system.

Beginning in AIX 5.2, you can use NIM to simultaneously create multiple lpp_source andmksysb resources in separate file systems on the same server. You cannot simultaneouslycreate multiple SPOT resources, but you can simultaneously create a SPOT, lpp_source,and mksysb resource. The locking mechanism is set for each file system instead of foreach server.

However, if you know that you have enough space in a file system to create multipleresources simultaneously, you can use the force option (–F flag) to prevent the lockingmechanism from being used. This allows you to create multiple resources simultaneously inthe same file system.

LPP Source EnhancementsEnhancements to the management of lpp_source resources include the following:

• The lpp_source resource is no longer a required for mksysb installations.

• The update operation, which allows you to update an lpp_source resource by addingand removing packages. Previously, you could copy packages into an lpp_sourcedirectory or remove packages from an lpp_source directory and run nim –o check toupdate the lpp_source attributes. Previously, SMIT allowed you to add packages to alpp_source through the smit nim_bffcreate fast path. However, this SMIT function


does not check to see if the lpp_source is allocated or locked, nor does it update thesimages attribute when finished.

The update operation has been created to address this situation. For more information,see update.

• The lppmgr operation is available to help you manage your lpp_source resources. Thelppmgr operation is available through the command line and through SMIT. For moreinformation, see lppmgr.

Resource GroupsResource groups allow you to create a group of resources and specify clients (or a group ofclients) as defaults. Previously, every time a NIM operation occurred, the NIM resources hadto be specified. A default resource group can be created containing the required resources,so when a NIM operation is performed, the resources are already associasted to the clientby the default resource group.

NIM CommandsThe following NIM commands have been added to AIX:

• The nim_master_setup command. For further information, see Network InstallationManagement Commands Reference.

• The nim_clients_setup command. For further information, see Network InstallationManagement Commands Reference.

20-1Network Installation Management Introduction

Chapter 20. Network Installation ManagementIntroduction

This chapter provides an introduction to AIX Network Installation Management (NIM) andthe operations you can perform to manage the installation of the Base Operating System(BOS) and optional software on one or more machines.

The types of machines you can manage are standalone, diskless, and dataless. Astandalone machine is one that can boot (start up) by itself. Diskless and dataless systemscannot boot by themselves. They must use remote resources to boot. Diskless systemshave no disk drive. Dataless systems have a local disk drive but they cannot boot from it.This section provides concepts and procedures for setting up the NIM environment, initiatingthe installation of standalone machines, and initializing resources for diskless and datalessmachines.

Using NIM, you can install a group of machines with a common configuration or customizean installation for the specific needs of a given machine. The number of machines you caninstall simultaneously depends on the throughput of your network, the disk accessthroughput of the installation servers, and the platform type of your servers.

The NIM environment comprises client and server machines. A server provides resources(for example, files and programs required for installation) to another machine. A machinethat is dependent on a server to provide resources is known as a client. In this guide andreference, any machine that receives NIM resources is a client, although the same machinecan also be a server in the overall network environment.

All operations on clients in the NIM environment require one or more resources. NIMresource objects represent files and directories that are used to support some type of NIMoperation. Because NIM resources are ordinary file system objects in the AIX operatingsystem, most of them are provided to clients with standard Network File System (NFS)software. This means that many resources must reside locally on the servers providingthese resources, because NFS can only export file system objects that are stored on localmedia in the machines from which they are exported.

Most installation tasks in the NIM environment are performed from one server, called themaster. A set of installation tasks can also be performed from NIM clients. Once the networkinstallation setup is complete, users of standalone clients can, from the client, installsoftware that is available on NIM servers.

The machines you want to manage in the NIM environment, their resources, and thenetworks through which the machines communicate are all represented as objects within acentral database that resides on the master. Network objects and their attributes reflect thephysical characteristics of the network environment. This information does not affect therunning of a physical network but is used internally by NIM for configuration information.

Each object in the NIM environment has a unique name that you specify when the object isdefined. The NIM name is independent of any of the physical characteristics of the object itidentifies and is only used for NIM operations. The benefit of unique names is that anoperation can be performed using the NIM name without having to specify which physicalattribute should be used. NIM determines which object attributes to use. For example, toeasily identify NIM clients, the host name of the system can be used as the NIM objectname, but these names are independent of each other. When an operation is performed ona machine, the NIM name is used, and all other data for the machine (including the hostname) is retrieved from the NIM database.


For more information about NIM concepts, see Network Installation Management Conceptson page 27-1. For information on a particular NIM task, refer to NIM Task Roadmap on page21-1.

21-1NIM Task Roadmap

Chapter 21. NIM Task Roadmap

The NIM Task Roadmap provides an overview of NIM configuration tasks and installationtasks and where they can be found in this guide. Also provided is a brief description of thetask. Where appropriate, the SMIT fast path is provided.

Table 4. NIM Task Roadmap

NIM Task SMIT Fast Path Description

EZNIM on page 22-1 smit eznim Configure the NIMenviroment using EZNIM.Allows you to configure yoursystem as a NIM master ora NIM client. If you configureyour system as a NIMmaster, EZNIM also createsthe minimum basicinstallation resources.

Configuring the NIM Masterand Creating BasicInstallation Resources onpage 23-3

smit nim_config_env Configure the NIM master,create the minimum basicinstallation resourcesrequired to install NIM clientmachines, and manage theresources for diskless anddataless clients.

Adding a Standalone NIMClient to the NIMEnvironment on page 23-6

smit nim_mkmac Describes how to addstandalone clients to theNIM environment.

Using Installation Images toInstall the Base OperatingSystem (BOS) on a NIMClient on page 23-10

smit nim_bosinst Describes how to perform aBOS installation on a NIMclient.

Using a mksysb Image toInstall the Base OperatingSystem (BOS) on a NIMClient (mksysb Installation)on page 23-12

smit nim_bosinst Describes how to restore amksysb image andadditional software to atarget NIM client from amksysb resource in the NIMenvironment.

Performing a NonpromptedBOS Installation on page23-15

• smit nim_mkres

• smit nim_bosinst

Provides information abouthow to perform anonprompted NIM BOSinstallation using abosinst_data resource.

Installing to Clients on ATMNetworks on page 23-17

Provides information abouthow to configure NIM towork with ATM adapters.


Customizing NIM Clientsand SPOT Resources onpage 23-19

smit nim_task_inst Describes how to use NIM toinstall software packages,updates, and maintenancelevels on running,configured NIM clients andSPOT resources.

Remove Installed Softwarefrom a NIM Client or a SPOTResource.

smit nim_remove From the NIM master, youcan uninstall software thatresides on client machines.NIM also gives you thecapability of committing andrejecting updates over thenetwork.

Perform MaintenanceOperations on NIM ClientMachines

smit nim_mac_op Hardware diagnostics canbe performed on NIM clientsusing a diagnostic bootimage from a NIM server,rather than booting from adiagnostic tape or CD–ROM.Not only does this eliminatethe need for diagnostic bootmedia, it eliminates the needto have diagnostics installedon the local disks ofmachines.

For maintenance operations,you can boot a NIM clientinto maintenance mode fromthe boot image on a NIMserver instead of using abootable tape or CD–ROM.

Perform MaintenanceOperations on NIMResources

smit nim_res Allows you to list NIMresources; changecharacteristics of aresource; show the contentsof a resource; and verifyresources.

Software Maintenance andUtilities

smit nim_task_maint Provides information abouthow to commit, reject,remove, copy, verify, andclean up software.

Adding a Diskless orDataless Client to the NIMEnvironment on page 23-24

smit nim_task_dd Provides information abouthow to add diskless anddataless systems to yourNIM environment. You canalso manage resources fordiskless and dataless clientsfrom the NIM master.

21-3NIM Task Roadmap

Installing to an AlternateDisk on a NIM Client(cloning or mksysb) on page23-29

smit nim_alt_install NIM can be used to clonethe running of rootvg (rootvolume group) to analternate disk, or install amksysb image to analternate disk.

Alternate Disk MigrationInstallation on page 15-4

smit nimadm NIM can be used to performan alternate disk migrationinstallation to a NIM client.


22-1EZNIM

Chapter 22. EZNIM

The SMIT EZNIM feature helps the system administrator by organizing the commonly usedNIM operations and simplifies frequently used advanced NIM operations.

Features of SMIT EZNIM include:

• Task–oriented menus

• Automatic resource naming that includes the level of the software used to create NIMresources.

• The user can review what steps will take place before executing a task, wheneverpossible.

Use the SMIT eznim fast path to open the EZNIM main menu. If the NIM environment hasnot been set up on your system, the EZNIM main menu displays the following options:

• Configure as a NIM Master

• Configure as a NIM Client

EZNIM Master OperationsIf you select Configure as a NIM Master, the following options display:

Setup the NIM Master environment

Add fixes to the NIM Master environment

Add client to the NIM environment

Update clients

Backup a client

Reinstall clients

Reset clients

Show the NIM environment

Verify the NIM environment

Remove NIM environment

• To configure your current system as a NIM master, select Setup the NIM Masterenvironment. You can select the software source to configure from, select the volumegroup to use for the NIM resources, and select the file system to use for the NIMresources. When the NIM master environment is configured, the basic NIM resourcesare created. To view the NIM resources created by EZNIM, select Show the NIMenvironment, or run the lsnim command on the NIM master.

• To install updates and maintenance level packages to the NIM master, select Add fixesto the NIM Master environment. This option performs an update installation of aspecified set of fixes onto the default SPOT resource. A second SPOT resourcecontaining the newly installed fixes is created by this operation. You can optionally selectto update all your NIM clients during this operation.

• To update a client using EZNIM, select Update clients. The Update clients option allowsyou to perform an update_all operation on a selected client (or clients) using anlpp_source resource.

• To back up a client using EZNIM, select Backup a client. The Backup a client optionallows you to create a system backup image of a selected client and store the backupimage on the NIM master.


• To reinstall a client using EZNIM, select Reinstall clients. The Reinstall clients optionperforms a mksysb restore on a selected client (or clients). You must select a systembackup image to restore, and decide whether to reboot and install the client now.

• To reset a NIM client to the ready state, select Reset clients. This option resets the stateof a client or clients in the NIM environment. Use this option after a NIM operation hasfailed, and you want to return the client to the ready state.

EZNIM Client OperationsEZNIM also allows you to manage a NIM client. On a client system, use the SMIT eznimfast path. Select Configure as a NIM Client, and the following options display:

Add this system to a NIM environment

Update this system

Reinstall this system

Reset this system

• To define your client in the NIM environment, select Add this system to a NIMenvironment.

• To update your client, select Update this system. This option allows you to perform anupdate_all operation on your client using an lpp_source resource.

• To reinstall your client, select Reinstall this system. This option performs a mksysbrestore on the client. You must select a system backup image to restore, and decidewhether to reboot and install the client now.

• To reset your client in the NIM environment, select Reset this system. This optionresets the state of the client in the NIM environment. Use this option after a NIMoperation has failed, and you want to return the client to the ready state.

23-1Basic NIM Operations and Configuration

Chapter 23. Basic NIM Operations and Configuration

Note: AIX 5.2 provides the cdromd CD and DVD automount facility, which isincluded in the bos.cdmount fileset. To determine if the cdromd daemon isenabled on your system, run the following command:

# lssrc –s cdromd

The cdromd daemon can interfere with scripts, applications, or instructions thatattempt to mount the CD or DVD device without first checking to see if the device isalready enabled. A resource or device busy error occurs in such a condition. Use the cdumount or cdeject command to unmount the device. Then mount the device asspecified in the program or instructions. Alternatively, use the cdcheck –m or mount command to determine the current mount point of the device. For furtherinformation, see the cdromd command documentation in the AIX 5L Version 5.2Commands Reference.

The installation code allows for this automatic mounting. If cdromd is enabled andthe mkcd command is run, the CD–R or DVD–RAM is ejected after the image iscompleted. If you do not want to have the media ejected, then the cdromd daemonshould be put in the inoperative state with the following command:


This chapter describes the following procedures for performing basic NIM operations andsimple configuration tasks using the Web-based System Manager NIM interface or theSystem Management Interface Tool (SMIT), as well as from the command line. Theprocedures in this chapter identify prerequisite tasks or conditions that must be met beforeperforming the task.

• Configuring the NIM Master and Creating Basic Installation Resources on page 23-3

• Adding a Standalone NIM Client to the NIM Environment on page 23-6

• Using Installation Images to Install the Base Operating System (BOS) on a NIM Clienton page 23-10

• Using a mksysb Image to Install the Base Operating System (BOS) on a NIM Client(mksysb Installation) on page 23-12

• Performing a Nonprompted BOS Installation on page 23-15

• Installing to Clients on ATM Networks on page 23-17

• Customizing NIM Clients and SPOT Resources on page 23-19

• Configuring the NIM Master and Creating Resources to Support Diskless and DatalessClients Only on page 23-21

• Adding a Diskless or Dataless Client to the NIM Environment on page 23-24

• Initializing and Booting a Diskless or Dataless Machine on page 23-26

• Uninitializing Diskless and Dataless Machines on page 23-28

• Installing to an Alternate Disk on a NIM Client (cloning or mksysb) on page 23-29

• Network Installation Management Commands Reference on page 23-31


To start the Web-based System Manager NIM interface from an X–Windows session on theNIM master, type:

wsm

Notes:

1. For additional information about NIM operations and the required and optional attributesto customize operations, see Network Installation Management Concepts on page 27-1.

2. Using an AIX Version 5 lpp_source to install filesets on an AIX Version 4 client throughNIM, is not supported. If installing Version 5 filesets on a Version 4 system is necessary,the user can NFS export the lpp_source, mount it on the client, and then use theinstallp command or geninstall command to perform the installation procedures.

3. For assistance, use the online contextual help available for both the Web-based SystemManager and SMIT interfaces.

Extended help is available in the Web-based System Manager interface, offeringguidance for tasks you may need to do in NIM. To view extended help, select Contentsfrom the Help menu in the NIM container.

4. For tasks performed at the command line, the root user must be using ksh. Unexpectedresults can occur if the root user is set to another shell, such as csh.

5. If errors occur, it may be necessary to reset the machine before retrying the operation.For information about testing a NIM client, see Resetting Machines on page 24-4.


Configuring the NIM Master and Creating Basic InstallationResources

Using this procedure, you can configure the NIM master, create the minimum basicinstallation resources required to install NIM client machines, and manage the resources fordiskless and dataless clients.

Note: This procedure produces a large amount of output, especially whencreating the SPOT resource. Be sure to scan through the output to look fornonfatal errors and warnings that may not be evident from a successfulreturn code.

PrerequisitesThe NIM master must have at least 1 GB of available disk space. If such space is notavailable, see Using Client Machines as Resource Servers, and Defining an lpp_source onCD–ROM versus Disk.

From Web-based System Manager

1. Insert the AIX 5.2 Volume 1 CD into the appropriate drive of the designated mastermachine.

2. Start the Web-based System Manager Software application by entering wsm.

3. In the navigation area, expand and select the NIM container, then follow the directions inthe wizard.

From SMIT1. Insert the AIX 5.2 Volume 1 CD into the appropriate drive of the designated master

machine.

2. To install the bos.sysmgt.nim.master fileset, enter the smit install_latest fast path.

3. Using the LIST option, select /dev/cd0 for the INPUT device / directory for software.

4. Specify bos.sysmgt.nim.master as the SOFTWARE to install.

5. Accept the default values for all other fields on this screen. After successful completionof this installation, exit SMIT.

6. To configure the NIM master, enter the smit nim_config_env fast path.

7. Using the LIST option, select the Primary Network Interface for the NIM Master.

8. Using the LIST option, select /dev/cd0 or /dev/rmt0 for the Input device forinstallation / images field.

9. If you will be supporting diskless and dataless clients, select yes at the CreateDiskless/Dataless Machine Resources? field, and supply names for the resources tobe created.

10.Select yes at the Remove all newly added NIM definitions and file systems if anypart of this operation fails? field. This will make it easier to restart this procedure iffailures occur.

11.Accept the default values for all other fields on this screen.

Notes:

1. Depending on the speed of your machine, creating the basic NIM resources could be alengthy process.


2. This procedure provides the capability for much more than just configuring the NIMmaster and creating the lpp_source and SPOT resources. However, for this simpleconfiguration, only a subset of the available functions will be used. Advanced NIMadministrators can use the SMIT screens accessed through this procedure to create amore complex environment.

3. As you develop a better understanding of configuration tasks, you may prefer to notautomatically undo all configuration when failures occur (as in step 10 in the previousprocedure). Continuing from the last point of failure results in faster configuration forexperienced administrators.

From the Command Line1. Insert the AIX 5.2 Volume 1 CD into the appropriate drive of the designated master

machine.

2. To install the bos.sysmgt.nim.master fileset from the CD, enter:

# installp –agXd /dev/cd0 bos.sysmgt.nim.master

To install the bos.sysmgt.nim.master fileset from a tape, enter:

# installp –agXd /dev/rmt0 bos.sysmgt.nim.master

3. To configure the NIM master using the nimconfig command, enter:

# nimconfig –a attr1 = value 1 \

–a attr2 = value2 \

...

For example, to configure a NIM master with the following configuration:

master host name=master1

primary network interface = tr0

ring speed = 16

platform = chrp

kernel type = mp

Enter the following command sequence:

# nimconfig –a netname=network1 –a pif_name=tr0 \

–a ring_speed1=16 –a platform=chrp –a netboot_kernel=mp

Note: For additional attribute information, see the nimconfig command.

4. To create a file system in the rootvg volume group with 400 MB of space with a mountpoint of /export/lpp_source, enter:

# crfs –v jfs –g rootvg –a size=$((2000*400)) \

–m /export/lpp_source –A yes –p rw –t no \

–a frag=4096 –a nbpi=4096 –a compress=no

5. To mount the file system, enter:

# mount /export/lpp_source

6. The lpp_source contains the installation images copied from the source device (in thisexample, the CD–ROM). The server of the lpp_source will be the NIM master. Theimages will be stored in the /export/lpp_source/lpp_source1 directory. To create thelpp_source resource named lpp_source1, enter:

# nim –o define –t lpp_source –a source=/dev/cd0 \

–a server=master –a location=/export/lpp_source/lpp_source1 \

lpp_source1

7. To create a file system in the rootvg volume group with 200 MB of space with a mountpoint of /export/spot, enter:


–m /export/spot –A yes –p rw –t no \




# mount /export/spot

9. The SPOT resource will be installed from images in the image source (in this case, thelpp_source that was created in step 6). The server of the resource will be the NIMmaster, and the SPOT will be stored in the /export/spot/spot1 directory. To create theSPOT resource named spot1, enter:

# nim –o define –t spot –a source=lpp_source1 \

–a server=master –a location=/export/spot spot1

10.If you are not supporting diskless and dataless clients, you do not need to continue withthis procedure. If you are supporting diskless and dataless clients, create and mount afile system for their resources.

To create a file system in the rootvg volume group with 150 MB of space and a mountpoint of /export/dd_resource, enter:


–m /export/dd_resource –A yes –p rw –t no \


11.To mount the file system, enter:

# mount /export/dd_resource

12.Create the diskless and dataless client resources in subdirectories of the/export/dd_resource directory. Not all resources are required. Create only theresources to be used in your environment.

To create the root resource named root1 (required for diskless and dataless clients),enter:

# nim –o define –t root –a server=master \

–a location=/export/dd_resource/root1 root1

To create the dump resource named dump1 (required for diskless and dataless clients),enter:

# nim –o define –t dump –a server=master \

–a location=/export/dd_resource/dump1 dump1

To create the paging resource named paging1 (required for diskless clients), enter:

# nim –o define –t paging –a server=master \

–a location=/export/dd_resource/paging1 paging1

To create the home resource named home1 (optional), enter:

# nim –o define –t home –a server=master \

–a location=/export/dd_resource/home1 home1

To create the shared_home resource named shared_home1 (optional), enter:

# nim –o define –t shared–home –a server=master \

–a location=/export/dd_resource/shared_home1 shared_home1

To create the tmp resource named tmp1 (optional), enter:

# nim –o define –t tmp –a server=master \

–a location=/export/dd_resource/tmp1 tmp1

Notes:

1. The file systems created for the NIM resources are not required, but they can bebeneficial for storage management.

2. A SPOT resource is required for supporting diskless and dataless clients. The SPOTcreated in step 13 can be used for this purpose, so there is no need to create anotherSPOT specifically for diskless and dataless clients.

3. For more information about NIM resources, see NIM Resources on page 27-15.


Adding a Standalone NIM Client to the NIM Environment

This procedure describes how to add standalone clients to the NIM environment.Standalone clients are machines that, once installed, can obtain a boot image and mount allfile systems from the local hard disk, unlike diskless and dataless clients which depend onremote servers.

From one of the following interfaces, use Method A if the client machine is not running or ifthe client does not have AIX installed. Method A can also be used if BOS is to be installedon the client and the client is to be network–booted manually or to initiate the installationfrom a force–push operation. This procedure automatically adds NIM networks whenneeded.

From one of the following interfaces, use Method B if the client machine has AIX alreadyinstalled.

If the NIM client being defined is on a network that is not currently defined in the NIMenvironment, the niminit command will fail. If this is the case, use Method A: on page 23-6of this procedure to define the client on the NIM master, and then follow the steps in MethodB: on page 23-6 to complete the configuration.

Prerequisites1. The NIM master must be configured. For more information, see Configuring the NIM

Master and Creating Basic Installation Resources.

2. You must know the subnet mask, the default gateway for the client machine, and thedefault gateway for the NIM master.


1. To start the Web-based System Manager Software application, type:

wsm

2. In the navigation area, expand and select the NIM container.

3. Select the Machines container.

4. From the Machines menu, select New ––> Machine.

5. Use the wizard to complete the task.

From SMITTo add a standalone NIM client to the NIM environment using SMIT, choose between thefollowing methods:

Method A:1. On the NIM master, add a standalone client to the NIM environment by typing the smit

nim_mkmac fast path.

2. Specify the host name of the client.

3. The next SMIT screen displayed depends on whether NIM already has information aboutthe client’s network. Supply the values for the required fields or accept the defaults. Usethe help information and the LIST option to help you specify the correct values to add theclient machine.

Method B:1. On a system that you have chosen to be a NIM client, verify that if the

bos.sysmgt.nim.client fileset is installed by typing the following:

# lslpp –L bos.sysmgt.nim.client


2. If the bos.sysmgt.nim.client fileset is not installed, then install the fileset from the AIXVolume 1 CD by typing the following:

# installp –acXd /dev/cd0 bos.sysmgt.nim.client

3. Enter the smit niminit fast path.

4. Supply the values for the required fields or accept the defaults. Use the help informationand the LIST option to help you specify the correct values for defining your clientmachine.

Note: In AIX 5.2, if the LIST option is used to display valid platforms for the clientdefinition, only chrp is displayed as a selectable platform.

From the Command LineTo add a standalone NIM client to the NIM environment from the command line, choosebetween the following methods:

Method A:On the NIM master, type:

# nim –o define –t standalone –a platform= PlatformType \

–a netboot_kernel= NetbootKernelType \

–a if1= InterfaceDescription \

–a net_definition= DefinitionName –a ring_speed1= SpeedValue \

–a cable_type1= TypeValu e –a iplrom_emu= DeviceName MachineName

Example 1:

To add the machine with host name machine1 with the following configuration:

host name=machine1

platform=chrp

kernel=up

network type=ethernet

subnet mask=255.255.240.0

default gateway=gw1

default gateway used by NIM master=gw_master

cable type=bnc

network boot capability=yes (no emulation needed)

enter the following command sequence:

# nim –o define –t standalone –a platform=”chrp” \

–a netboot_kernel=”up” –a if1=”find_net machine1 0” \

–a cable_type1=”bnc” \

–a net_definition=”ent 255.255.240.0 gw1 gw_master” machine1

Example 2:


host name=machine2

platform=chrp

netboot_kernel=up

network type=token ring


default gateway=gw2


ring speed=16


# nim –o define –t standalone –a platform=”chrp” \

–a netboot_kernel=”up” –a if1=”find_net machine2 0” \

–a ring_speed1=”16” \

–a net_definition=”tok 255.255.225.0 gw2 gw_master” machine2


Notes:

1. If the find_net keyword in the if attribute causes NIM to successfully match a networkdefinition to the client definition, the net_definition attribute is ignored.

2. For more information about the attributes you can specify when defining NIM clients, seeDefining NIM Clients.

Method B:1. Install the bos.sysmgt.nim.client fileset on the client machine.

2. From the machine being defined as a client, enter:

# niminit –a name= ClientDefinitionName –a master= MasterName \

–a pif_name= Interface –a platform= PlatformType \

–a netboot_kernel= NetbootKernelType –a ring_speed1= SpeedValue \

–a cable_type1= TypeValue –a iplrom_emu= DeviceName

Note: For detailed attribute information, see the niminit command.

Example 1:


host name=machine1

NIM master’s host name=master_mac

primary interface adapter=en0

platform=chrp

kernel=up

cable type=bnc



# niminit –a name=machine1 –a master=master_mac \

–a pif_name=en0 –a platform=chrp –a netboot_kernel=up \

–a cable_type1=bnc

Example 2:


host name=machine2

NIM master’s host name=master_mac

primary interface adapter=tr0

platform=chrp

netboot_kernel=up

ring speed1=16


# niminit –a name=machine2 –a master=master_mac \

–a pif_name=tr0 –a platform=chrp –a netboot_kernel=up \

–a ring_speed1=16

Verifying the Status of Your Client Machine

To verify that the niminit command completed successfully, enter the following command atthe NIM client:

# nimclient –l –l MachineObjectName

Note: There is neither a Web-based System Manager application nor a SMITmenu to do this task.


The system returns output similar to the following:

Standalone2:

class = machines

type = standalone

Cstate = ready for a NIM operation

platform = chrp

netboot_kernel = up

if1 = Network2 standalone2 08005acd536d

cable_type1 = bnc

iplrom_emu = /dev/fd0

prev_state = customization is being performed

cpuid = 000247903100

Mstate = currently running

Cstate_result = success

If the system output to this query indicates any errors, you must validate all of your data,checking for accurate spelling, nonduplication of NIM names, and so forth, and redo theniminit operation.

Be sure to coordinate this operation with the system administrator of the NIM master, andensure that all NIM object names are unique in the entire NIM environment.


Using Installation Images to Install the Base Operating System(BOS) on a NIM Client

Using installation images to install BOS on a NIM client is similar to the traditional BOSinstallation from a tape or CD–ROM device, because the BOS image is installed from theinstallation images in the lpp_source resource.

Prerequisites• The NIM master must be configured, and lpp_source and SPOT resources must be

defined. See Configuring the NIM Master and Creating Basic Installation Resources.

• The NIM client to be installed must already exist in the NIM environment. To add theclient to the NIM environment, see Adding a Standalone NIM Client to the NIMEnvironment.


1. From the NIM container, select the Machines container.

2. In the contents area, select a target standalone machine for the installation.

3. From the Selected menu, choose Install Operating System.

4. If the client machine being installed is not already a running, configured NIM client, NIMwill not automatically reboot the machine over the network for installation. If the clientwas not rebooted automatically, initiate a network boot from the client to install it. Forinformation about performing a network boot, see Booting a Machine Over the Networkon page A-2.

5. After the machine boots over the network, the display on the client machine will beginprompting for information about how to configure the machine during installation. Specifythe requested information to continue with the installation.

Note: To perform a nonprompted installation, follow the instructions inPerforming a Nonprompted BOS Installation on page 23-15 to completethe prerequisite tasks.

From SMIT1. To install BOS on a NIM client using an rte installation, type smit nim_bosinst from

the NIM master.

2. Select the TARGET for the operation.

3. Select rte as the installation TYPE.

4. Select the SPOT to use for the installation.

5. Select the LPP_SOURCE to use for the installation.

6. In the displayed dialog fields, supply the correct values for the installation options oraccept the default values. Use the help information and the LIST option to help you.

7. If the client machine being installed is not already a running, configured NIM client, NIMwill not automatically reboot the machine over the network for installation. If the clientwas not rebooted automatically from SMIT, initiate a network boot from the client toinstall it. Use the procedure for Booting a Machine Over the Network to initiate thenetwork boot.

8. After the machine boots over the network, the display on the client machine will beginprompting for information about how the machine should be configured duringinstallation. Specify the requested information to continue with the installation.


Note: To perform a nonprompted installation, follow the instructions inPerforming a Nonprompted BOS Installation to complete the prerequisitetasks.

From the Command Line1. To initiate the bos_inst operation, type:

# nim –o bos_inst –a source=rte –a lpp_source= Lpp_Source \

–a spot= SPOTName –a accept_licenses=yes –a boot_client=yes/no

ClientName

Specify the resources to be used to support the installation and any additional options forcustomizing the installation. To perform a simple rte installation, specify the lpp_sourceand SPOT resources.

If the client machine being installed is not already a running, configured NIM client, NIMwill not automatically reboot the machine over the network for installation. A network bootmust be performed manually on the machine. If that is the case, supply theboot_client=no attribute to the bos_inst command. If the boot_client attribute value isnot specified, it defaults to boot_client=yes.

2. If the client was not rebooted automatically, initiate a network boot from the client toinstall it. Follow the Booting a Machine Over the Network on page A-2 procedure toperform the network boot.


Example

The client machine, machine1, is not a running, configured NIM client. You shouldspecify boot_client=no. To install the client using the lpp_source namedlpp_source1 and the SPOT named spot1, enter:

# nim –o bos_inst –a source=rte –a lpp_source=lpp_source1 \

–a spot=spot1 –a accept_licenses=yes –a boot_client=no machine1

Notes:

a. The steps to perform an rte installation are almost identical to the steps to performother types of BOS installations. The main difference is that rte must be specified inthe source attribute of the nim bos_inst command.

b. To perform a nonprompted installation, follow the instructions in Performing aNonprompted BOS Installation on page 23-15 to complete the prerequisite tasks.

c. For a complete description of the different ways that a BOS installation can becustomized by NIM, see bos_inst on page 27-37.


Using a mksysb Image to Install the Base Operating System(BOS) on a NIM Client (mksysb Installation)

A mksysb installation restores BOS and additional software to a target from a mksysbimage in the NIM environment.

For a complete description of different ways to customize a BOS installation using NIM, seebos_inst on page 27-37.

Prerequisites1. The NIM master must be configured, and SPOT and mksysb resources must be


2. The NIM client to be installed must already exist in the NIM environment. To add theclient to the NIM environment, see Adding a Standalone NIM Client to the NIMEnvironment.

3. The mksysb must be available on the hard disk of the NIM master or a running NIMclient, or the mksysb image is created during this procedure from either the NIM masteror a running NIM client.

4. The SPOT and mksysb resources should be at the same level of AIX when used forNIM BOS installations.

5. Many applications, particularly databases, maintain data in sparse files. A sparse file isone with empty space, or gaps, left open for future addition of data. If the empty spacesare filled with the ASCII null character and the spaces are large enough, the file will besparse, and disk blocks will not be allocated to it.

This situation creates an exposure in that a large file will be created, but the disk blockswill not be allocated. As data is then added to the file, the disk blocks will be allocated,but there may not be enough free disk blocks in the file system. The file system canbecome full, and writes to any file in the file system will fail.

It is recommended that you either have no sparse files on your system or that youensure you have enough free space in the file system for future allocation of the blocks.

Cloning ConsiderationsThe mksysb images enable you to clone one system image onto multiple target systems.The target systems might not contain the same hardware devices or adapters, require thesame kernel (uniprocessor or multiprocessor).

Because NIM configures TCPIP at the end of an installation, it is recommended that abosinst_data resource be allocated for cloning mksysb installations with theRECOVER_DEVICES field set to no. This will prevent the BOS installation process fromattempting to configure the devices as they were on the source machine of the mksysbimage.

Beginning in AIX 5.2, devices are not recovered if the mksysb image that is being installedwas not created on the same system. Attention: If the system you have cloned is usingOpenGL or graPHIGS, there may be some device filesets from these LPPs that must beinstalled after a clone. OpenGL and graPHIGS have graphics adapter–specific filesets, so ifyou cloned onto a system with a different graphics adapter, you will need to create a bundleas follows:

echo OpenGL.OpenGL_X.dev > /usr/sys/inst.data/user_bundles/graphic_dev.bnd

echo PEX_PHIGS.dev >> /usr/sys/inst.data/user_bundles/graphic_dev.bnd

You can allocate this bundle when you install the mksysb, and the device filesets will beinstalled automatically if OpenGL and graPHIGS are in your lpp_source.


From Web-based System Manager1. In the NIM container, select the Resources container.

2. From the Resources menu, select New ––> Resource ––> New Resources.

3. Use the wizard to complete the task.

Note: To perform a nonprompted installation, follow the instructions in Performinga Nonprompted BOS Installation to complete the prerequisite tasks.

From SMIT1. If the mksysb resource has already been created, skip to step 6. Otherwise, to create

the mksysb resource, enter the smit nim_mkres fast path.

2. Select mksysb from the list of resource types that can be defined.

3. In the displayed dialogs, supply the values for the required fields. Use the helpinformation and the LIST option to help you specify the correct values for defining yourmksysb resource.

4. If the mksysb image does not exist, create it by supplying the values for the fields underSystem Backup Image Creation Options.

Note: If the mksysb image already exists as a file on the hard disk of the NIMmaster or client, no additional information is needed to define yourmksysb resource.

5. Upon successful completion of this task, exit SMIT.

6. To use the mksysb resource to install a NIM client, enter the smit nim_bosinst fastpath.

7. Select a TARGET for the operation.

8. Select mksysb as the installation TYPE.

9. Select the MKSYSB to use for the installation.

10.Select the SPOT to use for the installation.

11. In the displayed dialog fields, supply the correct values for the installation options oraccept the default values. Use the help information or the LIST option to help you.

12.Run the SMIT dialog to install the NIM client.

13.If the client machine being installed is not already a running, configured NIM client, NIMwill not automatically reboot the machine over the network for installation. If the clientwas not rebooted automatically from SMIT, initiate a network boot from the client toinstall it. For information about to initiating a network boot, see Booting a Machine Overthe Network on page A-2.

14.After the machine boots over the network, the display on the client machine will beginprompting for information about how to configure the machine during installation. Specifythe requested information to continue with the installation.

Note: To perform a nonprompted installation, follow the instructions inPerforming a Nonprompted BOS Installation on page 23-15 to completethe prerequisite tasks.

From the Command Line1. If the mksysb resource has already been created, skip to step 2. To create the mksysb

resource, enter:

nim –o define –t mksysb –a server= ServerName \

–a location= LocationName –a mk_image=yes \

–a source= SourceMachine ResourceName


Specify the server name and location of the mksysb image. The mk_image and sourceattributes are used to create the mksysb image if it does not already exist.

For a complete description of all the options that can be specified when creating amksysb resource, see mksysb Resource.

Example 1:

To define a mksysb resource, mksysb_res1, from an existing mksysb image located in/export/backups/client_mksysb on the master, enter:

nim –o define –t mksysb –a server=master \

–a location=/export/backups/client_mksysb mksysb_res1

Example 2:

To create a mksysb image of the client machine, client1, in/export/resources/new_mksysb on the master, and to define a mksysb resource,mksysb_res2, enter:

nim –o define –t mksysb –a server=master \

–a location=export/resources/new_mksysb –a mk_image=yes \

–a source=client1 mksysb_res2

2. To initiate the bos_inst operation, enter:

nim –o bos_inst –a source=mksysb –a mksysb=mksysb \

–a spot=SPOTName –a boot_client=yes/no ClientName

Specify the resources to be used to support the installation and any additional options forcustomizing the installation. To perform a simple mksysb installation, specify themksysb and SPOT resources.

If the client machine being installed is not already a running, configured NIM client, NIMwill not automatically reboot the machine over the network for installation. A network bootmust be performed manually on the machine. If that is the case, supply theboot_client=no attribute to the bos_inst command. If the boot_client attribute value isnot specified, it defaults to boot_client=yes.

3. If the client was not rebooted automatically, initiate a network boot from the client toinstall it. For information about performing a network boot, see Booting a Machine Overthe Network.


Example 3:

To perform a mksysb installation using the mksysb, mksysb1, an optional lpp_source,lpp_source1, and the SPOT, spot1, on client machine, machine1, which is not arunning, configured NIM client, enter:

nim –o bos_inst –a source=mksysb –a mksysb=mksysb1 \

–a lpp_source=lpp_source1 –a spot=spot1 –a boot_client=no machine1

Notes:

1. The steps to perform a mksysb installation are almost identical to the steps to performother types of BOS installations. The main differences are that mksysb must bespecified in the source attribute of the nim bos_inst command, and a mksysb resourcemust be allocated for the operation.

2. To perform a nonprompted installation, follow the instructions in Performing aNonprompted BOS Installation to complete the prerequisite tasks.


Performing a Nonprompted BOS InstallationThis procedure provides information about how to create a bosinst_data resource to usefor a nonprompted BOS installation. After you have created the bosinst_data resource,refer to the following procedures to perform the nonprompted installation:

• Using Installation Images to Install the Base Operating System (BOS) on a NIM Clienton page 23-10

• Using a mksysb Image to Install the Base Operating System (BOS) on a NIM Client(mksysb Installation) on page 23-12

Prerequisites1. The NIM master must be configured, and lpp_source and SPOT resources must be


2. The NIM client to be installed must already exist in the NIM environment. To add theclient to the NIM environment, use the procedure Adding a Standalone NIM Client to theNIM Environment.

3. If any of the software to be installed during the BOS installation requires acceptance of alicense agreement, determine whether to accept the license agreement during BOSinstallation or defer acceptance until after the client has booted. Note that licenseacceptance takes place at the client. For a sample bosinst.data file that specifies thesyntax to control license acceptance, see bosinst.data File Example.

From Web-based System ManagerYou can use the Install Base OS wizard to create a bosinst_data resource. Thebosinst_data resource can be used for a rte installation or a mksysb installation.

If you want to create the bosinst_data resource, continue with the following steps:

1. In the Resources container, from the Resources menu, select New ––> Resource. TheAdd New Resource wizard displays.

2. Follow the wizard instructions to create a bosinst_data resource. The wizard creates abasic bosinst.data file, which can be used ”as is” or can be enhanced according tosample files. For a sample bosinst.data file, see Nonprompted Network Installation onpage 11-11. To do a nonprompted installation, the bosinst_data resource must becreated first.

From SMIT1. On the NIM master or any running NIM client, create a bosinst.data file that describes

how a machine should be configured during a BOS installation. For a samplebosinst.data file, see bosinst.data File Example.

2. To define the bosinst.data file as a bosinst_data resource in the NIM environment,enter the smit nim_mkres fast path.

3. Select bosinst_data from the list of resource types displayed on your screen.

4. Supply the values for the required fields. Use the help information and the LIST option tohelp you specify the correct values for defining your bosinst_data resource.

5. After the bosinst_data resource has been defined, follow the procedures for performingan rte or mksysb installation on a standalone machine. Be sure to specify thebosinst_data resource to use during the installation.


From the Command Line1. On the NIM master or any running NIM client, create a bosinst.data file that describes

how a machine should be configured during a BOS installation.

Note: To accept license agreements for software to be installed during theBOS installation, specify –a accept_licenses=yes on the nim –obos_inst command.

2. To define the bosinst.data file as a bosinst_data resource, enter:

# nim –o define –t bosinst_data –a server= ServerName \

–a location= LocationName NameValue

Using the server attribute, specify the name of the machine where the bosinst.data fileis located.

Using the location attribute, specify the full path name of the bosinst.data file that is tobe used as a resource.

3. After the bosinst_data resource has been defined, follow the normal procedure forperforming an rte or mksysb installation on standalone machines. Be sure to specifythat the bosinst_data resource be used for the installation.

For example, to perform a nonprompted rte installation of machine1 using thelpp_source1, spot1, and bosinst_data1 resources, enter:

# nim –o bos_inst –a source=rte –a lpp_source=lpp_source1 \

–a spot=spot1 –a accept_licenses=yes –a bosinst_data=bosinst_data1 \

machine1


Installing to Clients on ATM NetworksUnlike other network adapters, ATM adapters cannot be used to boot a machine. Installing amachine over an ATM network requires special processing.

BOS Installation over Non–ATM AdaptersNormally when a machine performs a network boot over a specified adapter, the adapter isconfigured by IPL–ROM or firmware. Then a boot image is transferred from the boot serverto the client using tftp. This boot image performs further configuration and mounts networkinstallation resources before starting the BOS installation.

BOS Installation over ATM AdaptersBecause an ATM adapter cannot be configured by IPL–ROM or firmware, a boot imagecannot be obtained over the network to perform a BOS installation. The NIM bos_instoperation must copy a boot image to the hard disk of the client before the machine isrebooted. Some Object Data Manager (ODM) information is also saved on the clientmachine so that when the machine is rebooted, the ATM adapter can be configuredproperly.

NIM clients may not have the programs installed to support the special processing requiredfor installation over ATM, so the /usr/lib/boot/bin and /usr/lpp/bos.sysmgt/nim/methodsdirectories are mounted at the client from the NIM master. These directories contain theprograms that run during the setup performed by the NIM bos_inst operation.

After the initial setup completes, an at job is issued to reboot the machine after one minutehas elapsed. When the machine reboots, the boot image that was copied to the hard diskconfigures the ATM adapter and mounts network installation resources for the BOSinstallation. The installation then proceeds as normal until the customization phase. DuringNIM customization, the ATM adapter is not reconfigured with a mktcpip command becausethe ODM already contains information carried over from before the machine was reinstalled.All other aspects of NIM customization are the same as for non–ATM clients.

NIM Configuration Requirements for ATM Networks• Machines that will have BOS installed over ATM must be running and configured NIM

clients.

Note: Configured NIM clients have the bos.sysmgt.nim.client filesetinstalled, are registered in the NIM master database, and have a valid/etc/niminfo file.

• BOS installations over ATM adapters will always use the at0 interface on the client.

• The NIM master fileset must be installed at AIX 4.3 or later with the update for ATMinstallation or any superseding level.

• The SPOT that will be used to install the clients must be at version AIX 4.3 or later withthe update for ATM installation or any superseding level.

Converting Generic Networks Into ATM NetworksPrior to the support of BOS installations over ATM, it was necessary to define ATM networksas ”generic” networks for performing other types of NIM operations. To convert genericnetworks into ATM networks, enter the following command:

nim –o change –a new_type=atm (network)

The adapter names for the client interfaces on the ATM network will automatically be set toat0 in the NIM database.

To change the name of the network, type the following:

nim –o change –a new_name= new_network_name current_network_name


System Recovery After Boot FailureBecause BOS installation over ATM requires a special boot image to be written to the harddisk of the client, the original boot image on the machine will be lost. If the installation isstopped or fails before BOS is reinstalled, it will not be possible to perform a normal rebootof the client unless system maintenance is performed. By performing system maintenance,a new boot image can be created on the hard disk to allow the machine to be booted fornormal use. Use the following procedure:

1. Boot the client from a CD.

2. When the installation options are displayed, select the option to perform systemmaintenance.

3. Make the necessary selections to access the machine’s root volume group.

4. In the maintenance shell, run the following sequence of commands:

a. bosboot –ad /dev/ipldevice

b. BLVDISK=’lslv –l hd5 | grep hdisk | head –1 |cut –d’ ’ –f1’

c. bootlist –m normal $BLVDISK

d. sync

e. sync

f. sync

g. reboot –q

If errors are detected during the NIM bos_inst operation and the client machine has notrebooted, it is possible to stop the machine from rebooting, and then execute the sequenceof commands in the above step 4 on the running system. To stop the reboot, use thefollowing procedure:

1. List the at jobs on the machine by entering the command: at –1

The first name in the output field will be the name of the job. For example:

$ at –1

root.884205595.a Wed Jan 7 14:39:55 1998

2. To remove the at job, enter the following command: at –r name of job

For example:

$ at –r root.884205595.a

at file: root.884205595.a deleted

Note: The reboot can also be prevented by removing the shutdown script that the at jobwas instructed to run by typing:

rm/tmp/_NIM_shutdown


Customizing NIM Clients and SPOT Resources

This procedure describes how to use NIM to install software on running, configured NIMclients and SPOT resources.

Prerequisites1. If the software is to be installed on a machine, the machine must be a running,

configured NIM client with push permissions enabled for the NIM master. Pushpermissions are enabled by default when a client is configured or installed by NIM.

2. If the software is to be installed on a SPOT resource, the server of the SPOT must berunning.

3. The installation image to be installed on the target is available in an lpp_sourceresource, and a check operation was performed on the lpp_source at some point afterthe image was first copied there. (The check operation updates the.toc file withinformation about the images present in the lpp_source.)

From Web-based System Manager1. From the NIM container, select the Machines container.

2. In the contents area, select a target machine (master or standalone), or in the Resourcescontainer, select a target SPOT.

3. From the Selected menu, choose Install/Update Software ––> Install AdditionalSoftware (Custom) to display the Install Software dialog.

4. Use the dialog to complete the task.

From SMITThe SMIT screens follow the same structure as those used for local installation operationsperformed on a system. When performing NIM customization operations, select the SMITscreen that most closely describes the installation you want to perform.

1. From the command line, enter the smit nim_task_inst fast path.

2. Select the SMIT menu item that matches the type of installation you want to perform.

3. Select a TARGET for the operation.

4. Select the lpp_source that contains the installation images to be used.

5. Select any other required resources.

6. In the final SMIT dialog, supply the values for the required fields or accept the defaults.Use the help information and the LIST option to help you specify the correct values.

From the Command LineTo perform the installation operation, enter:

nim –o cust –a lpp_source= Lpp_Source –a filesets= FilesetsList \

–a installp_bundle= InstallpBundle \

–a installp_flags= InstallpFlags TargetName

You will specify the resources to use to support the installation and any additional attributesfor customization.

The software to be installed on the client can be specified on the command line using eitherthe filesets attribute or by specifying an installp_bundle resource that lists the software.

The default installp flags to be used to install the software are –a, –g, –Q, and –X. Tospecify a different set of installp flags, you can list them in the installp_flags attribute.


Example 1:

To install the bos.diag and bos.dosutil filesets on the client, machine1, using thelpp_source resource named lpp_source1, enter:

nim –o cust –a lpp_source=lpp_source1 \

–a filesets=”bos.diag bos.dosutil” machine1

Example 2:

To install software into the SPOT resource, spot1, using the lpp_source resource,lpp_source1, and the list of filesets specified in the installp_bundle resource,installp_bundle1, enter:

nim –o cust –a lpp_source=lpp_source1 \

–a installp_bundle=installp_bundle1 spot1

Note: Several other resources and attributes can be specified on the commandline with the cust operation. For a complete description of the custoperation, see NIM Operations on page 27-33.


Configuring the NIM Master and Creating Resources toSupport Diskless and Dataless Clients Only

Use this procedure only if the NIM environment is to be used exclusively for diskless anddataless client management. If the NIM environment is also to be used for installing andmaintaining software on standalone machines, follow the procedure for Configuring the NIMMaster and Creating Basic Installation Resources on page 23-3.

Note: This procedure produces a large amount of output, especially whencreating the SPOT resource. Be sure to scan through the output to look fornonfatal errors and warnings that may not be evident from a successfulreturn code.

PrerequisitesThe NIM master must have at least 300 MB of available disk space. If such space is notavailable, see Using Client Machines as Resource Servers, and Defining an lpp_source onCD–ROM versus Disk.

From Web-based System Manager1. Insert the AIX media into the appropriate drive of the designated master machine.

2. Start the Web-based System Manager application by typing wsm.

3. In the navigation area, select and expand the Software container.

4. While still in the navigation area, select the Installed Software container.

5. From the Software menu, choose New Software (Install/Update) ––> InstallAdditional Software.

6. In the Install Software dialog, select /dev/cd0 as the software source.

7. Specify bos.sysmgt.nim as the software to install.

8. In the navigation area, select the NIM container.

9. From the NIM menu, select Configure Environment.

10.Follow the wizard instructions to guide you through the configuration.

From SMIT1. Insert the AIX media into the CD–ROM or tape drive of the designated master machine.

2. To install the bos.sysmgt.nim fileset, enter the smit install_latest fast path.

3. Using the LIST option, select /dev/cd0 or /dev/rmt0 for the INPUT device / directory forsoftware.

4. Specify bos.sysmgt.nim as the SOFTWARE to install.

5. Accept the default values for all other fields on this screen. After completion of thisinstallation, exit SMIT.

6. To configure the NIM master, enter the smit nimconfig fast path.

7. Specify a name in the Network Name field to be assigned to the NIM master’s network.

8. Using the LIST option, select the Primary Network Interface for the NIM Master.

9. Accept the default values for all other fields on this screen.

10.After the master is configured, exit SMIT.

11.Restart SMIT using the smit nim_mkres_dd_name_server fast path.


12.When prompted, select the NIM master as the server of the client resources.

13.Select yes in the Create a new SPOT? field, because there is not a SPOT currentlydefined in your environment.

14.Using the LIST option, select /dev/cd0 or /dev/rmt0 as the input device for installationimages.

15.Specify a name in the SPOT Name field.

16.Specify names for the other resources to be created in the NIM environment. If a nameis not specified, the resource will not be created.

17.Select yes at the Remove all newly added NIM definitions and filesystems if any part of this operation fails? field. This will make iteasier to restart this procedure if failures occur.

18.Accept the default values for all other fields on this screen.

Note: In most NIM environments, the SPOT will already exist to support baseoperating system installation operations on standalone machines. Insuch environments, it is not necessary to create a new SPOT.

From the Command Line1. Insert the AIX media into the CD–ROM or tape drive of the designated master machine.

2. If installing from a tape, skip to step 5. To create a mount point for the CD, type:

mkdir /cdfs

3. To create a cdrom file system, type:

crfs –v cdrfs –p ro –d’cd0’ –m’/cdfs’

4. To mount the CD, type:

mount /cdfs

5. To install the bos.sysmgt.nim fileset from the CD, type:

installp –agX –d /cdfs/usr/sys/inst.images bos.sysmgt.nim

or to install the bos.sysmgt.nim fileset from a tape, type:

installp –agX –d /dev/rmt0 bos.sysmgt.nim

6. If installing from CD, to unmount the cdrom file system, type:

unmount /cdfs

7. To configure the NIM master using the nimconfig command, type:

nimconfig –a attr1=value1 \

–a attr2=value2 \

...

For example, to configure a NIM master with the following configuration:

master host name=master1

primary network interface = tr0

ring speed = 16

platform = chrp

kernel type = mp


nimconfig –a netname=network1 –a pif_name=tr0 –a ring_speed=16 \

–a platform=chrp –a netboot_kernel=mp

Note: For additional attribute information, see the nimconfig command.

crfs –v jfs –g rootvg –a size=$((2000*200)) \

–m /export/spot –A yes –p rw –t no \




mount /export/spot

9. The SPOT resource will be installed from images in the image source (in this example,the CD). The server of the resource will be the NIM master, and the SPOT will be storedin the /export/spot/spot1 directory. To create the SPOT resource, enter:

nim –o define –t spot –a source=/dev/cd0 –a server=master \

–a location=/export/spot spot1

10.To create a file system in the rootvg volume group with 150 MB of space and a mountpoint of /export/dd_resource, enter:

crfs –v jfs –g rootvg –a size=$((2000*150)) \

–m /export/dd_resource –A yes –p rw –t no \


11.To mount the file system, enter:

mount /export/dd_resource

12.Create the diskless and dataless client resources in subdirectories of the/export/dd_resource directory. Not all resources are required. Create only theresources to be used in your environment.

To create the root resource named root1 (required for diskless and dataless clients),enter:

nim –o define –t root –a server=master \

–a location=/export/dd_resource/root1 root1

To create the dump resource named dump1 (required for diskless and dataless clients),enter:

nim –o define –t dump –a server=master \

–a location=/export/dd_resource/dump1 dump1

To create the paging resource named paging1 (required for diskless clients), enter:

nim –o define –t paging –a server=master \

–a location=/export/dd_resource/paging1 paging1

To create the home resource named home1 (optional), enter:

nim –o define –t home –a server=master \

–a location=/export/dd_resource/home1 home1

To create the shared_home resource named shared_home1 (optional), enter:

nim –o define –t shared_home –a server=master \

–a location=/export/dd_resource/shared_home1 shared_home1

To create the tmp resource named tmp1 (optional), enter:

nim –o define –t tmp –a server=master \

–a location=/export/dd_resource/tmp1 tmp1

Notes:

1. The file systems created for the NIM resources are not required, but they can bebeneficial for storage management.

2. For more information about NIM resources, see NIM Resources on page 27-15.


Adding a Diskless or Dataless Client to the NIM Environment

This procedure describes how to add diskless and dataless clients to the NIM environmentby adding an entry for the client to the NIM database on the master. This provides NIM withthe information required to satisfy boot requests from the client. However, resources for thediskless or dataless client machine must be initialized before the client will be able tosuccessfully boot and configure. See Initializing and Booting a Diskless or Dataless Machineon page 23-26 for more information. Diskless clients must mount all file systems fromremote servers. Dataless clients can have paging space, as well as the /tmp and /home filesystems on the local disk. Neither diskless nor dataless clients have a boot image on thelocal disk. Therefore, they must boot over the network.

Prerequisites1. The NIM master must be configured, and the resources for diskless or dataless clients

must be defined. For more information, see Configuring the NIM Master and CreatingResources to Support Diskless and Dataless Clients Only.

2. You must know the subnet mask, the default gateway for the client machine, and thedefault gateway for the NIM master.

From Web-based System Manager1. In the Machines container, from the Machines menu, select New ––> OK. The Add New

Machine wizard displays.

2. Follow the wizard instructions to add a diskless or dataless client to the NIMenvironment.

From SMIT1. To define a diskless or dataless client, enter the smit nim_mkmac fast path.

2. Specify the host name of the machine.

3. The SMIT screen displayed next depends on whether NIM already has information aboutthe client’s network. Supply the values for the required fields or accept the defaults. Usethe help information and the LIST option to help you specify the correct values to definethe client machine.

From the Command LineTo define a diskless or dataless client, enter:

nim –o define –t Diskless/Dataless \

–a platform= PlatformType –a netboot_kernel= NetbootKernelType \

–a if1= InterfaceDescription –a net_definition= DefinitionName \

–a ring_speed1= Speedvalue –a cable_type1= TypeValue \

–a iplrom_emu= DeviceName MachineName

Note: For detailed attribute information, see the descriptions of diskless anddataless clients in NIM Machines on page 27-2.


Example 1:To add the diskless client with the host name diskless1 to the NIM environment with thefollowing configuration:

host name=diskless1

platform=rspc

kernel=up

network type=ethernet


default gateway=gw1


cable type=bnc



nim –o define –t diskless –a platform=”rspc” \

–a netboot_kernel=”up” –a if1=”find_net diskless1 0” \

–a cable_type1=”bnc” \

–a net_definition=”ent 255.255.240.0 gw1 gw_master” \

diskless1

Example 2:To add the dataless client with the host name dataless1 to the NIM environment with thefollowing configuration:

host name=dataless1

platform=rs6k

netboot_kernel=up

network type=token ring


default gateway=gw2


ring speed=16

network boot capability=no (use emulation on a diskette)


nim –o define –t dataless –a platform=”rs6k” \

–a netboot_kernel=”up” –a if1=”find_net dataless1 0” \

–a ring_speed1=”16” \

–a net_definition=”tok 255.255.225.0 gw2 gw_master” \

–a iplrom_emu=”/dev/fd0” dataless1

Note: If the find_net keyword in the if attribute causes NIM to successfully matcha network definition to the client definition, the net_definition attribute isignored.


Initializing and Booting a Diskless or Dataless Machine

This procedure describes how to use NIM to configure and boot a machine as a diskless ordataless client in the NIM environment.

Prerequisites1. The NIM master must be configured, and the resources for diskless and dataless clients

must be defined. See Configuring the NIM Master and Creating Resources to SupportDiskless and Dataless Clients Only.

2. The NIM client must already exist in the NIM environment. To add the client to the NIMenvironment, use the Adding a Diskless or Dataless Client to the NIM Environmentprocedure.

From Web-based System Manager1. Select the Machines container.

2. In the contents area, select the diskless or dataless machine you want to initialize.

3. From the Selected menu, choose Initialize Machine Resources.

4. Use the dialog to specify or select the resources to use for initialization. You will specifyeither the Home resource or Shared Home resource for the machine, but not both.

5. After completion of the initialization operation, use the Booting a Machine Over theNetwork on page A-2 procedure to boot the client machine over the network.

Note: On older model rspc systems, it may be necessary to permanently setthe bootlist from the firmware menus to make the client always boot overthe network. For other systems, the bootlist is automatically set the firsttime the machine is booted as a diskless/dataless client.

6. After the client boots over the network and performs some initialization, the client willdisplay instructions for you to select the console for the machine.

From SMIT1. On the NIM master, enter the smit nim_dd_init fast path.

2. Select the client to be initialized from the list of clients displayed on your screen.

3. Supply the values for the required fields. Use the help information and the LIST option tohelp you specify the correct values for the initialization options.

4. After completion of the initialization operation, use the Booting a Machine Over theNetwork procedure to boot the client machine over the network.



From the Command Line1. To initialize the client resources for diskless clients, enter the following on the NIM

master:

nim –o dkls_init –a spot= SPOTName –a root= RootNam e \

–a dump= DumpName –a paging= PagingName ClientName


2. To initialize the client resources for dataless clients, enter the following on the NIMmaster:

nim –o dtls_init –a spot= SPOTName –a root= RootName \

–a dump= DumpName ClientName

Note: For detailed information about other attributes you can specify for thedkls_init and dtls_init operations, see dkls_init on page 27-46 anddtls_init on page 27-47.

3. After completion of the initialization operation, use the Booting a Machine Over theNetwork on page A-2 procedure to boot the client machine over the network.




Uninitializing Diskless and Dataless Machines

Diskless and dataless machines are uninitialized by performing the reset operation. Thisaction also provides the option to deallocate all resources for the machine. Deallocating allresources from the diskless or dataless machine removes all root data for the machine.Without deallocating resources, the uninitialize operation deallocates just the network bootimage.


2. In the contents area, select the diskless or dataless machine you want to initialize.

3. From the Selected menu, choose Uninitialize Machine Resources.

4. Use the dialog to uninitialize and, if desired, deallocate all resources from the client.

From SMIT1. To uninitialize diskless and dataless machines, enter the smit nim_dd_uninit fast path.

2. Select the Target.

3. If you want to remove all root data, change the DEALLOCATE Resources field to yes.

From the Command Line1. To uninitialize the client machine, enter the following on the NIM master:

nim –F –o reset ClientName

2. To deallocate all resources and remove root data, enter the following on the NIM master:

nim –o deallocate –a subclass=all ClientName


Installing to an Alternate Disk on a NIM Client (cloning ormksysb)

NIM allows you to install an AIX 4.3 or later mksysb image (mksysb resource) on a NIMclient’s alternate disk or to clone a NIM client’s current disk onto an alternate disk and applyupdates. Because the client system is running during installation, less time is required thanfor a normal installation.

Note: For information about the different ways NIM can customize an alternatedisk installation, see alt_disk_install on page 27-34.

Prerequisites1. The NIM master must be configured. To install a mksysb image onto the alternate disk,

the mksysb resource must be defined. See Configuring the NIM Master and CreatingBasic Installation Resources.

2. The NIM client must already exist in the NIM environment and must be running. To addthe client to the NIM environment, see Adding a Standalone NIM Client to the NIMEnvironment.

3. The bos.alt_disk_install.rte fileset must be installed on the NIM client. To install a newfileset on a NIM Client, see Customizing NIM Clients and SPOT Resources.

From Web-based System Manager1. Select the Machines Container.

2. In the contents area, select the standalone machine for the alternate disk installation.

3. From the Selected menu, choose Alternate Disk Installation ––> Clone the Rootvg toan Alternate Disk or Install Mksysb on an Alternate Disk.

4. Use the dialog to finish the installation.

From SMIT1. Enter the smit nim_alt_mksysb fast path from the NIM master.

2. Select the Target Machine or Target Group to Install.

3. Enter the Target Disk or Disks on the Target machine.

4. Accept the default installation options, or supply different ones in the displayed dialogfields. Use the help information and the LIST option for guidance.

5. The alternate disk installation will be initiated on the client, and progress can be seenwith the lsnim command (smit lsnim). If the ”Reboot when complete?” option is set toyes and the ”Phase to execute” is all or includes Phase 3, the client will reboot from thenewly installed disk when the alt_disk_install command is complete.

6. To clone a disk onto a NIM client’s alternate disk, enter the smit nim_alt_clone fast pathfrom the NIM master.

From the Command LineThe alt_disk_install command is initiated on the target system, and progress is shown withthe lsnim command. In addition, a log kept on the target system,/var/adm/ras/alt_disk_inst.log, contains progress messages and any error or warningmessages that might occur. The /var/adm/ras/nim.alt_disk_install log will contain debuginformation, if requested.


Installing mksysb on an Alternate DiskInitiate the alt_disk_install operation by entering:

nim –o alt_disk_install –a source=mksysb –a mksysb= Mksysb \

–a disk=’ diskname(s) ’ ClientName

Specify the mksysb resource to be used and any additional options for customizing theinstallation. To perform a simple alternate disk mksysb install, specify the source, mksysb,and disk resources.

Note: For detailed information about the mksysb resources, see mksysbResource.

Cloning the rootvg to an Alternate DiskTo clone a disk onto a NIM client’s alternate disk, enter:

nim –o alt_disk_install –a source=rootvg –a disk= diskname(s) ClientName

Specify any additional options for customizing the installation.

ExamplesThe client machine machine1 is a running system with a disk, hdisk2, that is notcurrently occupied by a volume group.

• To install this disk with a mksysb resource named 51mksysb enter:

nim –o alt_disk_install –a source=mksysb –a mksysb=51mksysb \

–a disk=hdisk2 machine1

• To clone the rootvg to hdisk2 enter:

nim –o alt_disk_install –a source=rootvg –a disk=hdisk2 machine1


Network Installation Management Commands ReferenceThis section provides information on NIM commands and where to find more information onthe NIM commands.

The nim_master_setup CommandThe nim_master_setup command installs the bos.sysmgt.nim.master fileset, configuresthe NIM master, and creates the required resources for installation, including a mksysbsystem backup.

The nim_master_setup command uses the rootvg volume group and creates an/export/nim file system, by default. You can change these defaults using thevolume_group and file_system options. The nim_master_setup command also allowsyou to optionally not create a system backup, if you plan to use a mksysb image fromanother system. The nim_master_setup usage is as follows:

Usage nim_master_setup: Setup and configure NIM master.

nim_master_setup [–a mk_resource={yes|no}]

[–a file_system= fs_name ]

[–a volume_group= vg_name ]

[–a disk= disk_name ]

[–a device= device ]

[–B] [–v]

–B Do not create mksysb resource.

–v Enable debug output.

Default values:

mk_resource = yes

file_system = /export/nim

volume_group = rootvg

device = /dev/cd0

The nim_clients_setup CommandThe nim_clients_setup command is used to define your NIM clients, allocate theinstallation resources, and initiate a NIM BOS installation on the clients. Thenim_clients_setup command uses the definitions in the basic_res_grp resource toallocate the necessary NIM resources to perform a mksysb restore operation on theselected clients. The usage for nim_clients_setup is as follows:

Usage nim_clients_setup: Setup and Initialize BOS install for NIM clients.

nim_clients_setup [–m mksysb_resource ]

[–c] [–r] [–v] client_objects

–m specify mksysb resource object name –OR– absolute file path.

–c define client objects from client.defs file.

–r reboot client objects for BOS install.

–v Enables debug output.

Note: If no client object names are given, all clients in the NIM environment areenabled for BOS installation; unless clients are defined using the –c option.

Other NIM Commands ReferenceThe AIX 5L Version 5.2 Commands Reference provides reference information about theNIM commands, AIX operating system commands, and commands for other licensedprograms for end users, system administrators, and programmers. This set of bookscontains examples and descriptions of the commands and their available flags. Thecommand entries are arranged in alphabetic order:

• AIX 5L Version 5.2 Commands Reference, Volume 1 contains commands ac through cx

• AIX 5L Version 5.2 Commands Reference, Volume 2 contains commands da through hy


• AIX 5L Version 5.2 Commands Reference, Volume 3 contains commands ib through mw

• AIX 5L Version 5.2 Commands Reference, Volume 4 contains commands na through rw

• AIX 5L Version 5.2 Commands Reference, Volume 5 contains commands sa through uu

• AIX 5L Version 5.2 Commands Reference, Volume 6 contains commands va through yp

For example, AIX 5L Version 5.2 Commands Reference, Volume 3 contains referenceinformation for the NIM lsnim command. The AIX 5L Version 5.2 Commands Reference,Volume 4 contains reference information for the NIM nim, nimclient, nimconfig, nimdef,and niminit commands.

24-1Advanced NIM Installation Tasks

Chapter 24. Advanced NIM Installation Tasks

This chapter describes the following procedures for performing advanced NIM installationtasks using the Web-based System Manager application or the System ManagementInterface Tool (SMIT), as well as from the command line:

• Controlling the Master or Client on page 24-2

• Resetting Machines on page 24-4

• Using Client Machines as Resource Servers on page 24-5

• Defining a Machine Group on page 24-6

• Adding New Members to Machine Groups on page 24-7

• Removing Members from Machine Groups on page 24-8

• Including and Excluding a Group Member from Operations on the Group on page 24-9

• Using Resource Groups to Allocate Related Resources to NIM Machines on page 24-10

• Managing Software on Standalone Clients and SPOT Resources on page 24-12

• Rebuilding Network Boot Images for a SPOT on page 24-15

• Maintaining Software in an lpp_source on page 24-16

• Viewing Installation, Configuration, and Boot Logs on page 24-18

• Verifying Installation with the lppchk Operation on page 24-19

• Using NIM to Install Clients Configured with Kerberos Authentication on page 24-20

• Concurrency Control on page 24-21

• Alternate Disk Migration Installation on page 15-4


Controlling the Master or Client

In the NIM environment, control is held by the NIM master or the standalone client. Thesystem allocating the resources has control. The allocation of resources is the act of makingresources available to clients for NIM operations. Normally, resources are allocatedautomatically as part of an operation, but they may also be allocated prior to the initiation ofan operation. The control status acts like a locking mechanism and remains with the clientor the master until the resources are deallocated. Using NIM, if the installation of astandalone client completes successfully, the resources are automatically deallocated.

When there are no resources allocated to the standalone client by the NIM master, thestandalone client takes control by allocating resources or disabling the NIM master’s pushpermissions. The control attribute is managed by the master and indicates whether themaster or the standalone client has permission to perform operations on the standaloneclient.

The control attribute indicates four control states. You can display the control attribute froma NIM client by entering:

nimclient –l –l StandAloneClientName

The control attribute can be displayed from the NIM master by entering:

lsnim –l StandaloneClientName

The control states are as follows:

control attribute is not set If the control attribute is not displayedwhen listing the machine object attributes,then neither the master nor the standaloneclient has control.

control = master The master has allocated resources to theclient and is ready to initiate an operation(or has already initiated an operation).

control = StandaloneClientName The standalone client has allocatedresources and can now initiate NIMoperations on itself.

control = StandaloneClientName push_off The standalone client has prohibited theNIM master from allocating resources orinitiating operations on the client. The clientitself can still control the allocation of NIMresources and the initiation of NIMoperations.

Disabling Master Push PermissionsThe NIM master must have push permissions to perform push operations on the NIMclients. You can disable the NIM master’s push permissions using Web–based SystemManager, SMIT, or command line as follows:

From Web-based System Manager1. From the main Web-based System Manager container, select the Software icon.

2. From the Software menu, select NIM Client ––> Permissions.

3. Select whether to grant or deny permission for the NIM master to initiate pushinstallations.


From SMITTo disable the master’s push permissions, enter the smit nim_perms fast path from theclient machine.

From the Command LineTo set control on the client to push_off, enter the following on the client machine:

nimclient –P

To re–enable push permission on the client, enter the following on the client machine:

nimclient –p


Resetting Machines

The operations performed using NIM can be very complex. To help ensure that theoperations can be completed successfully, NIM requires that a machine be in the readystate before operations can be run on it. While an operation is being performed, the state ofthe machine will reflect the current operation. After the operation completes, the machinereturns to the ready state.

If an operation on a machine is interrupted, the machine state may continue to reflect theoperation. If this occurs, the machine must be reset to the ready state before performingany further operations. To return a machine to the ready state, use the NIM reset operation.


2. In the contents area, select a target standalone, diskless, or dataless machine to reset.

3. From the Selected menu, choose Administration ––> Reset NIM State.

4. Use the dialog to reset the state of the machine.

You can also do this task from Troubleshooting. From the Selected menu, chooseTroubleshooting ––> Clean Up Failed or Interrupted Installation.

From SMIT1. To return a machine to the ready state, enter the smit nim_mac_op fast path.

2. Select the target machine for the operation.

3. Select reset as the Operation to Perform.

4. To deallocate resources, change the Deallocate All Resources? field to yes.

5. Change the Force field to yes.

From the Command Line1. To return a machine to the ready state, enter:

nim –Fo reset MachineName

2. To deallocate resources, enter:

nim –o deallocate –a ResourceType = ResourceName MachineName

where ResourceType is the type of the resource being deallocated (for example, lpp_source, SPOT, Script, etc.), ResourceName is the name of the resource beingdeallocated, and MachineName is the name of the machine that has been allocated theresources.

Note: Resetting a machine will not automatically deallocate all the resourcesthat were allocated for the operation. To deallocate resources, use theNIM deallocate operation.


Using Client Machines as Resource Servers

Any machine in the NIM environment can be a resource server. In simple environments, theNIM master is usually used to serve all the NIM resources.

Defining resources on client machines can be beneficial for the following reasons:

• Disk space limitations on the NIM master may prohibit the storage of all the resources ona single machine.

• Resource usage may be heavy, and communications and data access bottlenecks couldoccur if all the resources were served by a single machine.

For example, if you use NIM to install 200 machines on 5 different subnets, you couldhave a set of resources created and available on each subnet. Each set of resourceswould be used to install the machines on the same subnet. In addition to distributing theworkload among several resource servers, this would also reduce the network trafficacross the gateways between the different subnets.

From Web-based System Manager1. Select the Resources container.

2. From the Resources menu, select New Resources.

3. Follow the wizard instructions to create the resource.

From SMIT1. To create a resource on a NIM client, enter the smit nim_mkres fast path.

2. Select the Resource Type.

3. In the displayed dialog fields, supply the correct values for the resource options. Be sureto specify the name of the client machine for the Server of the Resource field. Use thehelp information or the LIST option to help you. All attributes specified when the resourceis defined (such as location and source) must be local to the server machine.

From the Command LineTo create a resource on a NIM client, specify the client’s NIM name for the server attributewhen defining the resource.

Example:

To create an lpp_source resource named images2 from a CD on the NIM client machine,client_mac1, in the /resources/images directory, enter:

nim –o define –t lpp_source –a server=client_mac1 \

–a location=/resources/images –a source=/dev/cd0 images2


Defining a Machine Group

Machine groups can be defined to collect multiple clients in a common target for NIMoperations. Groups can be defined for standalone, diskless, or dataless clients; but a groupcan only contain clients of a single type.

Web-based System Manager supports the following types of machine groups:

• A temporary machine group is created when multiple machines are selected in the NIMcontainer and an action from the Selected menu is performed. The temporary group isremoved when the action is completed.

• If you want a more permanent machine group, you can create it using the New MachineGroup menu option in the NIM menu.

In the Web-based System Manager NIM application, machine groups are not explicitlycreated and managed, but ad hoc groupings are supported by multi–selecting the iconsrepresenting machines in the NIM container. After they are selected, a group of machinescan be administered by selecting an action from the Selected menu.

Note: You can perform most operations only on multi–selected machines of thesame type.

From Web-based System Manager1. Select the Groups container.

2. From the Groups menu, select New ––> Group.

3. Select the machine type.

4. Select a machine from the list on the right, and click the < button to add the machine tothe new group. Repeat this step until all the desired members of the machine group arein the Members list on the left.

5. Click OK.

From SMIT1. To define a machine group, enter the smit nim_mkgrp fast path.

2. Select the type of group you want to define.

3. Enter the name of the group and member information.

From the Command LineTo define a machine group, enter:

nim –o define –t mac_group –a add_member= MemberName GroupName

For example, to create a machine group named MacGrp1 containing previously definedmachines Standalone1, Standalone2, and Standalone3, enter:

nim –o define –t mac_group –a add_member=Standalone1 \

–a add_member=Standalone2 –a add_member=Standalone3 \

–a comments=”Machines for Department d03” MacGrp1


Adding New Members to Machine Groups

New members can be added to machine groups, however, the new member must be of thesame machine type as existing members. Members can be added to machine groups usingthe Web-based System Manager NIM application.


2. In the contents area, select a group.

3. From the Selected menu, choose Add/Remove Members....

4. Select a machine from the list on the right, and click on the < button to add the machineto the new group. Continue with this step until all the desired members of the machinegroup are in the list on the left.

5. Click on OK.

From SMIT1. To add members to a machine group, enter the smit nim_chgrp fast path.

2. Select the machine group to modify.

3. Specify members to add to the group. Use the LIST option to select members to add.

From the Command LineTo add a member to a machine group, enter:

nim –o change –a add_member= MachineName GroupName

For example, to add the diskless client, diskless5, to the machine group,diskless_grp, enter the following command:

nim –o change –a add_member=diskless5 diskless_grp

Alternatively, you could have specified group members in both the define and changeoperations by using sequenced member attributes, such as –a member1=Standalone1–a member2=Standalone2 and so forth.


Removing Members from Machine Groups

Members can be removed from machine groups. Whenever the last member of a machinegroup is removed, the group definition is also removed.

The Web-based System Manager NIM application can be used to remove members frommachine groups.


2. From the Selected menu, choose Add/Remove Members.

3. Select a machine from the list on the left and click on the > button to add the machine tothe list on the right. Continue with this step until all the desired members of the machinegroup have been removed.

4. Click on OK.

From SMIT1. To remove members from a machine group, enter the smit nim_chgrp fast path.

2. Select the machine group to modify.

3. Specify members to remove from the group. Use the LIST option to select members toremove.

From the Command LineTo remove a member from a machine group, enter the following command:

nim –o change –a rm_member= MachineName GroupName

For example, to remove machine, Standalone2, and add machine, Standalone4, to thegroup, MacGrp1, enter:

nim –o change –a rm_member=Standalone2 \

–a add_member=Standalone4 MacGrp1


Including and Excluding a Group Member from Operations onthe Group

Group members may be included or excluded by using the Web-based System ManagerNIM application, SMIT, or from the command line. Use the select operation from thecommand line to indicate that specific members of a machine group should be included orexcluded from operations on that group. This capability is useful if an operation needs to betried again on specific group members that failed during an initial operation on the group.When a group member is marked as being excluded, it remains so until it is included again.


2. In the contents area, expand a group container to view the members included in thatgroup.

3. Select a machine from those listed in the container.

4. From the Selected menu, choose Properties.

From SMIT1. To include or exclude a group member from operations on the group, enter the smit

nim_grp_select fast path.

2. Select the name of the group from which you want to include or exclude members.

3. Select the members to include or exclude.

From the Command LineTo include or exclude a group member, enter the following:

nim –o select –a include_all= Value –a exclude_all= Value \

–a include= MemberName –a exclude= MemberName GroupName

As an example, to exclude the machine, Standalone2, from further operations on machinegroup, MacGrp1 and to include a previously excluded machine, Standalone3, enter:

nim –o select –a exclude=Standalone2 –a include=Standalone3 MacGrp1

The special attributes include_all and exclude_all, when assigned a value of yes, can beused respectively to include or exclude all members in a group. The select operationevaluates command line attributes from left to right. The following example shows how toexclude all members except Standalone2 from subsequent operations on the MacGrp1machine group:

nim –o select –a exclude_all=yes –a include=Standalone2 MacGrp1

Using the special –g option shows the excluded status of the group’s members:

lsnim –g MacGrp1

Group member information similar to the following is displayed:

MacGrp1:

type = mac_group

member1=Standalone1;ready for a NIM operation,not running;EXCLUDED

member2=Standalone2;ready for a NIM operation; currently running;

member3=Standalone3;ready for a NIM operation,not running;EXCLUDED


Using Resource Groups to Allocate Related Resources to NIMMachines

NIM resource groups allow association of resources so they can be allocated as a logicalunit to machines prior to other NIM operations. Resource groups can only contain one ofeach resource type, except for script and installp_bundle resources, which may occurmultiple times in a given resource group.

Defining a Resource Group

From SMIT1. To define a resource group, enter the smit nim_mkgrp_resource fast path.

2. Enter the name of the group with member information.

From the Command LineTo define a resource group, enter:

nim –o define –t res_group –a ResourceType = ResourceName GroupName

As an example, to create a resource group named ResGrp1 containing previously definedresources, images1, spot1, bosinst_data1, and bundle1, enter:

nim –o define –t res_group –a lpp_source=images1 –a spot=spot1 \

–a bosinst_data=bosinst_data1 –a installp_bundle=bundle1 \

–a comments=”BOS Install Resources” ResGrp1

Allocating a Resource Group

From SMIT1. To allocate a resource group, enter the smit nim_alloc fast path.

2. Select the machine or machine group from the list of defined machines (for example,Standalone1 ).

3. A list of resource groups is displayed. Select the resource group you want to allocate.

From the Command LineTo allocate a resource group, enter:

nim –o allocate –a group= ResGroupName TargetName

For example, to allocate a resource group named ResGrp1 to a machine namedStandalone1, enter:

nim –o allocate –a group=ResGrp1 Standalone1

Alternatively, the group resource can be specified on the command line to the operation. Forexample, to allocate the resource group, ddResGrp, while performing the dkls_initoperation on a group of diskless machines named DklsMacs, enter:

nim –o dkls_init –a group=ddResGrp DklsMacs

Defining Default Resource Groups

After a resource group is defined, you may want to specify the group as the set of defaultsfor all operations that require resources. Set the default_res attribute on the master to thename of the resource group that you want to be the default.


From SMIT1. To define default resource groups, enter the smit nim_grp fast path.

2. Choose Select/Unselect a Default Resource Group.

3. Fill in the name of the group that is to act as the default.

From the Command LineTo define default resource groups, enter:

nim –o change –a default_res= ResGroupName master

For example, if the ResGrp1 resource group should be the set of default resources for allNIM operations, enter:

nim –o change –a default_res=ResGrp1 master

Note: All applicable resources are allocated from the group specified as thedefault for all operations, except for installp_bundle for a maint operation.

A resource from the default group will only be allocated if a resource of the same typeis not already allocated and if a resource of that type is not specified on the commandline for automatic allocation. The exceptions are the script and installp_bundleresources, of which all occurrences in the resource group and specified on thecommand line will be allocated.

Default members can be overridden by specifying a null value in the attributeassignment for that resource.

The following bos_inst operation allocates all applicable bos_inst resources from theresource group specified as the default, except for the bosinst_data resource:

nim –o bos_inst –a bosinst_data=Standalone1


Managing Software on Standalone Clients and SPOTResources

The commands for managing software on standalone clients and SPOT resources aregenerally the same. Specify the name of the machine, group, or SPOT as the target of theoption.

Note: If the SPOT is currently allocated to a NIM client, NIM prevents the changeto the SPOT. Use the Force (–F) option to force the operation.

Software updates to a SPOT cause the SPOT ’s network boot images to be rebuilt whennecessary. If you think the boot images are bad, you can force them to be rebuilt using theNIM check operation.

Software updates to a SPOT may also cause software updates to occur in the root parts ofdiskless and dataless clients of the SPOT. This will occur automatically. You can force asynchronization of the client root parts using the NIM sync_roots operation on the SPOT.

For information on how to install additional software on standalone clients and SPOTresources, see Customizing NIM Clients and SPOT Resources on page 23-19.

Listing Software Installed on a Standalone Client or SPOT


2. In the contents area, select a target machine (master or standalone), or in the Resourcescontainer, select a target SPOT resource.

3. From the Selected menu, choose List Installed Software ––> All Installed.

From SMIT1. To list software installed on a standalone client or SPOT, enter the smit

nim_list_installed fast path.

2. Select the menu item that describes the list operation you want to perform.

3. Select a target for the operation.

4. In the displayed dialog fields, supply the required values. Use the help information or theLIST option to help you.

From the Command LineEnter the following command:

nim –o lslpp [–a lslpp_flags= LslppFlags ] TargetName

where LslppFlags are the flags to be passed to the lslpp command, and TargetName is thename of the client or SPOT object.

For example:

nim –o lslpp –a lslpp_flags=La spot1


Listing Software Updates, Installed on a Standalone Client or SPOT, byKeyword


2. In the contents area, select a target machine (master or standalone), or in the Resourcescontainer, select a target SPOT resource.

3. From the Selected menu, choose List Installed Software ––> Fix (APAR) Status.

4. Use the dialog to list the installation status of specific installed fixes.

From SMIT1. To list fixes installed on a standalone client or SPOT by APAR number or keyword, enter

the smit nim_mac_op fast path for standalone clients, or enter the smit nim_res_opfast path for SPOTs.

2. Select the standalone client or SPOT resource object.

3. Select the fix_query operation.

4. Select the desired fix_query flags or accept the default settings. Specify the fix_bundleobject name; or to check the installation status of an APAR, specify the fix APARnumbers. If you leave both blank, all known fixes are displayed.


nim –o fix_query [ –afixes=” FixKeywords ” ] \[–afix_bundle=

FixBundleName ] [ –afix_query_flags= FixQueryFlags ] \

TargetName

where FixKeywords are APAR numbers; FixBundleName is the object name of thefix_bundle resource; FixQueryFlags are optional flags to the fix_query operation, andTargetName is the client, group, or SPOT for which to display fix information.

Valid FixQueryFlags are as follows:

–a Displays symptom text.

–c Displays output in colon–separated format.

–F Returns failure unless all filesets associated with a fix are installed.

–q Quiet option; if –q is specified, no heading is displayed.

–v Verbose option; gives information about each fileset associated with afix (keyword).

For example:

• To query the fix database on standalone1 to determine if all fileset updates for fixIX12345 are installed, enter:

nim –o fix_query –afixes=IX12345 standalone1

• To list fix information for all known fixes installed on spot1, with symptom text, enter:

nim –o fix_query –afix_query_flags=a spot1


Maintaining Software on Standalone Clients and SPOT Resources

NIM uses the installp command to construct a SPOT by installing in the SPOT the softwareproducts that each SPOT needs to support the NIM environment. Because the installpcommand also supports software maintenance tasks, you can perform these tasks onSPOTs as well. For example, you can remove previously installed optional software from aSPOT when they are no longer being used. This kind of task is accomplished by performingthe NIM maint operation on a SPOT using the Web-based System Manager NIMapplication, SMIT, or command line interface. You interact with the installp command bysupplying the installp_flags, and either filesets or installp_bundle attributes.


2. In the contents area, select a target standalone machine, or in the Resources container,select a target SPOT resource.

3. From the Selected menu, choose Software Utilities ––> Commit Applied Updates,Reject Applied Updates, or Remove Software, depending upon the task you want toperform.

From SMIT1. To perform software maintenance, enter the smit nim_task_maint fast path.

2. Select the menu item that describes the maintenance that you want to perform.

3. Select the target for the operation.

4. In the displayed dialog fields, supply the required values. Use the help information or theLIST option to help you.


nim –o maint –a installp_flags=” InstallpFlags ” \

[–a filesets=” FileSetNames ” | \

–a installp_bundle= BundleResourceName ] [–F] TargetName

where InstallpFlags are the flags you want to pass to the installp command; FileSetNamesare the names of the filesets or packages you want to maintain; BundleResourceName isthe object name of the installp_bundle resource; and TargetName is the object name ofthe standalone client, group, or SPOT.

For example:

• To remove the bos.adt and bos.INed software packages from standalone1,enter:

nim –o maint –a filesets=”bos.adt bos.INed” –a \

installp_flags=”–u” standalone1

• To remove the bos.INed software package from spot1, which is allocated to disklessor dataless clients, without deallocating spot1 first, enter:

nim –o maint –F –a filesets=bos.INed –a installp_flags=”–u” \

spot1

• To remove the packages from spot1 which are listed in the bundle pointed to by theinstallp_bundle resource object, bundle1, enter:

nim –o maint –a installp_flags=”–u” –a installp_bundle=bundle1 \

spot1

• To clean up from an interrupted software installation on spot1, enter:

nim –o maint –a installp_flags=”–C” spot1


Rebuilding Network Boot Images for a SPOT


2. In the contents area, select a target SPOT.

3. From the Selected menu, choose Check SPOT.

4. Use the dialog to select the Build debug network boot images and/or the force option, ifneeded.

You can also perform this task from Troubleshooting. From the Selected menu, chooseTroubleshooting ––> Build Non–Debug Network Boot Images.

From SMIT1. To rebuild network boot images for a SPOT, enter the smit nim_res_op fast path.

2. Select the SPOT.

3. Select the check operation.

4. In the displayed dialog fields, set the Force option to yes.

From the Command LineTo force the rebuild of the boot images, enter:

nim –Fo check SPOTName

For information on how to install additional software on standalone clients and SPOTresources, see Customizing NIM Clients and SPOT Resources.


Maintaining Software in an lpp_source

To add or remove software in an lpp_source, add or remove the installation image from thelpp_source directory, and then initiate the NIM check operation on the lpp_source.

Copying Software to an lpp_source


2. In the contents area, select an lpp_source.

3. From the Selected menu, choose Properties. The General page of the propertiesnotebook displays.

4. From the General page, identify the location of the resource. Close the notebook.

5. From the Resources menu, select Copy Software to Directory, and specify as thedestination directory, the location of the resource identified in the notebook.

6. After the copy is completed, select the lpp_source and from the Selected menu, chooseCheck NIM State. This action updates the table of contents (.toc) file for thelpp_source.

From SMIT1. To copy software from installation media to an lpp_source, insert the installation media

in the appropriate drive of the lpp_source server.

2. To copy the software to the lpp_source directory, enter smit bffcreate from theresource server.

3. Enter the INPUT device / directory for software.

4. In the displayed dialog fields, supply the correct values or accept the default values. Besure to specify the lpp_source location for the directory to store the installation images.Use the help information and the LIST option to help you.

From the Command Line1. Copy the software from the media to the lpp_source directory.

2. Perform the NIM check operation on the lpp_source by entering the followingcommand:

nim –o check Lpp_sourceName

Removing Software from an lpp_source

To remove software from an lpp_source, delete the installation image from the lpp_sourcedirectory.

Note: This function is only available from the command line interface.

From the Command Line1. Remove the installation image from the lpp_source directory.

2. Perform the NIM check operation on the lpp_source by entering the followingcommand:



Running the NIM check Operation

After adding or removing software, you must run the NIM check operation on thelpp_source to update the installation table–of–contents file for the resource.

In addition to updating the table–of–contents for the lpp_source, the check operation alsoupdates the simages attribute for the lpp_source, which indicates whether the lpp_sourcecontains the images necessary to install the Base Operating System images on a machine.


2. In the contents area, select a target lpp_source resource.

3. From the Selected menu, choose Check NIM State.

From SMIT1. To run the NIM check operation, enter the smit nim_res_op fast path.

2. Select the lpp_source for the operation.

3. Select check for the operation to be performed.

From the Command LineTo initiate the NIM check operation on the lpp_source, enter:


If the lpp_source is currently allocated to a client, use the Force option as follows:

nim –F –o check Lpp_sourceName


Viewing Installation, Configuration, and Boot Logs

After installing a standalone machine, use the showlog operation to check the installationresults by viewing the installation, boot, and configuration logs. One of several log types canbe viewed by specifying one of the following as the value of the log_type attribute to theshowlog operation:

devinst Output from the installation of key system and device–driversoftware

niminst Output from the installation of user–specified software (includinginstallation of NIM client software during a bos_inst operation)

bosinst Output from the BOS installation program

boot The machine’s boot log

lppchk A log of the output from the lppchk operation executed on astandalone NIM client

script Output from any configuration script resources allocated for abos_inst operation

nimerr Errors encountered during execution of the nim command.

By default, the showlog operation applied to a standalone machine displays the niminstlog and shows the output logged when software was last installed on the machine usingNIM. The last entry is also shown by default for the script and lppchk logs. The entirecontents of the niminst, script, and lppchk logs can be displayed by assigning the full_logattribute a value of yes when executing the showlog operation. The entire log is shown forall other log types.


2. In the contents area, select a target machine (master, standalone, diskless, or dataless),or in the Resources container, select a target SPOT.

3. From the Selected menu, choose Troubleshooting ––> Show NIM Logs.

4. Use the dialog to select the log you want to examine.

From SMIT1. Enter the smit nim_mac_op fast path to view a machine’s log, or enter smit

nim_res_op to view a SPOT ’s log.

2. Select the object name of the machine or SPOT whose log you want to view.

3. Select showlog from the list of operations.

4. Select the log type to be viewed.

5. Specify if the full log should be viewed (only applicable to script, lppchk, and niminstlogs).

From the Command LineTo view a log on a standalone machine or SPOT, enter:

nim –o showlog –a LogTyp e= value ObjectName

where LogType represents the log you want to view, and ObjectName is the name of themachine or SPOT whose log will be viewed.


Verifying Installation with the lppchk Operation

When investigating functional problems in software, you can use the lppchk operation tocheck the integrity of installed software.


2. In the contents area, select a target standalone machine, or in the Resources container,select a target SPOT.

3. From the Selected menu, choose Troubleshooting ––> Verify Installed Software.

4. Use the dialog to select whether to verify all or some installed software on the selectedmachine or SPOT.

From SMIT1. Enter the smit nim_mac_op fast path to check software on a machine, or enter smit

nim_res_op to check software on a SPOT.

2. Select the target of the lppchk operation.

3. Select the desired verification mode.


nim –o lppchk –a filesets= FilesetName \

–a lppchk_flags=”lppchkFlags” ObjectName

where FilesetName is the name of a single fileset (or a name with the * wildcardcharacter), and ObjectName is the name of the machine or SPOT which is the target ofthe lppchk operation. Valid lppchk_flags are defined as follows:

–f Fast check (file existence, file length)

–c Checksum verification

–v Fileset version consistency check (default)

–l File link verification

Note:Only one of the flags –f, –c, –v, or –l may be specified.

–u Update inventory (only valid with –c or –l)

–m n Controls detail of messages. n equals 1 to 3, where 3 is the mostverbose.

For example, to perform the lppchk operation while verifying checksums for all filesets onthe machine named Standalone1, enter the following:

nim –o lppchk –a lppchk_flags=”–c” Standalone1


Using NIM to Install Clients Configured with KerberosAuthentication

Normally, NIM relies on Standard AIX authentication to allow the NIM master to remotelyexecute commands. Standard AIX authentication uses the.rhosts file to provide thiscapability. While NIM functionality depends on its ability to remotely execute commands,some system environments require stricter authentication controls. Kerberos authenticationprovides a higher level of authentication for executing remote commands on the systemwithout disabling NIM’s capabilities.

Using NIM to Install Clients Configured with Kerberos 4 AuthenticationIn AIX 4.3.3 and later, NIM can be used to install machines in an environment configured forKerberos 4 authentication. Clients configured for Kerberos 4 authentication will contain a$HOME/.klogin file for the root user. This file will determine what ticket is required to allowremote command execution. The user must obtain the required ticket before attempting toexecute remote commands through NIM.

The NIM master and all secure clients must have the Parallel System Support Program forAIX 3.1 (or later) installed and configured.

If secure clients will be reinstalled with BOS (Base Operating System), the authenticationmethods on the NIM master should be set for both Kerberos 4 and Standard UNIX.Because NIM will not have configured Kerberos 4 on the client after the BOS is installed.NIM will therefore have to rely on a.rhosts file to guarantee that it can remotely executecommands on the client until the client can be configured with Kerberos 4 and made into asecure client.

If only software customization and maintenance will be performed, the NIM master musthave its authentication methods set to match those of the clients. To manage secure clients,the master will need authentication methods set to include Standard UNIX.

For more information on installing and configuring Kerberos 4, see the SP AdministrationGuide (GC23–3897).

Using NIM to Install Clients Configured with Kerberos 5 AuthenticationIn AIX 4.3.2 and later, NIM can be used to install machines in an environment configured forKerberos 5 authentication. Clients configured for Kerberos 5 authentication will contain a$HOME/.k5login file for the root user. This file will contain an entry that specifies what hosttoken is required to allow remote command execution. This entry uses the following form:

hosts/hostname/self@cell

The NIM master and all secure clients must have DCE installed and configured at a levelgreater than or equal to 2.2.1.

If secure clients will be reinstalled with BOS, the authentication methods on the NIM mastershould be set for both Kerberos 5 and Standard UNIX. Because the client will not have DCEor Kerberos 5 configured and running after the BOS is installed. NIM will therefore have torely on standard rhosts to remotely execute commands on the client until it can beconfigured with Kerberos 5 and made into a secure client.

If only software customization and maintenance will be performed, the NIM master musthave its authentication methods set to match those of the clients. To manage secure clients,the master will need authentication methods set to include Standard UNIX.


Concurrency ControlNIM installations can become overburdened when they are being performed on a largenumber of clients at the same time. This can be caused by network bandwidth or workloadon the NIM servers. Users can ease the severity of this situation by controlling the numberof clients installing at the same time.

The concurrent and time_limit attributes can be used in conjunction with the bos_inst,cust, and alt_disk_install operations to control the number of client machines beingoperated on simultaneously from a client group. The concurrent attribute controls thenumber of clients in a group that are processing a particular operation at one time. After aclient finishes the operation, another client will initiate the operation one at a time. Thetime_limit attribute prohibits NIM from initiating an operation on any more clients of thegroup, after the specified time (in hours) has elapsed.


2. In the contents area, select multiple targets.

3. From the Selected menu, choose any of the following options:

– Install Operating System

– Install/Update Software

– Alternate Disk Install

4. From any of those dialogs, select the NIM settings or Advanced button.

5. In those dialogs, a section containing the Concurrency Controls can be specified.

Note: Web-based System Manager does not provide support for continuing aftera failure or if the group of machines were individually selected and the timelimit expired. The user must reselect the clients that failed or were notattempted and then reissue the command.

From SMITThe Concurrency Control attributes can be accessed from all SMIT panels under the Installand Update Software menu and the Alternate Disk Installation menu.

From the Command LineThe concurrent and time_limit attributes can be used in conjunction with the bos_inst,cust and alt_disk_install operations.

For example, to have the bos.games fileset installed on only five machines from the clientgroup tmp_grp at one time, enter the following command:

nim –o cust –a lpp_source=lpp_source1 –a filesets=bos.games \

–a concurrent=5 tmp_grp

In this example, to BOS install only 10 clients from tmp_grp, using lpp_source,lpp_source1, and SPOT, spot1, with no other installs permitted after three hours haveelapsed, enter the following command:

nim –o bos_inst –a lpp_source=lpp_source1 –a spot=spot1 \

–a concurrent=10 –a time_limit=3 tmp_grp

Note: The Concurrency Controlled operation can complete and leave the groupin one of the following states:

. All machines install successfully.


. Some machines may fail the installation.

. If the time_limit attribute was used, time may have expired before the installationoperation was complete.

In the first situation, the group will revert to the state prior to the operation. In thesecond and third situations, the group will be left in a state that indicates somemachines have completed and some have not. Problems with failing machines shouldbe investigated. At this point, the user can continue with the machines that did notcomplete by rerunning the command on the group. Alternatively, the user can ”reset”the group, which will set the group back to its state prior to the ConcurrencyControlled operation.

25-1Advanced NIM Configuration Tasks

Chapter 25. Advanced NIM Configuration Tasks

This chapter describes the following procedures for performing advanced NetworkInstallation Management (NIM) configuration tasks using the Web-based System ManagerNIM application or the System Management Interface Tool (SMIT), as well as from thecommand line:

• Removing Machines from the NIM Environment on page 25-2

• Creating Additional Interface Attributes on page 25-3

• Defining /usr versus non–/usr SPOTs on page 25-5

• Re–Creating SPOT Resources from Existing Directories on page 25-7

• Defining an lpp_source on CD–ROM versus Disk on page 25-8

• Establishing a Default NIM Route Between Networks on page 25-9

• Establishing a Static NIM Route Between Networks on page 25-10

• Recovering the /etc/niminfo File on page 25-12

• Backing Up the NIM Database on page 25-13

• Restoring the NIM Database and Activating the NIM Master on page 25-14

• Unconfiguring the NIM Master on page 25-15

• Booting Diagnostics on page 25-16

• Booting in Maintenance Mode on page 25-18

• Secondary Adapter Support on page 25-20


Removing Machines from the NIM Environment

Removing a machine from the NIM environment can be done by removing the clientinformation from the NIM database.

Note: When a client is removed from the NIM environment, NIM attempts toremove the /etc/niminfo file from the client machine. However, the clientfileset and rhost permission for the NIM master must be removed manuallyfrom the client system if such additional cleanup is desired.


2. In the contents area, select a machine to remove from the NIM environment.

3. From the Selected menu, choose Delete to remove the machine.

From SMIT1. To remove a machine from the NIM environment, enter the smit nim_rmmac fast path.

2. Select the machine to remove.

3. In the displayed dialog fields, accept the defaults.

From the Command LineTo remove a machine from the NIM environment, enter:

nim –o remove MachineName

where MachineName is the name of the machine to be removed.


Creating Additional Interface Attributes

The primary interface or the first interface (if1) is created when the master is activated, anda sequence number is used to identify the additional interfaces (if2, if3,...) in the machineobject definition. To create an additional if attribute for the master object, use eitherWeb–based System Manager, SMIT, or the nim –o change command operation.


2. In the contents area, select any machine (master, standalone, diskless, or dataless).

3. From the Selected menu, choose Properties. The General page of the MachineProperties notebook for the selected machine displays.

4. Select the NIM Interfaces tab.

5. Follow the dialog instructions.

From SMIT1. To create an additional if attribute, enter the smit nim_mac_if fast path.

2. Select the Define a Network Install Interface option.

3. Select the machine object name. In the example, this is master.

4. Enter the host name for the interface.

5. Complete the network–specific information in the entry fields on the Define a NetworkInstall Interface screen.

Note: If a NIM network does not already exist corresponding to the IP addressof the host name specified for the interface, additional networkinformation will be requested so the network can be defined.

From the Command LineTo create an additional if attribute for the master object, enter:

For Token–Ring:

nim –o change –a ifseq_no=’ NetworkObjectName AdapterHostNam e \

AdapterHardwareAddress ’ –a ring_speedseq_no =Speed master

For Ethernet:

nim –o change –a ifseq_no=’ NetworkObjectName AdapterHostName \

AdapterHardwareAddress ’ –a cable_typeseq_no =Type master

For FDDI:

nim –o change –a ifseq_no=’ NetworkObjectNam e AdapterHostName \

AdapterHardwareAddress ’ master

For other networks:

nim –o change –a ifseq_no=’ NetworkObjectName AdapterHostName \

AdapterHardwareAddress ’ master

Note: If you do not know the name of the NIM network to which the interface isattached or if a network corresponding to the interface has not beendefined, use the find_net keyword and net_definition attribute asdescribed in Defining NIM Clients.


In the example, the following command is run:

nim –o change –a if2=’Network2 srv1_ent 0’ –a \

cable_type2=bnc master

With this syntax, another if attribute is created for the master, which tells NIM that themaster has an Ethernet interface that uses a host name of srv1_ent, that the Ethernetadapter’s hardware address is 0 (not used), and that the master connects to the Network2network object.

To display detailed information about the master which will now show the if2 attribute, enter:

lsnim –l master

The command produces output similar to the following:

master:

class = machines

type = master

Cstate = ready for a NIM operation

reserved = yes

platform = rs6k

serves = boot

serves = nim_script

comments = machine which controls the NIM environment

Mstate = currently running

prev_state = ready for a NIM operation

if1 = Network1 server1 10005AA88399

master_port = 1058

registration_port = 1059

ring_speed1 = 16

if2 = Network2 Srv1_ent 02608c2e222c

cable_type2 = bnc


Defining /usr versus non–/usr SPOTs

A SPOT resource contains operating system files that are normally installed in the /usr filesystem of a machine. If disk space is limited on a machine or a SPOT must be createdquickly, it may be helpful to convert the machine’s /usr file system to a SPOT instead ofcreating an entirely separate SPOT at a different location.

If the /usr file system of a machine is converted to a SPOT, additional software will beinstalled on the machine to provide support for machines with different hardwareconfigurations. Most of the operating system files will already be installed on the system andwill not be reinstalled when the SPOT is created.

After a /usr file system is converted to a SPOT, all software installation and maintenanceoperations on the machine should be performed using NIM on the /usr SPOT resource thatwas created. This will ensure that all necessary SPOT operations are performed in additionto software installation or maintenance on the machine.


2. From the Resources menu, select New Resource.

3. Follow the wizard instructions to create the SPOT resource.

From SMIT1. To create a /usr SPOT, enter the smit nim_mkres fast path.

2. Select the Resource Type.

3. Type /usr in the Location of Resource field.

4. Supply the values or accept the defaults for all other fields on this screen.

From the Command LineTo create a /usr–SPOT, enter:

nim –o define –t spot –a server= ServerName \

–a location=/usr –a source= SourceName ResourceName

Example:

To convert the /usr file system on the machine, client1, to a SPOT named usrspotusing lppsource1 as the source for additional installation images, enter:

nim –o define –t spot –a server=client1 –a location=/usr \

–a source=lpp_source1 usrspot

Using the installp CommandAfter you convert a /usr file system to a SPOT, it is not recommended that you use theinstallp command to install or maintain software on the machine serving the SPOT. Thediskless and dataless clients and network boot images associated with the SPOT will not beupdated by the installp command unless it is invoked using NIM’s cust or maintoperations. If you need to use the installp command to install or maintain software on a/usr SPOT server, use the following steps:

1. Ensure that all NIM operations on the server and any clients associated with the SPOTare complete.

2. Deallocate the SPOT from all standalone clients.

3. Run the installp command.


4. Run the check operation on the SPOT after the installp command has completed:

nim –o check –F usrSPOTName

Note: The –F flag is required for rebuilding the boot images.

5. If this SPOT is being used to serve diskless or dataless clients, resynchronize alldiskless and dataless clients with the SPOT after the installp command completes byissuing the nim command with the sync_roots operation for the /usr SPOT:

nim –o sync_roots usrSPOTName

nim –o check –F usrSPOTName

The cust and maint operations must be used to manage software installed on non– /usrSPOT s.


Re–Creating SPOT Resources from Existing DirectoriesDefining NIM resources from existing files and directories can usually be done by specifyingthe server and location attributes to the nim – o define command. SPOT resources takelonger to define because software must be installed from installation images into the SPOTlocation. The nim –o command line interface always builds a SPOT from installationimages. However, if a directory structure for a SPOT already exists from a prior creation, itis possible to call a NIM method directly to redefine the SPOT without reinstalling all thesoftware.

The need to define a SPOT from an existing SPOT directory typically arises only when it isnecessary to rebuild the NIM database during system recovery.

To define a SPOT from a directory that previously had a SPOT installed in it, use thefollowing command:

/usr/lpp/bos.sysmgt/nim/methods/m_mkspot –o –a server= server \

–a location= location –a source=no spotname

Example:

A SPOT named spot1 was created on the NIM master in the /export/spot directory. Later,the NIM database became corrupted and has to be rebuilt. The SPOT files are still on themachine, but the SPOT must be redefined to NIM using the following command:

/usr/lpp/bos.sysmgt/nim/methods/m_mkspot –o –a server=master \

–a location=/export/spot –a source=no spot1


Defining an lpp_source on CD–ROM versus Disk

Normally an lpp_source resource is created by copying installation images from installationmedia to the hard disk of the lpp_source server. If disk space is limited on the server or ifan lpp_source is needed quickly, you can use a directory mounted from CD–ROMinstallation media as the lpp_source.


2. From the Resources menu, select New Resource.

3. Follow the wizard instructions to create the lpp_source resource.

Note: You can also define an lpp_source resource through the Configure NIMwizard, both when you are configuring your environment, and afterconfiguration.

From SMIT1. Mount the CD as a CDROM file system. The installation images can be found in the

/usr/sys/inst.images directory under the mount point of the CDROM file system.

2. To define the lpp_source using the directory of install images, enter the smitnim_mkres fast path.

3. Specify the name of the machine with the CD–ROM as the Server.

4. Specify CD_MountPoint/ usr/sys/inst.images as the location of the lpp_source, andleave the Source field blank.

From the Command Line1. Mount the CD as a CDROM file system. The installation images can be found in the

/usr/sys/inst.images directory under the mount point of the CDROM file system.

2. Define the lpp_source using the directory of install images for the location attribute. Donot specify a value for the source attribute, since an existing set of images will be used.With the CD mounted at /cdfs on the NIM master, to define an lpp_source namedcd_images, enter:

nim –o define –t lpp_source –a server=master \

–a location=/cdfs/usr/sys/inst.images cd_images


Establishing a Default NIM Route Between Networks

This procedure describes how to create default NIM routes for two Networks (for example,Network1 and Network3 ).

From Web-based System Manager1. Select the Networks container.

2. In the contents area, select any network.

3. From the Selected menu, choose Properties. The General page of the Propertiesnotebook for the selected network displays.

4. Select the NIM Routes tab. The NIM Routes page of the Properties notebook displays.

5. Use the NIM Routes page to add the default route.

From SMIT1. To create default NIM routes, enter the smit nim_mkdroute fast path.

2. In the displayed dialog fields, supply the values or accept the defaults. Use the helpinformation and the LIST option to help you.

From the Command LineTo create a default NIM route for a network, enter:

nim –o change –a routingseq_no=’default Gateway ’ NetworkObject

where default is the reserved keyword used by NIM to indicate a default route, andGateway is the host name (or IP address) of the interface that clients on NetworkObjectuse to contact other networks in the NIM environment.

For example, to establish default NIM routes for Network1 and Network3, enter:

nim –o change –a routing1=’default gw1_tok’ Network1

nim –o change –a routing1=’default gw1_fddi’ Network3

where gw1_tok is the host name of the default gateway for machines on Network1, andgw1_fddi is the host name of the default gateway for machines on Network3.

The detailed information for the network objects now shows the added default routes. Todisplay the detailed information for the two networks, enter:

lsnim –l Network1 Network3

which produces output similar to the following:

Network1:

class = networks

type = tok

net_addr = 9.101.1.0

snm = 255.255.255.0

Nstate = ready for use

prev_state = ready for use

routing1 = default gw1_tok

Network3:

class = networks

type = fddi

net_addr = 9.101.3.0

snm = 255.255.255.0


prev_state = information is missing from this

object’s definition

routing1 = default gw1_fddi


Establishing a Static NIM Route Between Networks

This procedure describes how to create a static NIM route between two networks (forexample, Network1 and Network3 ).

From Web-based System Manager1. Select the Networks container.

2. In the contents area, select any network.

3. From the Selected menu, choose Properties. The General page of the Propertiesnotebook for the selected network displays.

4. Select the NIM Routes tab. The NIM Routes page of the Properties notebook displays.

5. Use the NIM Routes page to add the static route.

From SMIT1. To create a static NIM route, enter the smit nim_mkroute fast path.

2. In the displayed dialog fields, supply the values or accept the defaults. Use the helpinformation and the LIST option to help you.

From the Command LineTo create a static NIM route between two networks, enter:

nim –o change –a routingseq_no=’ DestinationNetworkObject \

Gateway1 Gateway2 ’ NetworkObject

where Gateway1 is the host name of the interface that clients on NetworkObject use toget to DestinationNetworkObject, and Gateway2 is the host name that clients onDestinationNetworkObject use to get back to NetworkObject.

For example, to establish a NIM route between Network1 and Network3, enter:

nim –o change –a routing1=’Network3 gw1_tok gw1_fddi’ Network1

where gw1_tok is the host name of the gateway that machines on Network1 use tocommunicate with machines on Network3, and gw1_fddi is the host name of thegateway that machines on Network3 use to communicate with machines on Network1.

The detailed information for the network objects now shows the added routing attributes.

To display the detailed information about the two networks, enter:

lsnim –l Network1 Network3


The command produces output similar to the following:

Network1:

class = networks

type = tok

net_addr = 9.101.1.0

snm = 255.255.255.0


prev_state = ready for use

routing1 = Network3 gw1_tok

Network3:

class = networks

type = fddi

net_addr = 9.101.3.0

snm = 255.255.255.0


prev_state = information is missing from this object’s

definition

routing1 = Network1 gw1_fddi


Recovering the /etc/niminfo File

The /etc/niminfo file, which resides on the master and running NIM clients, is required torun NIM commands and perform NIM operations. If the /etc/niminfo file is accidentallydeleted, you can rebuild the file.

From Web-based System Manager1. Select the NIM container.

2. From the NIM menu, select Advanced Configuration ––> Rebuild MasterConfiguration File.

Note: The Configure NIM wizard will detect when you do not have a niminfo file,yet do have NIM database entries. The wizard queries whether it shouldrebuild the master configuration file.

From the Command LineEnter the following command from the master to rebuild the file:

nimconfig –r

To rebuild the /etc/niminfo file from a running NIM client, enter:

niminit –a master_port= PortNumber –a master= MasterHostName \

–a name= ClientMachineObjectName


Backing Up the NIM Database

To back up the NIM database, you will be prompted for the name of a device or a file towhich the NIM database and the /etc/niminfo file will be backed up. The level of theinstalled NIM master fileset will also be written to a file called /etc/NIM.level and saved inthe backup. A backup of a NIM database should only be restored to a system with a NIMmaster fileset which is at the same level or a higher level than the level from which thebackup was created.

From Web-based System Manager1. From the NIM container, from the NIM menu, select Back Up Database.

2. Use the dialog to specify the backup device or file.

From SMITTo back up the NIM database, enter the smit nim_backup_db fast path.

From the Command LineSave the following NIM files:

/etc/niminfo

/etc/objrepos/nim_attr

/etc/objrepos/nim_attr.vc

/etc/objrepos/nim_object

/etc/objrepos/nim_object.vc


Restoring the NIM Database and Activating the NIM Master

Note: A NIM database should only be restored to the same or later level of NIMthat was used for the backup.

From Web-based System Manager1. From the NIM container, from the NIM menu, select Restore Database.

2. Use the dialog to specify the restore device or file.

From SMITTo configure a NIM master from a NIM database backup, enter the smit nim_restore_dbfast path.

From the Command LineRestore the files saved in Backing Up the NIM Database.


Unconfiguring the NIM Master

This operation removes the NIM daemons from the system and removes all configurationfrom the NIM database. The NIM master should only be unconfigured if the NIMenvironment is to be completely redefined or if the NIM master fileset is to be removed fromthe system.

From Web-based System Manager1. From the NIM Container, from the NIM menu, select Unconfigure Environment.

2. You have the option to back up the NIM database before starting the unconfigure action.

From SMITTo unconfigure a NIM master, enter the smit nim_unconfig fast path.

The SMIT screen will prompt you to first back up your NIM database before unconfiguringthe NIM master.

From the Command LineTo unconfigure a NIM master, enter nim –o unconfig master.


Booting Diagnostics

Hardware diagnostics can be performed on all NIM clients using a diagnostic boot imagefrom a NIM server, rather than booting from a diagnostic tape or CD–ROM. This is useful forstandalone clients, because the diagnostics do not have to be installed on the local disk.Diagnostic support comes from a SPOT resource.

From Web-based System Manager1. Select the NIM container.

2. In the contents area, select the standalone, diskless, or dataless machine you want toenable for diagnostics boot.

3. From the Selected menu, choose Troubleshooting ––> Enable Diagnostic Boot.

4. Use the dialog to select a SPOT resource from which to boot.

From SMIT

Initiating the diag Operation from the Client1. Enter the smit nim_client_op fast path.

2. Select the diag operation from the displayed list of operations.

Initiating the diag Operation from the Master1. Enter the smit nim_mac_op fast path.

2. Select the machine object.

3. Select the diag operation from the list of operations.

From the Command LineTo perform the diag operation from the client, enter:

nimclient –o diag –a spot= SPOTName

To perform the diag operation from the master, enter:

nim –o diag –a spot= SPOTName MachineObjectName

Verifying the diag OperationAfter you have enabled the client to perform a diagnostic boot, you can verify the success ofthe operation by querying the client’s control state (Cstate).

On the client, enter:

nimclient –l –l ClientMachineObjectName

On the master, enter:

lsnim –l ClientMachineObjectName

If the operation is successful, output similar to the following is displayed:

Cstate = Diagnostic boot has been enabled

For the client to boot the diagnostics, you need to reboot the client. If it is a diskless or adataless client, you have already defined a network adapter as the default boot device(BOOTP request), so no additional action is required. For a standalone machine, the bootlist for normal boot lists the hard disk as the primary boot device, so you must follow theprocedure described in Booting a Machine Over the Network on page A-2.


Loading Diagnostics without the diag Operation

In addition to using the procedure in the previous section, diskless and dataless clients haveanother way of loading diagnostics from the network. You can boot a diskless or datalessclient from the network the same way you do for normal use, but with the machine’s keymode switch in the Service position. If the client’s key mode switch is in the Service positionat the end of the boot process, hardware diagnostics from the server’s SPOT are loaded. Ifa standalone client boots with the key mode switch in the Service position, the diagnostics(if installed) are loaded from the hard disk.


Booting in Maintenance Mode

If you need to perform maintenance on a standalone machine that is not part of the NIMenvironment, the system must be booted from a bootable tape or CD–ROM. This mayrequire connecting an external device. If the machine is part of a NIM environment, you canenter maintenance mode directly by enabling the maint_boot operation for a NIMstandalone machine.


2. In the contents area, select a target standalone machine you want to enable formaintenance boot.

3. From the Selected menu, choose Troubleshooting ––> Enable Maintenance Boot.

4. Use the dialog to select a SPOT resource from which to boot.

From SMIT

Initiating the maint_boot Operation from the Client1. Enter the smit nim_client_op fast path.

2. Select the maint_boot operation.

3. Select the SPOT to be used for the operation.

4. Press Enter to enable the client for maintenance boot.

Initiating the maint_boot Operation from the Master1. Enter the smit nim_mac_op fast path.

2. Select the client’s machine object.

3. Select the maint_boot operation.

4. Select the SPOT to be used for the operation.

5. Press Enter to enable the client for maintenance boot.

From the Command LineTo issue the maint_boot operation from the client, enter:

nimclient –o maint_boot –a spot= SPOTNAME

To issue the maint_boot operation from the master, enter:

nim –o maint_boot –a spot= SPOTNAME CLIENT

To verify that the maintenance boot operation worked:

1. On the client, enter:

nimclient –l –l ClientMachineObjectName

2. On the master, enter:

lsnim –l ClientMachineObjectName

If the operation was successful, the client’s Cstate output will look similar to the following:

Cstate = maintenance boot has been enabled

For the machine to boot into maintenance mode, follow the procedure for issuing theBOOTP request from the client. See Booting a Machine Over the Network for moreinformation about initiating a BOOTP request.


Using Maintenance Mode

After successfully booting and defining the console, the System Maintenance menu isdisplayed. The maintenance menu options and their descriptions are described below. Formore information about maintenance mode, see Accessing a System That Does Not Booton page 17-8.

Access a Root Volume Group6 This option allows you to activate the rootvolume group and start the maintenance shellwith a full set of commands.

Copy a System Dump to RemovableMedia

This option allows you to copy a previoussystem dump to external media.

Access Advanced MaintenanceFunction

This option allows you to start a maintenanceshell with a limited set of commands.


Secondary Adapter SupportPreviously, during a NIM rte BOS installation operation, only the network adapter andinterface used during BOS installation were configured. Using NIM secondary adapterdefinitions you can have additional network adapters and interfaces configured during aBOS installation or customized installation.

The nimadapters command parses a secondary adapter stanza file to build the filesrequired to add NIM secondary adapter definitions to the NIM environment as part of anadapter_def resource. The nimadapters command does not configure secondaryadapters. The actual configuration takes place during a nim –o bos_inst operation or a nim–o cust operation that references the adapter_def resource.

The secondary adapter stanza file is processed by the nimadapters command and turnedinto a file that contains one stanza for each secondary adapter or interface on the NIMclient. During a BOS installation, NIM processes this information and converts it into optionsand parameters that the mktcpip2 command can process. If a secondary adapter is alreadyconfigured in the requested manner, NIM does not reconfigure the secondary adapter.

Note: Before using the nimadapters command, you must configure the NIMmaster. For information on configuring the NIM master, refer to Configuringthe NIM Master and Creating Basic Installation Resources on page 23-3.

Secondary Adapter File RulesThe format of the secondary adapter file must comply with the following rules:

• After the stanza header, follow attribute lines of the form: Attribute = Value

• If you define the value of an attribute multiple times within the same stanza, only the lastdefinition is used.

• If you use an invalid attribute keyword, that attribute definition is ignored.

• Each line of the file can have only one header or attribute definition.

• More than one stanza can exist in a definition file for each machine host name.

• Each stanza for a machine host name represents a secondary adapter definition on thatNIM client. No two secondary adapter definitions for the same machine host name canhave the same location or interface_name. There should be only one definition peradapter or interface on a given NIM client.

• If the stanza header entry is the default keyword, this specifies to use that stanza for thepurpose of defining default values.

• You can specify a default value for any secondary adapter attribute. However, thenetaddr and secondary_hostname attribute must be unique. Also, the location andinterface_name must be unique on a NIM client.

• If you do not specify an attribute for a secondary adapter but define a default value, thedefault value is used.

• You can specify and change default values at any location in the definition file. After adefault value is set, it applies to all definitions following it.

• To turn off a default value for all following machine definitions, do not set the attributevalue in a default stanza.

• To turn off a default value for a single machine definition, do not set the attribute value inthe machine stanza.

• You can include comments in a client definition file. Comments begin with the #character.


• When parsing the definition file for header and attribute keywords and values, tabcharacters and spaces are ignored.

Note: During a nim –o bos_inst or nim –o cust operation, if NIM examinesthe configuration data on the client and determines that a secondaryadapter is already configured with precisely the attributes requested inthe adapter_def resource, this secondary adapter is not reconfigured.

Secondary Adapter File KeywordsThe secondary adapter file uses the following keywords to specify machine attributes:

Required Attributesmachine_type = secondary

Specifying the machine_type attribute as secondary clearly distinguishesthe nimadapters input from nimdef input. If a secondary adapters file ismistakenly passed to the nimdef command, the error can be detected.

netaddr Specifies the network address for the secondary adapter.

network_type = en | et | sn | mlSpecifies the type of network interface, which can be one of en, et, sn, orml.

subnet_mask Specifies the subnet mask used by the secondary adapter.

Optional Attributesattributes Blank–separated list of interface attributes and values. For example,

Attribute1 = Value1 Attribute2 = Value2. To see the list of attributes that canbe set for the requested interface, run the command lsattr –E –lInterfaceName.

cable_type Specifies the cable type (optional if network_type is en or et).

comments Specifies a comment to include in the secondary adapter definition.Enclose the comment string in quotation marks.

interface_name Specifies the name of the network interface for the secondary adapter (forexample, en1, sn0, ml0). Do not specify both location andinterface_name.

Note: The interface_name must be consistent with thenetwork_type.

location Specifies the physical location of the adapter corresponding to this networkinterface. Do not specify both the location and interface_name attributes.

Note: Except for the multilink pseudo–device, use of the locationattribute is highly recommended. If the location attribute isnot specified and the user adds multiple adapters or addsan adapter at the same time that the operating system isreinstalled, the adapter and network interface names mightbe reassigned by the operating system in unexpectedways.

media_speed Specifies the media speed (optional if network_type is en or et).

secondary_hostnameHost name to save in the /etc/hosts file with the netaddr attribute. Thishost name is not set using the hostname command or uname –Scommand.


Secondary Adapter File Stanza ErrorsA secondary adapter stanza causes an error under any of the following conditions:

• The host name that was used in the stanza header for the definition cannot be resolved.

• A required attribute is missing.

• An invalid value was specified for an attribute.

• An attribute mismatch occurs. For example, if the network_type is not en or et, youcannot specify cable_type = bnc or media_speed = 1000_Full_Duplex.

• The stanza contains both a location attribute and an interface_name attribute.

• Secondary adapter definitions occur multiple times for the same adapter location and thesame host name.

• Secondary adapter definitions occur multiple times for the same interface_name andthe same host name.

If a secondary adapter stanza is incorrect, the errors are reported, the stanza is ignored,and the following input is processed without regard to the incorrect stanza.

Example Secondary Adapter FileThe following is an example of a secondary adapter file:

# Set default values.

default:

machine_type = secondary

subnet_mask = 255.255.240.0

network_type = en

media_speed = 100_Full_Duplex

# Define the machine ”lab1”

# Take all defaults and specify 2 additional attributes.

# Unlike the case of the client definitions that are input to the

# nimdef command, the secondary adapter definition includes at least

# one required field that cannot be defaulted.

lab1:

netaddr = 9.53.153.233

location = P2–I1/E1

# Change the default ”media_speed” attribute.

default:

media_speed = 100_Half_Duplex

# define the machine ”test1”

# Take all defaults and include a comment.

test1:

comments = ”This machine is a test machine.”

Examples1. To preview the client definition file secondary_adapters.defs, type:

nimadapters –p –f secondary_adapters.defs adapter_def

2. To add the NIM secondary adapters described in the secondary adapters definition filesecondary_adapters.defs, type:

nimadapters –d –f secondary_adapters.defs adapter_def

3. To define the NIM secondary adapters for a client called pilsner, type:

nimadapters –d \

–a info=”en,P2–I1/E1,N/A,1000_Full_Duplex,9.53.153.233,255.255.254.0” \

–a client=pilsner adapter_def

26-1Additional Topics

Chapter 26. Additional NIM Topics

This chapter describes Network Installation Management (NIM) topics that are not part ofthe usual installation procedures.

The following topics are included:

• NIM Master Management Tasks on page 26-2

• NIM Name Resolution on page 26-4

• Booting a FDDI Interface Over a Router on page 26-5

• Default Paging Space During BOS Installation Through NIM on page 26-6

• Migrating Diskless and Dataless Clients and NIM SPOTS on page 26-7

• Defining the NIM Environment Using the nimdef Command on page 26-8

• Name Requirements for NIM Object Definitions on page 26-9

• Interacting with the Dynamic Host Configuration Protocol on page 26-10

• Creating File Resources in the root Directory on page 26-11

• Restricting NIM Client Resource Allocation on page 26-12

• Preventing Machines from Adding Themselves as Clients on page 26-13

• Disabling Client CPU ID Validation on page 26-14

• Exporting NIM Resources Globally on page 26-15

• Creating Network Boot Images to Support Only the Defined Clients and Networks onpage 26-16

• Updating a Spot with New Device Support for a New Level of AIX on page 26-17

• Tuning Client–Request Processing on page 26-18


NIM Master Management TasksThe following tasks can be performed on the NIM master:

• Deactivating the NIM Master and Removing the NIM Master Fileset on page 26-2

• Increasing the Number of Hosts to Which NIM Can NFS–Export a Resource on page26-2

• Controlling the Asynchronous Behavior of NIM Operations on page 26-3

• Suppressing Output from NIM Operations on page 26-3

• Reducing Space Requirements for NIM Resources on page 26-3

Deactivating the NIM Master and Removing the NIM Master Fileset

After the NIM master fileset has been installed, the master activated, and the master objectdefined in the NIM database, this object, and hence the master fileset itself, cannot beremoved. The master must be deactivated before the NIM master fileset can be removed.

To deactivate the master using Web–based System Manager, see Unconfiguring the NIMMaster.

To use the command line to deactivate the master and remove the NIM master fileset, enter:

nim –o unconfig master

installp –u bos.sysmgt.nim.master

Increasing the Number of Hosts to Which NIM Can NFS–Export aResource

By default, when NIM exports a file or directory through NFS during resource allocation, itcreates an entry in the /etc/exports file granting the target host both client mount accessand root access for root users. As a result, when exporting to numerous clients, the limit onthe length of a line in the exports file (32767 characters) may be exceeded, resulting infailure.

NIM provides an option to decrease the line length of an allocation entry in an NFS exportsfile by approximately one–half, effectively permitting files to be allocated to a greater numberof hosts. This action has the side effect of increasing the number of machines permitted in aNIM machine group. NIM achieves this by only granting root access to allocation targethosts. The client mount access list is not created, which allows any machine to mount theresource, but still restricts root access to NIM clients only. NFS permits no more than 256host names in a root exports file entry.

To enable this mode of operation, set the restrict_nfs_exports attribute to no on themaster’s NIM object. Use the change operation as follows:

nim –o change –a restrict_nfs_exports=no master

To restore client mount access restrictions, set restrict_nfs_exports to yes with thechange operation.

For information about how to export NIM resources globally, see Exporting NIM ResourcesGlobally on page 26-15.


Controlling the Asynchronous Behavior of NIM Operations

Certain NIM operations are asynchronous, meaning that NIM master might initiate theoperation on the client, but does not wait for the operation to finish. The reason for thisasynchronous behaviour is because the NIM operation running on the client is typicallytime–consuming. An example of an asynchronous operation is the bos_inst operation.Examples of synchronous operations are the cust, maint, and lppchk operations on asingle machine target. However, these operations, when applied to members of a machinegroup, are asynchronous. The nim command initiates these operations on each member ofthe group without waiting for the operation to finish.

If desired, the asynchronous behavior of the cust, maint, and lppchk operations can becontrolled by setting the async attribute on the command line. For example, to ensure thatthe execution of a customization script identified by the NIM resource script1 is executedcompletely on a given member of the group MacGrp1 before initiating execution of thescript on the next member of the group, enter the following:

nim –o cust –a script=script1 –a async=no MacGrp1

To force the master to not wait for the customization operation to finish when running thescript on machine Standalone1 that is not part of a machine group, enter:

nim –o cust –a script=script1 –a async=yes Standalone1

Suppressing Output from NIM Operations

By default, progress messages are displayed by the nim command operating on machinegroups to inform the user of how much processing remains. Similarly, the output from theinstallation and customization programs invoked by the cust and maint operations onSPOTs and machines is also displayed. This output can be suppressed by setting theshow_progress attribute to no on the command line. For example, to indicate to NIM notto display output from the installp command when updating the machine Standalone1with software from the lpp_source named images1, enter the following command:

nim –o cust –a show_progress=no –a lpp_source=images1 \

–a fixes=update_all Standalone1

Reducing Space Requirements for NIM Resources

It is not unusual for resources such as the SPOT and lpp_source to take several hundredmegabytes of storage space on a NIM server. By creating /usr SPOTs and definingCD–ROM file–system directories as lpp_sources, space consumption can be reducedsignificantly on resource servers.

A /usr SPOT can be created from the /usr file system of the NIM master or any NIM client.The AIX system files for the BOS are already installed, so only software for additional devicesupport will be added to the system. The resulting system ultimately has more softwareinstalled on it than it needs to run, but far less disk space is used than otherwise would havebeen, had a non–/usr SPOT been created on the same system. For more information oncreating /usr SPOT resources, see SPOT (Shared Product Object Tree) Resource andDefining /usr versus non–/usr SPOTs.

A directory on the AIX product CD can be mounted and defined as an lpp_source,eliminating the need to copy installation images to the hard disk of a resource server. Thedefined lpp_source contains all the images available on the CD, but the CD must remainmounted at the server for the lpp_source to be usable in NIM operations. For moreinformation about using a CD–ROM file system as an lpp_source, see Defining anlpp_source on CD–ROM versus Disk.


NIM Name Resolution

NIM relies on standard AIX library routines to perform name resolution. If a networkenvironment uses multiple sources for name resolution, NIM will resolve host names byquerying the sources in whatever order is specified for the system. For example, if a systemis configured to resolve host names by first querying NIS, then BIND/DNS, then a local/etc/hosts file, NIM will also follow that order when resolving client host names.

Problems may result if the NIM master and the NIM clients use different orders whenquerying sources for name resolution. Problems may also arise if a name service isavailable to one machine but not to another, causing different name resolution sources to beused.

Note: Mixing BIND/DNS, which is not case–sensitive, with NIS, which iscase–sensitive, may result in problems.

It is possible to override the default system–wide order that AIX and NIM use when queryingsources for host name resolution. This can be done by setting the NSORDER environmentvariable in the environment where NIM commands are being run. For example, to configurethe environment to query NIS first, then BIND/DNS, then a local /etc/hosts file, type thefollowing on the command line where NIM operations are being run:

export NSORDER=nis,bind,local

For more information on TCP/IP name resolution, refer to AIX 5L Version 5.2 SystemManagement Guide: Communications and Networks.


Booting a FDDI Interface Over a Router

Boot over a router on a FDDI interface only if the router supports all–route broadcast.Booting over a router that does not support all–route broadcast on a FDDI interface may faildue to known limitations of these router types.


Default Paging Space During BOS Installation Through NIMIn AIX 4.3 or later, default paging space is set by the BOS installation process wheninstalling through NIM. Default paging space is set by the BOS installation process, if thefollowing conditions are met:

• The method of installation is overwrite.

• Neither an image_data resource nor an image.data file on the diskette is specified forthe installation.

• The source of the BOS image is not a mksysb image.

• The source of the BOS image is a SPOT, and the default image.data file contains morethan one entry for paging. This file is located at:

(spot_location)/lpp/bosinst/image_template

• The source of the BOS image is a SPOT, and the LPs value for the single paging entry isset to the default value of 16.

The default paging size is calculated from the smaller value of optimal_ps andrecommended_ps where:

• RAM = amount of memory on the target system measured in megabytes (MB).

• optimal_ps = maximum between RAM and (0.2 size of rootvg)

• IF CDE (Common Desktop Environment) is installed, recommmended_ps =

– amount of RAM is less than 32 MB, then recommended_ps = 3 * RAM

– amount of RAM is 32 MB or more, then recommended_ps = RAM + 64 MB

• IF CDE (Common Desktop Environment) is not installed, recommmended_ps =

– amount of RAM is less than 32 MB, then recommended_ps = 2 * RAM

– amount of RAM is 32 MB or more, then recommended_ps = RAM + 32 MB

The default paging space set by this process is never greater than 512 MB.


Migrating Diskless and Dataless Clients and NIM SPOTS

Migration to a new release of AIX is not supported for diskless and dataless clients. Also,migration of a SPOT that is not a converted /usr file system is not supported.

After migrating a machine that is a SPOT server to a new release of AIX, you must removeand redefine the SPOT in order to also bring it to the new AIX level.

To remove and redefine the SPOT, enter:

nim –o remove SPOT_name

nim –o define –t spot –a location= SPOTDirectory \

–a server= SPOTServer –a source= SPOTSource SPOTName

A /usr SPOT served by a client in the NIM environment can be reinstalled with a new levelof AIX using the migration procedure, but the SPOT object must be removed and thenredefined after the migration completes. Any diskless or dataless clients served by thatSPOT must be reinitialized. To reinitialize diskless and dataless clients after migrating a /usrSPOT server, deallocate, then reallocate the root resources, and then perform the dtls_initor dkls_init operation accordingly.

To reinitialize diskless and dataless clients, enter:

nim –o reset –F ClientName

nim –o deallocate –a root= RootResourceName ClientName

nim –o allocate –a root= RootResourceName ClientName

nim –o dkls_init ClientName

Attention: Any customization that was done previously will be erased, because deallocatingthe root resource will delete all the files in the root directory.


Defining the NIM Environment Using the nimdef Command

The nimdef command assists administrators when defining complex NIM environments andadding large numbers of client machines.

The nimdef command solves a common usability problem when defining large NIMenvironments.

Regardless of how well a NIM environment is understood, it can be a very time–consumingprocess to execute all the commands necessary to define it. If NIM could process a simpledefinition file for configuration of the NIM environment, a great deal of time could be savedthat would otherwise be spent defining each network and machine manually.

The nimdef command reads a definition file for input. The definition file is in a structuredstanza format. Each stanza describes a machine that will be added to the NIM environment.Included in the stanza is information about the machine’s network adapter and routingconfiguration. Based on the supplied information, the nimdef command can determine theremaining information needed to define both networks and machines in the NIMenvironment.

For more information, see the nimdef command. For a sample definition file for the nimdefcommand, see Sample Files on page 28-1.


Name Requirements for NIM Object Definitions

The name that you give a NIM object will be used in all future operations involving thatobject. This name must be unique among NIM objects, and it must adhere to certainrestrictions:

• It must have between 1 and 39 characters.

• Valid NIM name characters include the uppercase and lowercase letters of the alphabet,the numbers 0–9, and the underscore character.

• Invalid NIM name characters include the dot character, all shell metacharacters, all filesystem metacharacters, and all regular expression metacharacters.


Interacting with the Dynamic Host Configuration Protocol

Select your NIM master to be the same system as the Dynamic Host Configuration Protocol(DHCP) server when using NIM in an environment that uses DHCP. Use host nameswhenever possible when defining NIM machine objects.

For more information, refer to DHCP and Network Installation Management (NIM)Interactions and Suggestions in AIX 5L Version 5.2 System Management Guide:Communications and Networks.


Creating File Resources in the root Directory

Due to a limitation in NFS, file resources, such as bosinst_data and script resourcescannot be created in the root directory (” / ”) of a resource server.


Restricting NIM Client Resource AllocationNIM provides client machines with the capability of allocating and using any resource in theNIM environment. In some tightly controlled NIM environments, administrators may not wantclients to be able to access all resources at all times. To control client–resource allocation, aNIM administrator can use the client_alloc attribute. The restrictions placed by theclient_alloc attribute will prevent clients from allocating and using resources, but the NIMmaster will continue to have the full capability of performing operations on clients.

Note: This task is not supported by Web–based System Manager.

From SMITNIM client–allocation restrictions can be changed from the SMIT interface by typing theSMIT fast path:

smit nim_control_alloc

From the Command LineTo restrict all clients from being able to use any resources, set the attribute client_alloc=noon the NIM master:

nim –o change –a client_alloc=no master

To restrict a particular client from being able to use any resources, set the attributeclient_alloc=no on the client:

nim –o change –a client_alloc=no clientname

To restrict all clients from being able to use a particular resource, set the attributeclient_alloc=no on the resource:

nim –o change –a client_alloc=no resourcename

To lift the restrictions on client–resource allocation, remove the client_alloc attribute bysetting it to yes for the applicable object:

nim –o change –a client_alloc=yes master

nim –o change –a client_alloc=yes clientname

nim –o change –a client_alloc=yes resourcename


Preventing Machines from Adding Themselves as ClientsMachines may add themselves as clients in NIM environments by using the niminitcommand and specifying the hostname of a NIM master. In some environments,administrators may want total control over which machines are added as clients of theirmasters. To prevent clients from adding themselves to a NIM environment, an administratorcan use the client_reg attribute.

Note: This task is not supported by Web–based System Manager.

From SMITThe option to allow clients to add themselves to a NIM environment can be changed fromthe SMIT interface by typing the SMIT fast path:

smit nim_client_reg

From the Command LineTo prevent machines from adding themselves as clients in a NIM environment, set theattribute client_reg=no on the NIM master:

nim –o change –a client_reg=no master

To allow machines to add themselves as clients of a NIM master, remove the client_regattribute by setting it to yes on the master:

nim –o change –a client_reg=yes master


Disabling Client CPU ID ValidationThe CPU ID of a NIM client is stored in the NIM database so that the master can performverification that NIM client commands are coming from the machines that were originallyregistered as clients. A NIM administrator would not want this CPU ID validation to beperformed in the following situations:

• When the hardware of a client machine is changed, giving the client a new CPU ID.

• When a single client definition is used to install different machines, as on a preinstallassembly line.

From Web-based System ManagerTo enable or disable NIM client CPU ID validation from the NIM application:

1. From the NIM menu, select Advanced Configuration ––> Control Client CPU IDValidation.


From SMITManage the client CPU ID validation from the SMIT interface by typing the SMIT fast path:

smit nim_cpuid_validate

From the Command LineClient CPU ID validation can be managed on the NIM master by using the validate_cpuidattribute.

To disable client CPU ID validation, set the attribute validate_cpuid=no on the NIM master:

nim –o change –a validate_cpuid=no master

To perform client CPU ID validation, remove the validate_cpuid attribute from the masterby setting it to ”yes”:

nim –o change –a validate_cpuid=yes master

Attention: The value of the validate_cpuid attribute should not be changed whileoperations are being performed on NIM clients because it could potentially disrupt clientcommunications for active machines.


Exporting NIM Resources GloballyWhen resources are allocated for use during NIM operations, they are NFS–exported to theclient machines where the operations will be performed. If operations are performedsimultaneously on many different clients, the /etc/exports and /etc/xtab files may becomevery large on the resource servers. This may cause size limits to be exceeded in the files,and it may also negatively affect NIM performance as the files are locked and modified foreach resource allocation or deallocation.

In environments where administrators are not concerned about who has access to the NIMresources, they may set an option to globally export the resources and thereby eliminate therepeated updates to the /etc/exports and /etc/xtab files. The only resources that may notbe globally exported are those that are used exclusively by diskless and dataless clients.The global export of a NIM resource will make it readable by any machine in the network,not just those in the NIM environment. The resource will be globally exported as long as it isallocated to any client. When the resource is deallocated from all clients, it is unexported.

From Web-based System ManagerTo enable or disable global export of NIM resources from the NIM application:

1. From the NIM menu, select Advanced Configuration ––> Export NIM ResourcesGlobally.


From SMITTo manage global exporting of NIM resources from the SMIT interface, type the SMIT fastpath:

smit nim_global_export

From the Command LineGlobal exporting of NIM resources for use by clients can be managed with theglobal_export attribute.

To enable global exporting of NIM resources, set the attribute global_export=yes on theNIM master:

nim –o change –a global_export=yes master

To disable global exporting of NIM resources, remove the global_export attribute from themaster by setting it to no:

nim –o change –a global_export=no master

Do not change the enablement and disablement of global exports when there are resourcesallocated to clients because this could lead to situations where resources are exported withincorrect permissions. All NIM operations should be completed and resources deallocatedbefore any attempts are made to change the global_export value. If resources arecurrently allocated to clients, the nim command will fail to change the global_export value.


Creating Network Boot Images to Support Only the DefinedClients and Networks

When a SPOT resource is created, network boot images are created in the /tftpbootdirectory to support certain NIM operations.

NIM only creates network boot images to support clients and networks that are defined. If anew client is defined and there is no network boot image already created for it in theenvironment, then the boot image will not be created until either the SPOT is allocated tothe client or a check operation is performed on the SPOT to rebuild the boot images.

When clients are removed from the NIM environment, boot images are not automaticallyremoved. To remove boot images that are no longer necessary for a NIM environment, thelist of required machine–network combinations in the environment must be rebuilt. The bootimages must then be rebuilt for each SPOT.

From Web-based System ManagerTo limit or enable boot image creation according to whether the interface is defined from theWeb-based System Manager application:

1. From the NIM menu, select Advanced Configuration ––> Control Network BootImage Creation.


From SMITTo manage the creation of boot images from the SMIT interface, type the SMIT fast path:

smit nim_control_boot

From the Command LineTo rebuild the list of machine types and networks that must be supported by network bootimages in the NIM environment, perform a change operation on the NIM master with theif_discover=yes attribute:

nim –o change –a if_discover=yes master

To rebuild network boot images from a SPOT, perform a check operation on the SPOT withthe force option:

nim –Fo check spot_name

If an administrator prefers to have NIM always create all possible boot images from theSPOT resources, the if_prebuild=yes attribute can be specified on the master:

nim –o change –a if_prebuild=yes master

To return NIM to the behavior of creating only the boot images that are required for theenvironment, remove the if_prebuild attribute from the master by setting it to ”no”:

nim –o change –a if_prebuild=no master


Updating a Spot with New Device Support for a New Level ofAIX

A NIM SPOT may be updated from one level of AIX to another using the update_all optionof the NIM cust operation. This process will update all current SPOTs with the latest level ofcode on the installation media. However, this process will not automatically install newsoftware packages or device drivers from the installation media.

Machines in the NIM environment that are being upgraded to a new level of AIX require thatnew applicable device support be updated for any existing NIM SPOTs intended to supportnetwork boot and installation. This must be done after the SPOT is updated to the new levelof AIX.

The new device support can be installed in the SPOT using NIM’s cust operation,specifying the desired device–specific filesets in an installp_bundle resource or by usingthe filesets attribute. Alternatively, a fileset name of devices can be specified as the valueof the filesets attribute to install all devices on the installation media. For further detailsabout the cust operation, see cust on page 27-43.


Tuning Client–Request ProcessingFor large installation environments, NIM can be scaled to support anywhere from 20 to 150client requests simultaneously. NIM scaling is done by enabling the multithreaded option onthe nimesis daemon. The multithreaded option provides better handling of the volume ofclient information change requests and client state changes. Without the use of themultithreaded option, the NIM master can become overloaded by activity on the NIMdatabase and the number of active processes, resulting in simultaneous failures during theinstallation of a large number of client machines.

The multithreaded nimesis daemon will serialize and buffer NIM client requests to protectthe NIM master from process overload, without causing significant performancedegradation. The user must understand that many of the client information changes will notbe reflected in the NIM database. The most recent information changes for any client,however, are eventually processed. Debugging of failed or hung clients will not be adverselyaffected.

The number of threads assigned to this daemon determines how many simultaneous NIMclient requests can be handled in the NIM environment. Because most of the NIM clientrequests are processed rapidly, it is not necessary to have one thread for every clientinstalling. The number of threads needed to support the activities in a NIM environment isdependent upon several items. The following should be considered when determining thenumber of threads:

• Number of clients that will be operated on at the same time

• Processing capacity of the NIM master machine

• What type of operations are planned

In general, one thread can support two to four clients that are installing BOS at the sametime. For example, when installing 150 machines, 50 to 75 threads is sufficient. The numberof threads is highly dependent on the processing power of the NIM master machine, andslower master machines may require more threads.

For smaller NIM environments, enabling the multithreaded daemon can monopolize systemresources on the master that will not be used. For example, when installing 50 machinessimultaneously, 20 to 25 threads or even the single–threaded daemon would suffice.

Note: The multithreaded option alone will not allow more machines to be installedsimultaneously. The multithreaded option should be used in conjunctionwith global export of NIM resources, distribution of NIM resourcesthroughout the NIM environment, and a network environment capable ofhandling a large volume of throughput.

From SMITTo tune client–request processing from the SMIT interface, type the SMIT fast path:

smit nim_tune_nimesis

From Web-based System ManagerTo tune client–request processing from the NIM application:

1. From the NIM menu, select Advanced Configuration––>Tune Client RequestProcessing.



From the Command LineThe max_nimesis_threads attribute can be used to tune client–request processing. Toenable the multithreaded nimesis daemon, set a value to the max_nimesis_threadsattribute on the NIM master using the following command:

nim –o change –a max_nimesis_threads= value master

Note: The range for the value attribute above is 20 to 150.

To disable the multithreaded nimesis daemon, set a null value to themax_nimesis_threads attribute on the NIM master:

nim –o change –a max_nimesis_threads=”” master


27-1Network Installation Management Concepts

Chapter 27. Network Installation Management Concepts

This chapter discusses the concepts required to understand the operation of NetworkInstallation Management (NIM). To use all the available features in NIM, you shouldunderstand various components of AIX installation. The details discussed in this chapterfocus on command–line operations, but the information is applicable to the other NIMinterfaces as well. Use this chapter as reference material to supplement the online helpavailable in the other interfaces.

This chapter contains the following topics:

• NIM Machines on page 27-2

• NIM Networks on page 27-10

• NIM Resources on page 27-15

• NIM Operations on page 27-33

• NIM Groups on page 27-56


NIM Machines

The types of machines that can be managed in the NIM environment are standalone,diskless, and dataless clients. This section describes the differences between the machines,the attributes required to define the machines, and the operations that can be performed onthem. The NIM environment is composed of two basic machine roles: master and client.The NIM master manages the installation of the rest of the machines in the NIMenvironment. The master is the only machine that can remotely run NIM commands on theclients. All other machines participating in the NIM environment are clients to the master,including machines that may also serve resources.

NIM Operations on Client MachinesThere are unique operations to initialize the different client configurations. NIM checks thatthe operation is a valid operation for a specific client configuration. The following tableshows the operations that can be performed on the different client configuration types.

NIM Operation Machine Configuration

Standalone Diskless Dataless

bos_inst x

dkls_init x

dtls_init x

diag x x x

cust x

fix_query x

lppchk x

maint x

maint_boot x

reset x x x

check x x x

showlog x x x

reboot x x x

For more information about NIM operations, see NIM Operations.

Defining NIM Clients

Standalone, diskless, and dataless clients are defined in the NIM environment using theNIM define operation. The command line syntax is as follows:

nim –o define –t MachineType –a Attribute = Value ...

MachineName


where the following attributes are required:

–t MachineType6 Specifies the type of machine being defined. Validvalues are standalone, diskless, and dataless.

–a if= Value ... Stores network interface information for a NIM client,and requires a sequence number when specified. Thevalue for this attribute consists of three required valuesand a fourth, optional value:

Value 1Specifies the name of the NIM network to which thisinterface connects. If the name of the NIM network isunknown, then the find_net keyword can be used tomatch the client’s IP address to a defined NIMnetwork. If the find_net keyword is used, but NIMdoes not find a matching network, the optionalnet_definition attribute should be used to define thenetwork, as well.

Value 2Specifies the host name associated with thisinterface.

Value 3Specifies the network adapter hardware address ofthis interface. A value of 0 can be specified unlessbroadcasting is used for network boot of the client.

Value 4Specifies the logical device name of the networkadapter used for this interface. If this value is notspecified, NIM uses a default based on the type ofnetwork interface defined. This field is required whenthe client is defined on a heterogeneous network.

This attribute requires a sequence number for NIMto distinguish between multiple network interfaces.Because machines can be multihomed, NIM allowsmore than one if attribute per machine.

The following attributes are optional:

–a ring_speed= Value Specifies the ring speed of the client’s token–ringadapter. This value is required if the client’s NIMnetwork is token–ring. This attribute requires asequence number for NIM to distinguish between ringspeeds for multiple interfaces on the machine.

–a cable_type= Value Specifies the cable type of the client’s ethernet adapter.This value is required if the client’s NIM network isEthernet. This attribute requires a sequence number forNIM to distinguish between cable types for multipleinterfaces on the machine.

–a platform= Value Specifies the platform of the machine being defined.The default value is platform=chrp. Run the bootinfo–p command on a running machine to determine itsplatform.

–a netboot_kernel= Value Specifies the kernel type of the client. Valid values areup for uniprocessor machines and mp formultiprocessor machines. The default value isnetboot_kernel=up.


–a iplrom_emu= Value Specifies the device that contains the IPL ROMemulation software. IPL ROM emulation is required formachines that do not have bootp–enabled IPL ROM.

–a net_definition= Value ... Defines a NIM network to be associated with the clientbeing defined. The value for this attribute consists oftwo required values and three optional values:

Value 1 = NetworkType (required)Specified values are tok, ent, fddi, and generic.

Value 2 = SubnetMask (required)Specifies the dotted decimal mask for the network.

Value 3 = ClientGateway (optional)Specifies the IP address or host name of the defaultgateway used by the machine being defined tocommunicate with the NIM master.

Value 4 = MasterGateway (optional)Specifies the IP address or host name of the defaultgateway used by the NIM master to communicatewith clients on other subnets.

Value 5 = NetworkName (optional)Specifies a name to be given to the NIM definitioncreated for the network. (Otherwise, a unique defaultvalue is assigned.)

When specifying the net_definition attribute to createor change a machine definition, the find_net keywordmust be specified as the first component of the ifattribute for the machine. The net_definition attributemay also be specified when defining additional NIMinterfaces (if attributes) for machine definitions.

–a cpuid= Value Specifies the CPU ID of the machine being defined.This attribute can be used for client verification duringNIM operations. To display the CPU ID on a runningmachine, use the uname –m command. This field isoptional and will be automatically set the first time aclient communicates with the NIM master.

–a master_port= Value Specifies the port number used by the NIM master forsocket communication with the clients. The defaultmaster port number is 1058.

–a registration_port= Value Specifies the port number used by clients to registerthemselves with the NIM master. The defaultregistration port number is 1059.

–a group= Value Specifies a machine group to which the client should beadded. The group will be defined if it does not exist.

–a comments= Value Provides comments about the client being defined.

–a verbose= Value Displays information for debugging. Use verbose=5 toshow maximum detail.


Standalone Clients

Standalone NIM clients are clients with the capability of booting and running from localresources. Standalone clients mount all file systems from local disks and have a local bootimage. Standalone clients are not dependent upon network servers for operation.

Network Booting a Standalone Client

Although an installed standalone client is capable of booting from the local disk, it may benecessary to perform a network boot of the client for certain NIM operations. Clients mustboot over the network in order for NIM to perform a BOS installation (bos_inst) of the clientor to boot into maintenance mode (maint_boot) and diagnostics (diag). For instructions onbooting a client over the network, see Booting a Machine Over the Network on page A-2.

Managing Software on Standalone Clients

The AIX Base Operating System can be installed directly on standalone clients using theNIM bos_inst operation. Additional software and updates can be installed and managed onstandalone clients using the NIM cust and maint operations. For more information aboutthese and other operations, see NIM Operations.

Diskless and Dataless Clients

Diskless and dataless clients are machines that are not capable of booting and runningwithout the assistance of servers on a network. As their names imply, diskless clients haveno hard disk, and dataless clients have disks that are unable to hold all the data that may berequired for operation. Diskless machines must mount paging space and all file systemsfrom remote servers. Dataless machines can only use a local disk for paging space and the/tmp and /home file systems. Neither diskless nor dataless clients have a local boot image,and they must boot from servers on the network.

Defining a machine as diskless or dataless has the following advantages:

• Cost savings

No hard disk is required for diskless clients. Only a small hard disk is needed fordataless clients.

• Manage software configurations on machines

On diskless and dataless clients, the file system containing the BOS is mounted from aserver. All client systems that mount the same file system for BOS run from identicalsoftware.

• Manage storage of user data

User data for diskless and dataless clients are stored on remote servers. A systemadministrator can manage storage allocation and data backups for the client machinesby managing the data on the server, rather than on each machine separately.


Required and Optional Resources for Diskless and Dataless Clients

The file systems that are mounted by the diskless and dataless client machines are treatedas resources in the NIM environment. Like other resources, they exist on a server in theNIM environment, and they are NFS–exported to the clients that use them.

The following resources are managed by NIM to support diskless and dataless clients:

boot Defined as a network boot image for NIM clients. The boot resourceis managed automatically by NIM and is never explicitly allocated ordeallocated by users.

SPOT Defined as a directory structure that contains the AIX run–time filescommon to all machines. These files are referred to as the usr partsof the fileset. The SPOT resource is mounted as the /usr file systemon diskless and dataless clients.

Contains the root parts of filesets. The root part of a fileset is the setof files that may be used to configure the software for a particularmachine. These root files are stored in special directories in theSPOT, and they are used to populate the root directories of disklessand dataless clients during initialization.

The network boot images used to boot clients are constructed fromsoftware installed in the SPOT.

A SPOT resource is required for both diskless and dataless clients.

root Defined as a parent directory for client ” / ” (root) directories. Theclient root directory in the root resource is mounted as the ” / ” (root)file system on the client.

When the resources for a client are initialized, the client rootdirectory is populated with configuration files. These configurationfiles are copied from the SPOT resource that has been allocated tothe same machine.

A root resource is required for both diskless and dataless clients.

dump Defined as a parent directory for client dump files. The client dumpfile in the dump resource is mounted as the dump device for theclient.

A dump resource is required for both diskless and dataless clients.

paging Defined as a parent directory for client paging files. The client pagingfile in the paging resource is mounted as the paging device for theclient.

A paging resource is required for diskless clients and optional fordataless clients.

home Defined as a parent directory for client /home directories. The clientdirectory in the home resource is mounted as the /home file systemon the client.

A home resource is optional for both diskless and dataless clients.

shared_home Defined as a /home directory shared by clients. All clients that use ashared_home resource will mount the same directory as the /homefile system.

A shared_home resource is optional for both diskless and datalessclients.


tmp Defined as a parent directory for client /tmp directories. The clientdirectory in the tmp resource is mounted as the /tmp file system onthe client.

A tmp resource is optional for both diskless and dataless clients.

resolv_conf Contains nameserver IP addresses and a network domain name.

Unlike the other resources used by diskless/dataless clients, theresolv_conf resource does not remain mounted by the client.Instead, it is copied to the /etc/resolv.conf file in the client’s rootdirectory.

A resolv_conf resource is optional for both diskless and datalessclients.


Initialization of Diskless and Dataless Clients

Diskless and dataless clients are not installed in the same way as standalone machines.Instead, they are initialized. Initialization of diskless and dataless clients involves severalphases of operation:

Resource Allocation The resources required to support a diskless/datalessclient must be allocated to the client before or during theinitialization operation.

If the resource is a parent directory of client directories, theallocation will create an empty subdirectory for the client.The client subdirectory is then NFS–exported to the client.The client subdirectories are not populated until theinitialization is actually performed.

Client Initialization The dkls_init and dtls_init operations are used in NIM toinitialize the resources for client use.

Among the operations performed during client initializationare the following:

• The boot image is made available to the client forperforming a network boot.

• The root files, which are used for machine–specificcustomization, are copied into the client’s subdirectory inthe root resource. The files that are copied into the clientroot directories come from the SPOT resource that hasbeen allocated to the client.

• The /tftpboot/ Client.info file is created on the bootserver (which is the SPOT server). This file containsinformation that will be needed by the client during thestart–up configuration processing to successfullyconfigure as a diskless or dataless client.

The following are some of the variables defined in theClient.info file:

export NIM_CONFIGURATION=diskless

export RC_CONFIG=rc.dd_boot

export ROOT=Host:Client_Root_Directory

export DUMP=Host:Client_Dump_Directory

export SPOT=Host:SPOT_Location

The paging location is set in the client’s root directory inthe /etc/swapspaces file.

Network Boot of the Client The client machine is booted over the network usingstandard bootp procedures for the machine type. Theclient obtains the boot image and begins running amini–kernel in a file system in RAM.

The client tftp’s the Client.info file from the /tftpbootdirectory on the SPOT server. The information in theClient.info file is used to properly configure the client as adiskless or dataless machine.

The remote file systems are mounted from the resourceservers.

If the client is a dataless client, and no paging, tmp,home, or shared_home resource is allocated, then theclient will create the missing file system on the local harddisk.


Managing Software on Diskless and Dataless Clients

The /usr and root file systems of diskless and dataless clients are resources that havebeen mounted from a server. Therefore, in order to install or uninstall software on a disklessor dataless client, the processing must actually occur on the resources that the clients use.

The SPOT contains the directory structure for an installed /usr file system. It also containssubdirectories for the ”root” parts of installed filesets. Because the SPOT contains both usrand root files, software maintenance must be performed on the SPOT in order to updatethe software that is running on the clients. Such actions must be performed using the NIMcust and maint operations. For more information about the cust and maint operations, seeNIM Operations.

If the SPOT is currently allocated for client use, NIM will prevent software customizationoperations from being performed on it. This is to safeguard the SPOT from changes thatmay adversely affect running client machines. However, this restriction can be overridden byspecifying the force option when performing the operation.

When NIM is used to install software in a SPOT, the following operations are performed tomanage the software for diskless and dataless clients:

1. The /usr files are installed in the SPOT. These files are automatically seen by all theclients that mount the SPOT as their /usr file systems.

2. The root files are installed in special subdirectories in the SPOT.

3. After all the filesets have been installed in the SPOT, the root files are copied to the rootdirectories of any diskless or dataless clients that have been initialized with the SPOT.

When NIM is used to uninstall software in a SPOT, the following operations are performed tomanage the software for diskless and dataless clients:

1. The /usr files are removed from the SPOT. This also automatically ”removes” the filesfrom the client systems.

2. The root files of the software are removed from the client root directories.

NIM also provides a sync_roots operation to perform consistency verification andcorrection to ensure the client root directories match the root parts stored in the SPOT.


NIM NetworksIn order to perform certain NIM operations, the NIM master must be able to supplyinformation necessary to configure client network interfaces. The NIM master must also beable to verify that client machines can access all the resources required to supportoperations. To avoid the overhead of repeatedly specifying network information for eachindividual client, NIM networks are used to represent the networks in a NIM environment.When NIM clients are defined, the associated network for the client must be specified.During NIM operations, the NIM master is able to use information from the client’s networkdefinition when necessary.

When the NIM master is configured, the network associated with the master is automaticallydefined in the NIM environment. It is necessary only to define additional NIM networks ifclients reside on other local area networks or subnets. The procedures described in thisguide and reference are designed to automatically define NIM networks, if necessary, whenclients are added. However, this section is included to describe NIM networks in detail incase manual definition of networks and routes is required.

Supported NIM Network TypesThe supported network types are as follows:

• Ethernet

• Standard Ethernet

• IEEE 802.3 Ethernet

• Token–Ring

• FDDI

• ATM

• Generic

Network boot support is provided for Ethernet, Token–Ring, and FDDI. Unlike other networkadapters, ATM adapters cannot be used to boot a machine. Therefore, installing a machineover an ATM network requires special processing. See Installing to Clients on ATMNetworks. The Generic network type is used to represent all other network types wherenetwork boot support is not available. For clients on Generic networks, NIM operations thatrequire a network boot, such as bos_inst and diag, are not supported. However,nonbooting operations, such as cust and maint, are allowed. Diskless and dataless clientscannot be associated with Generic networks, because they inherently rely on network bootcapability.

Defining NIM NetworksNetworks are defined in the NIM environment using the NIM define operation. Thecommand line syntax is as follows:

nim –o define –t NetworkType –a Attribute = Value ...

MachineName


where the following attributes are required:

–a net_addr= Value Specifies the IP address of the network being defined.If the network address is not known, see Determining aNetwork’s IP Address on page 27-12.

–a snm= Value Specifies the subnet mask for the network.

–t NetworkType Specifies the type of network being defined. Validvalues are atm, tok, ent, fddi, and generic.

The following attributes are optional:

–a comments= Value Provides comments about this network.

–a ieee_ent= Value Specifies IEEE 802.3 Ethernet configuration. This isonly valid for networks that are defined with the enttype or those that have an other_net_type attribute setto ent.

–a other_net_type= Value Specifies another network type that applies to thislogical network. Each NIM network is used to representone logical network that exists in the NIM environment.When the network is defined, the type of networkinterface used in the network must be supplied. Usually,a network is composed of only one type. However, abridge can be used to connect different network typestogether to form one logical network. In that situation,NIM needs to know what the other network interfacetypes are, and this attribute is used to specify thatinformation. For more information on how to use theother_net_type attribute, see Defining aHeterogeneous Network on page 27-12.

–a routing= Value... Stores NIM routing information for a network. Thisattribute requires a sequence number when specified.When a new NIM route is specified, the routingattribute consists of three values:

Value 1Specifies the NIM name of the destination network forthis route.

Value 2Specifies the host name of the gateway to use inorder to communicate with the destination network.

Value 3Specifies the host name of the gateway used by thedestination network to get back to this network.

This attribute can be used to add a default route orstatic route. To add a default route, specify default forValue 1. Then, specify the default gateway for thenetwork in Value 2. Leave Value 3 blank.

For more information on adding and changing routes,see NIM Routes on page 27-12,

Establishing a Default NIM Route Between Networkson page 25-9, and Establishing a Static NIM RouteBetween Networks.

–a verbose= Value Displays information for debugging. Use verbose=5 toshow maximum detail.


It is also possible to define NIM networks automatically when client machines are defined.To do this, use the find_net and net_definition attributes when defining the client. Formore information, see NIM Machines on page 27-2.

Determining a Network’s IP AddressNIM determines a network’s IP address by performing a bitwise ”AND” on the binaryrepresentations of the network’s subnet mask and the address of any machine’s IP addresson the same network. For example:

subnet mask = 255.255.254.0

client address = 129.35.58.207

In binary:

subnet mask = 11111111.11111111.11111110.00000000

client address = 10000001.00100011.00111010.11001111

network address = 10000001.00100011.00111010.00000000

In decimal:

network address = 129.35.58.0

NIM RoutesRouting information is used internally by NIM to ensure that a client on one network cancommunicate with a server on another network. It defines the gateway to use to go from onenetwork to the other network.

NIM provides the ability to define default or static routes. Default NIM routes provide thefollowing advantages over static routes:

• They more closely model the network configuration of common network environments.

• They permit resources that are distributed throughout a NIM environment to be moreeasily accessed by any client in the NIM environment.

To determine the gateway used by machines on a given network, run netstat –rn on arunning machine on the network to see if a default gateway is listed. You can also issuetraceroute Host_Name from a running machine on the network in question, whereHost_Name is the name of the master’s primary network interface if determining thegateway for a client, or the name of a target client if determining the gateway used by themaster. The first gateway listed is the gateway used by machines on the specified network.

Note that NIM routes are not required if the only networks defined in a NIM environment areassociated with interfaces (if attributes) defined on the NIM master and if all resources willbe defined on the master. If resources are served by machines other than the master toclients that do not reside on the same network as the server, NIM routes are requiredbetween those networks even if all networks are attached to interfaces belonging to themaster. In this case, the master must act as a gateway (with IP–forwarding switched on),and the host name of the interface on the master should be used as a gateway.

Networks with default routes may be created automatically when NIM machines are beingdefined.

Communications between networks go through several gateways. However, it is importantto remember that when defining NIM routes for networks, the only gateways of interest arethe first ones used by the networks to reach their destinations. Intermediate gatewaysbetween the originating and destination networks are irrelevant for NIM routing purposes.

Defining a Heterogeneous NetworkThis section describes the NIM feature that enables NIM to model networks consisting ofdifferent data–link protocol segments. These kinds of networks use bridges to connect twosegments that have different data link protocols. A network consisting of a Token–Ring and


an Ethernet segment can be connected to form a single logical network, as shown in thefollowing figure.

Figure 1. Heterogeneous Network This illustration shows a single IP network in which themaster server uses its token–ring connection and a bridge to communicate with its client onan Ethernet segment.

Because a single NIM network object is used to represent one network, the other_net_typeattribute is reserved for a different type of interface that can exist in a network. Theother_net_type attribute can be added to the definition of a network object. When presentin a network definition, the other_net_type attribute tells NIM that this logical network usesa bridge to connect the other network type to the network type that was specified when theobject was defined.

When you define a machine object to be connected to a network object, NIM checks to seeif the network has any other_net_type attributes. If so, NIM requires that the fourth field,which is usually optional, in the if attribute, be specified. This field specifies the logical nameof the client’s network adapter. The following example defines a network object that has abridge joining a Token–Ring and an Ethernet segment:

nim –o define –t tok –a net_addr=129.35.129.0 \

–a snm=255.255.240.0 –a other_net_type1=ent b905net

lsnim –l b905net

class = network

type = tok

net_addr = 129.35.128.0

snm = 255.255.240.0

other_net_type1 = ent


prev_state = information is missing from this object’s def>

The other_net_type attribute requires a sequence number because a network could becomposed of all three types of interfaces linked by bridges.


When you define a client’s interface that is physically connected to an Ethernet segmentjoined with a Token–Ring network using a bridge (with master being on the Token–Ringside), you must supply the fourth field:

nim –o define –t standalone –a if1=’find_net mymac 08005ac9430c \

ent’ –a cable_type1=bnc mymac

Adding Another Network Type to a NIM Network

From Web-based System Manager1. In the NIM Network container, double–click on a network. The General page of the

properties notebook displays.

2. Use the General page to add a network type to the network.

From SMIT1. To add another network type, enter the smit nim_chnet fast path.

2. Select the network to change.

3. Specify the additional network type to be supported.

From the Command LineTo define a NIM network, enter:

nim –o change –a other_net_type SequenceNumber = NetworkType

NetworkName

For example, to change a Token–Ring network called network1 to also support Ethernetand FDDI, enter:

nim –o change –a other_net_type1=ent –a other_net_type2=fddi network1


NIM Resources

A large number of resources (files and directories) are needed to support NIM softwareinstallation and maintenance operations. Resources can be added through the Web-basedSystem Manager New Resources wizard.

To obtain detailed information about any resource, enter the following from the NIM master:

lsnim –Pa ResourceType

The Web-based System Manager and SMIT interfaces are designed to hide much of thedetail required for the command line interface. Therefore, these sections only document theresource task procedures for the command line. The following information applies to theother interfaces as well, but discussion of those interfaces is deferred to the onlinecontextual help available for those applications. The following sections describe detailedinformation about each NIM resource:

• adapter_def Resource on page 27-15

• boot Resource on page 27-16

• bosinst_data Resource on page 27-16

• dump Resource on page 27-17

• exclude_files Resource on page 27-17

• fb_script Resource on page 27-18

• fix_bundle Resource on page 27-19

• home Resource on page 27-19

• image_data Resource on page 27-20

• installp_bundle Resource on page 27-21

• lpp_source Resource on page 27-21

• mksysb Resource on page 27-23

• nim_script Resource on page 27-24

• paging Resource on page 27-24

• resolv_conf Resource on page 27-25

• root Resource on page 27-26

• script Resource on page 27-26

• shared_home Resource on page 27-27

• SPOT (Shared Product Object Tree) Resource on page 27-28

• tmp Resource on page 27-31

adapter_def ResourceThe adapter_def resource represents a directory that contains secondary adapterconfiguration files that are used during bos_inst and cust operations. The adapter_defresource directory is populated with secondary–adapter configuration files by thenimadapters command.

Defining an adapter_def ResourceThe command line syntax for defining a adapter_def resource is:

nim –o define –t adapter_def –a Attribute = Value ...

adapter_defName


The following attributes are required for the adapter_def resource:

–a location= Value Specifies the full path name of the adapter_def resourcedirectory.

–a server= Value Specifies the name of the machine where the adapter_defresource directory resides. Only the master can serve anadapter_def resource.

The following attributes are optional for the adapter_def resource:

–a comments= Value Describes the resource.

–a group= Value Specifies the name of a resource group to which thisresource should be added.

–a verbose= Value Displays information for debugging. To show maximumdetail, specify a value of 5.

boot Resource

The boot resource is an internally managed NIM resource used to indicate that a bootimage has been allocated to a client. The boot resource is automatically allocated to clientsto support NIM operations requiring a network boot. The boot resource will be automaticallydeallocated when the operation completes.

bosinst_data Resource

A bosinst_data resource represents a file that contains information for the BOS installationprogram. Normally, the BOS installation program looks for this information in the/bosinst.data file in the BOS installation image. If this file does not exist or if it does notcontain all the information that the BOS installation program requires, the program promptsfor information by using a console that is local to the target. Information must then bespecified manually for the BOS installation to proceed. With a bosinst_data resource, thedata can be specified in a NIM resource prior to the installation to prevent the need forprompting at the console.

A sample bosinst.data file (SPOT_Offset /usr/lpp/bosinst/bosinst.template) is located onthe SPOT resource server. Also, see Performing a Nonprompted BOS Installation on page23-15 for a sample bosinst_data file.

For instructions on how to create and use a bosinst_data file, see Performing aNonprompted BOS Installation on page 23-15.

Defining a bosinst_data Resource

The command line syntax for defining a bosinst_data resource is:

nim –o define –t bosinst_data –a Attribute = Value ...

bosinst_dataName

The following attributes are required for the bosinst_data resource:

–a location= Value Specifies the full path name of the bosinst_data resourcefile.

–a server= Value Specifies the name of the machine where thebosinst_data resource file resides.


The following attributes are optional for the bosinst_data resource:




–a source= Value Specifies an existing bosinst_data resource to bereplicated when defining a new resource. The file pointedto by the source resource will be copied to the newlocation.

dump Resource

A dump resource represents a directory in which client dump directories are maintained.When this type of resource is allocated to a client, NIM creates a subdirectory for the client’sexclusive use. This allocated subdirectory is initialized by the dkls_init or dtls_initoperation, which creates an empty file in this subdirectory. After initialization, the client usesthis file to store any dump images it creates.

Note: If you subsequently deallocate this resource, NIM removes the dump fileand the subdirectory that NIM created for the client’s use.

Defining a dump Resource

The command line syntax for defining a dump resource is:

nim –o define –t dump –a Attribute = Value ... DumpName

The following attributes are required for the dump resource:

–a location= Value Specifies the full path name of the parent directory for theclient dump files.

–a server= Value Specifies the name of the machine where the directory forthe dump resource will be created.

The following attributes are optional for the dump resource:




exclude_files Resource

An exclude_files resource represents a file that contains a list of files and directories thatshould be excluded when creating a system backup image. This resource may be usedwhen a mksysb resource is being created from a running NIM client.


Defining an exclude_files Resource

The command line syntax for defining an exclude_files resource is:

nim –o define –t exclude_files –a Attribute = Value ...

exclude_filesName

The following attributes are required for the exclude_files resource:

–a location= Value Specifies the full path name of the file containing the list offiles and directories to exclude from the mksysb.

–a server= Value Specifies the name of the machine where the file for theexclude_files resource resides.

The following attributes are optional for the exclude_files resource:




–a source= Value Specifies an existing exclude_files resource to bereplicated when defining a new resource. The file pointedto by the source resource will be copied to the newlocation.

fb_script ResourceAn fb_script resource represents a file that is used to configure devices when a NIM clientis booting for the first time after the BOS installation process is completed. During BOSinstallation, certain customization operations (such as device configuration) cannot beperformed because they require certain daemons to be running. However, at this point inthe BOS installation process, daemons are not available. As a result, certain devices maynot be configured during system reboot, and have to be manually configured after thesystem has booted.

You can use an fb_script resource to provide device–configuration information. The BOSinstallation process adds the content of the fb_script resource to the /etc/firstboot file,which is run the first time that a client is booted. The /etc/firstboot file then performs thedevice configuration.

Defining an fb_script ResourceThe command line syntax for defining an fb_script resource is as follows:

nim –o define –t fb_script –a server= server_name \

–a location= fbscript_file_location fbscript_object_name

After the fb_script resource is defined, you can allocate the resource and initiate a BOSinstallation operation using the fb_script resource, as follows:

nim –o bos_inst –a fb_script= fbscript_object_name client_name

The following attributes are required for the fb_script resource:

–a location= Value Specifies the full path name of the file being defined as thefb_script resource.

–a server= Value Specifies the name of the machine where the file for thefb_script resource resides.


The following attributes are optional for the fb_script resource:


–a source= Value Specifies an existing fb_script resource to be replicatedwhen defining a new resource. The file pointed to by thesource resource will be copied to the new location.

fix_bundle Resource

A fix_bundle resource represents a file containing fix keywords to be used by the instfixcommand, which is called by the NIM cust and fix_query operations. NIM mounts thefix_bundle resource on the client so it can be used by the local instfix command. NIMautomatically unmounts the resource when the operation has completed.

A fix can include either a single fileset update or multiple fileset updates that are related insome way; fixes are identified by unique keywords. When a fix is identified with anAuthorized Program Analysis Report (APAR) number, it includes all the fileset updates thatare necessary to fix the reported software problem identified by that number.

Defining a fix_bundle Resource

The command line syntax for defining a fix_bundle resource is:

nim –o define –t fix_bundle –a Attribute = Value ...

fix_bundleName

The following attributes are required for the fix_bundle resource:

–a location= Value Specifies the full path name of the file containing the list offixes to manage.

–a server= Value Specifies the name of the machine where the fix_bundleresource file resides.

The following attributes are optional for the fix_bundle resource:




–a source= Value Specifies an existing fix_bundle resource to be replicatedwhen defining a new resource. The file pointed to by thesource resource will be copied to the new location.

home Resource

A home resource represents a directory in which client /home directories are maintained.When this type of resource is allocated to a client, NIM creates a subdirectory for the client’sexclusive use. This allocated subdirectory is subsequently initialized when you perform thedkls_init or dtls_init operation. After initialization, any time the client performs a networkboot, the client NFS mounts this subdirectory over /home to gain access to the homedirectory that has been set up for its use. This subdirectory remains mounted over /homeon the client as long as the client is running.

Note: Whenever this resource is deallocated, NIM removes the subdirectory thatwas created for the client’s use. Therefore, back up any files you want to


save in the client’s subdirectory before you deallocate a resource of thistype.

Defining a home Resource

The command line syntax for defining a home resource is:

nim –o define –t home –a Attribute = Value ... HomeName

The following attributes are required for the home resource:

–a location= Value Specifies the full path name of the parent directory for theclient /home directories.

–a server= Value Specifies the name of the machine where the directory forthe home resource will be created.

The following attributes are optional for the home resource:




image_data Resource

An image_data resource represents a file that contains information for the BOS installationprogram. This information describes how physical disks and file systems should beconfigured in the root volume group during installation. Normally, the BOS installationprogram determines default values that should be used, or uses an image.data file from amksysb being restored. Use a customized image_data resource only in special cases.

A sample image.data file (SPOT_Offset /usr/lpp/bosinst/image.template) is located onthe SPOT resource server. For more information about the image.data file, see the AIX 5LVersion 5.2 Files Reference.

Defining an image_data Resource

The command line syntax for defining an image_data resource is:

nim –o define –t image_data –a Attribute = Value ...

image_dataName

The following attributes are required for the image.data resource:

–a location= Value Specifies the full path name of the image_data resourcefile.

–a server= Value Specifies the name of the machine where the image_dataresource file resides.

The following attributes are optional for the image.data resource:





–a source= Value Specifies an existing image_data resource to be replicatedwhen defining a new resource. The file pointed to by thesource resource will be copied to the new location.

installp_bundle Resource

An installp_bundle resource represents a file that contains the names of filesets thatshould be managed by NIM. During an installation or maintenance operation, NIM mountsthe installp_bundle file on the client machine so it can be used by the local installpcommand. NIM automatically unmounts the resource from the client when the operation hascompleted.

Defining an installp_bundle Resource

The command line syntax for defining an installp_bundle resource is:

nim –o define –t installp_bundle –a Attribute = Value ...

installp_bundleName

The following attributes are required for the installp_bundle resource:

–a location= Value Specifies the full path name of the file containing the list ofsoftware to manage.

–a server= Value Specifies the name of the machine where theinstallp_bundle resource file resides.

The following attributes are optional for the installp_bundle resource:




–a source= Value Specifies an existing installp_bundle resource to bereplicated when defining a new resource. The file pointedto by the source resource will be copied to the newlocation.

lpp_source Resource

An lpp_source resource represents a directory in which software installation images arestored. If the lpp_source contains the minimum set of support images required to install amachine, it is given the simages attribute and can be used for BOS installation (bos_inst)operations. If an lpp_source does not contain enough software to be an simageslpp_source, then it can only be used in NIM cust operations to install software on runningmachines and SPOTs.

NIM uses an lpp_source for an installation operation by first mounting the lpp_source onthe client machine. The installp commands are then started on the client using the mountedlpp_source as the source for installation images. When the installation operation hascompleted, NIM automatically unmounts the resource.

In addition to providing images to install machines, lpp_source resources can also be usedto create and update SPOT resources.


Note: When copying device images to a directory that you plan to define as anlpp_source, be sure to copy all the device images for a given type ofdevice. For example:

cp /cdfs/usr/sys/inst.images/devices.pci.* lpp_source_directory

You can define an lpp_source in several ways:

• If a directory containing installation images already exists, it can be directly defined as anlpp_source resource.

• If a directory should be created and populated by NIM with the default set of supportimages for a BOS install, use the source attribute when defining the resource. Thisattribute specifies the name of the device that contains the installation images. NIMcopies the software images from this device into the location specified for thelpp_source. The images copied will include those from the simages list, all availabledevice support, and some additional software that is typically installed as well (forexample, X11).

• If an lpp_source should be created from a source device using a list of software otherthan the default set of images, specify the packages attribute when defining thelpp_source. Use the packages attribute to list the alternative set of software images tocopy.

The size of an lpp_source may vary greatly with the amount of software it includes. Aminimum lpp_source with just enough software to qualify for the simages attribute may beunder 100 MB, but a default lpp_source created from a CD–ROM may be over 350 MB. Itis recommended that a separate file system be created to contain an lpp_source so thespace can be more easily managed. By default, NIM automatically expands a file system asneeded when creating an lpp_source and copying images from a source device.

Beginning in AIX 5.2, the simages message displays only if the user is creating anlpp_source resource with the default installation packages. The simages message willdisplay if the simages attribute could not be set for the lpp_source. If a user creates anlpp_source and specifies a list of packages, the simages message is not printed. Thesimages attribute is set correctly, whether or not a simages message is printed or not.

If a user attempts to do an rte BOS installation with an lpp_source that does not have thesimages attribute, the user receives an error. The error message instructs the user to runnim –o check on the lpp_source to determine the missing packages needed for an rteBOS installation. Whenever a user runs nim –o check on an lpp_source after it has beencreated, the simages message is printed if the lpp_source does not contain all the imagesneeded for a rte BOS installation.

Defining an lpp_source Resource

The command line syntax for defining an lpp_source resource is:

nim –o define –t lpp_source –a Attribute = Value ...

lpp_sourceName

The following attributes are required for the lpp_source resource:

–a location= Value Specifies the directory that will contain the installationimages.

–a server= Value Specifies the name of the machine where the lpp_sourceis to be created.


The following attributes are optional for the lpp_source resource:

–a comments= Value Describes the lpp_source.


–a packages= Value Specifies a list of filesets to copy into the lpp_source if thedefault list of images is not desired.

–a source= Value Identifies the source device for copying installation imageswhen defining the lpp_source. This attribute is notrequired if the location of the lpp_source already containsinstallation images.


If a migration installation will be performed on NIM client machines, the lpp_source used inthe operation must contain all the required software to migrate the machine.

If the directory specified in the location attribute does not exist, NIM will create thedirectory. NIM will also remove the directory and its contents if the lpp_source is laterremoved.

mksysb Resource

A mksysb resource represents a file that is a system backup image created using themksysb command. This type of resource can be used as the source for the installation of aclient. The mksysb image must reside on the hard disk of a machine in the NIMenvironment in order to be defined as a resource. It cannot be located on a tape or otherexternal media.

A mksysb resource can be defined from an image that already exists on the hard disk ofthe NIM master or any NIM client. If such an image does not exist, it can be created whenthe resource is defined. To create the image when the resource is defined, specify the nameof the NIM client that will be the source for the backup, and set the mk_image attribute toyes in the command to define the mksysb resource. Use an exclude_files resource to listany files and directories that should not be included in the backup image.

Defining a mksysb Resource

The command line syntax for defining a mksysb resource is:

nim –o define –t mksysb –a Attribute = Value ... mksysbName

The following attributes are required for the mksysb resource:

–a location= Value Specifies the full path name of the mksysb image.

–a server= Value Specifies the name of the machine where the mksysbimage resides or is to be created.

The following attributes are optional for the mksysb resource:

–a comments= Value Describes the mksysb.

–a exclude_files= Value Specifies an exclude_files resource to use to exclude filesand directories from the system backup.



–a mk_image= Value Specifies the flag to use to create a mksysb image from amachine in the NIM environment.

–a mksysb_flags= Value Specifies the flags to use to tell the command how tocreate the backup.

–a size_preview= Value Specifies the flag to verify that space is available beforecreating a mksysb image.

–a source= Value Specifies the name of the machine to be backed up in themksysb image.


–a source= Value Specifies the name of the machine to be backed up in themksysb image if the mk_image attribute is specified. If themk_image attribute is not specified, this value specifies anexisting mksysb resource to be replicated when defining anew mksysb resource. The file pointed to by the sourceresource will be copied to the new location.

nim_script Resource

The nim_script resource is an internally managed NIM resource used to indicate that ascript should be run by NIM as part of a NIM operation. The nim_script resource isautomatically allocated to support some NIM operations, and it is automatically deallocatedwhen the operations complete.

Depending on the operation, NIM will use the following rules to determine which NIM serverto place the nim_script resource on:

• For a bos_inst operation, the nim_script resource will be placed on the SPOT server.

• For cust operation with an lpp_source, the nim_script resource will be placed on thelpp_source server.

• For a cust operation without an lpp_source, the nim_script resource will be placed onthe script server.

• Otherwise, the nim_script resource will be placed on the NIM master.

paging Resource

A paging resource represents a directory where client paging files are maintained. Whenthis type of resource is allocated to a client, NIM creates a subdirectory for the client’sexclusive use. This allocated subdirectory is initialized by the dkls_init or dtls_initoperation, which creates a file in this subdirectory that the client configures as a pagingdevice when it performs a network boot. By default, 32 MB are reserved for this file. Adifferent value can be specified using the size flag when the dkls_init or dtls_init operationis performed.

After this resource has been initialized for a client, it is configured as a paging device by theclient each time the client performs a network boot.

Note: If you subsequently deallocate this resource, NIM removes the paging fileand the subdirectory it created for the client’s use.


Defining a paging Resource

The command line syntax for defining a paging resource is:

nim –o define –t paging –a Attribute = Value ... PagingName

The following attributes are required for the paging resource:

–a location= Value Specifies the full path name of the parent directory for theclient paging files.

–a server= Value Specifies the name of the machine where the directory forthe paging resource will be created.

The following attributes are optional for the paging resource:




resolv_conf Resource

A resolv_conf resource represents a file containing valid /etc/resolv.conf entries thatdefine Domain Name Protocol name–server information for local resolver routines. Aresolv_conf resource can be allocated to a standalone machine as part of a bos_instoperation or to a diskless or dataless machine as part of a dkls_init or dtls_init operation.Upon successful installation and reboot, the machine will be configured to use the domainname services defined by the resource.

The following are sample entries in a resolv_conf resource file:

nameserver 129.35.143.253

domain test.bull.com

Defining a resolv_conf Resource

The command line syntax for defining a resolv_conf resource is:

nim –o define –t resolv_conf –a Attribute = Value ...

resolv_confName

The following attributes are required for the resolv_conf resource:

–a location= Value Specifies the full path name of the file containing theinformation for domain name server (DNS) nameresolution.

–a server= Value Specifies the name of the machine where the resolv_confresource file resides.

The following attributes are optional for the resolv_conf resource:





–a source= Value Specifies an existing resolv_conf resource to be replicatedwhen defining a new resource. The file pointed to by thesource resource will be copied to the new location.

root Resource

A root resource represents a directory in which client root directories are maintained. Whenthis type of resource is allocated to a diskless or a dataless client, NIM creates asubdirectory for the client’s exclusive use. This allocated subdirectory is subsequentlyinitialized when you perform the dkls_init or dtls_init operation.

After initialization, anytime the client performs a network boot, the client NFS mounts thissubdirectory over ”/” to gain access to the root directory that has been set up for its use.This subdirectory remains mounted over / on the client as long as the client is running.

Note: Whenever this resource is deallocated, NIM removes the subdirectory thatwas created for the client’s use. Therefore, any files you want to save in theclient’s subdirectory should be backed up before you deallocate a resourceof this type.

Defining a root Resource

The command line syntax for defining a root resource is:

nim –o define –t root –a Attribute = Value ... RootName

The following attributes are required for the root resource:

–a location= Value Specifies the full path name of the directory under whichclient root directories will be created.

–a server= Value Specifies the name of the machine where the directory forthe root resource will be created.

The following attributes are optional for the root resource:




script Resource

A script resource represents a file that is a user–defined shell script. After it is defined, thistype of resource can be used to perform processing on a client as part of a NIM cust orbos_inst operation.

The script resources are always run by NIM after software installation is performed in custor bos_inst operations. This allows the scripts to perform configuration processing on theclient after all the software is installed. Multiple script resources can be allocated for clientuse, but the order in which the scripts will be run is not predictable.

Note: The script resources must not point to files that reside in the/export/nim/scripts directory. This directory is used for the nim_script


resource that is managed by NIM. NFS restrictions prevent defining multipleresources in the same location.

Defining a script Resource

The command line syntax for defining a script resource is:

nim –o define –t script –a Attribute = Value ... ScriptName

The following attributes are required for the script resource:

–a location= Value Specifies the full path name of the script resource file.

–a server= Value Specifies the name of the machine where the scriptresource file resides.

The following attributes are optional for the script resource:




–a source= Value Specifies an existing script resource to be replicated whendefining a new resource. The file pointed to by the sourceresource will be copied to the new location.

shared_home Resource

A shared_home resource represents a directory that can be used as a common /homedirectory by one or more clients. When this type of resource is allocated to a client, andwhen the dkls_init or dtls_init operation is performed, NIM configures the client’sconfiguration to use this common directory. After initialization, anytime the client performs anetwork boot, the client NFS mounts this common directory over its /home directory. Thiscommon directory remains mounted as long as the client is running.

Note: Whenever this resource is deallocated, NIM only changes the client’sconfiguration so that this directory is no longer used by the client. NIM doesnot remove the common directory.

Defining a shared_home Resource

The command line syntax for defining a shared_home resource is:

nim –o define –t shared_home –a Attribute = Value ...

shared_homeName

The following attributes are required for the shared_home resource:

–a location= Value Specifies the full path name of the directory to be used as acommon /home directory among clients.

–a server= Value Specifies the name of the machine where the directory forthe shared_home resource will be created.


The following attributes are optional for the shared_home resource:




SPOT (Shared Product Object Tree) Resource

The SPOT (Shared Product Object Tree) is a fundamental resource in the NIMenvironment. It is required to install or initialize all machine configuration types. A SPOTprovides a /usr file system for diskless and dataless clients, as well as the network bootsupport for all clients.

Everything that a machine requires in a /usr file system, such as the AIX kernel, executablecommands, libraries, and applications are included in the SPOT. Machine–uniqueinformation or user data is usually stored in the other file systems. A SPOT can be locatedon any standalone machine within the NIM environment, including the master. The SPOT iscreated, controlled, and maintained from the master, even though the SPOT can be locatedon another system.

You can create a SPOT by converting the /usr file system (/usr SPOT, or you can locate theSPOT elsewhere within the file system (non– /usr SPOT) on the server.

The /usr SPOT inherits all the optional software that is already installed on the server. Allthe clients using the /usr SPOT have access to the optional software installed on the server.The non– /usr SPOT can be used to manage a different group of optional software thanthose that are installed and licensed for the server.

Creating a SPOT by converting the /usr file system has the advantage of being fast andusing much less disk space. However, this method does not give you the flexibility to choosewhich software packages will be included in the SPOT, because all the packages andfilesets installed in the /usr file system of the machine serving the SPOT will be included inthe SPOT. The second method, creating a non– /usr SPOT, uses more disk space, but it ismore flexible. Initially, only the minimum set of software packages required to support NIMclients is installed in the SPOT, but additional packages and filesets can be installed. Also, itis possible to have multiple SPOT s, all with different additional packages and filesetsinstalled, serving different clients.

Note: Do not create a non– /usr SPOT in a subdirectory of the /usr file system.

A SPOT varies in size from 100 MB up to, and sometimes in excess of, 300 MB dependingon the software that is installed. Because all device support is installed in the SPOT and thenumber of device filesets typically increases, the size is not easily predictable from onerelease of AIX to another.

SPOTs are used to support all NIM operations that require a machine to boot over thenetwork. These operations are as follows:

• bos_inst

• maint_boot

• diag

• dkls_init

• dtls_init

When a SPOT is created, network boot images are constructed in the /tftpboot directory ofthe SPOT server, using code from the newly created SPOT. When a client performs anetwork boot, it uses tftp to obtain a boot image from the server. After the boot image is


loaded into memory at the client, the SPOT is mounted in the client’s RAM file system toprovide all additional software support required to complete the operation.

Each boot image created is up to 4 MB in size. Before creating a SPOT, ensure there issufficient space in the root (/) file system, or create a separate file system for /tftpboot tomanage the space required for the network boot images.

A single network boot image can be accessed by multiple clients; therefore, the networkboot image cannot contain any client–specific configuration information. The platform type isspecified when the machine object is defined, while the network type is determined from theprimary interface definition. Two files are created in the /tftpboot directory on the SPOTserver for each client to be network–booted: ClientHostName and ClientHostName.info.The ClientHostName file is a link to the correct network boot image, while theClientHostName.info file contains the client configuration information.

When the SPOT is defined (and created), the following occurs:

• The BOS image is retrieved from archive or, for /usr conversion, just the root directory isretrieved from archive (/usr/lpp/bos/inst_root).

• The device support required to support NIM operations is installed.

• Network boot images are created in the /tftpboot directory.

To list the software installed in a SPOT, enter the following command:

nim –o lslpp SPOTName

If you want to change your /usr SPOT back to a normal /usr file system, you must removethe SPOT from the NIM database.

For information about software installation and maintenance tasks you can perform on aSPOT, see Customizing NIM Clients and SPOT Resources.

Network Boot Images for AIX 4.2 SPOTsEach network boot image supports a single network, platform, and kernel type. The networkboot image files are named SPOTName.Platform.Kernel.Network. The network types areToken–Ring, Ethernet, and FDDI. The platform types are:

rs6k (AIX 5.1 and earlier).5 Used for POWER family/POWERfamily2/P2SC/POWER–based MCA bus–basedmachines.

rspc (AIX 5.1 and earlier) Used for POWER–based Reference Platform (PREP)Architecture–based machines.

chrp Used for POWER–based Common HardwareReference Platform (CHRP) Architecture–basedmachines.

The rs6ksmp platform for AIX 4.2 (and later) SPOTs is represented by the boot image witha platform type of rs6k and a kernel type of mp.

The kernel types are:

up Used for single processor machines.

mp Used for multiple processor machines.


Both up and mp boot images are created for each platform and network type. The networkboot images located in /tftpboot for a SPOT named 42spot look similar to the following:

42spot.rs6k.mp.ent

42spot.rs6k.mp.fddi

42spot.rs6k.mp.tok

42spot.rs6k.up.ent

42spot.rs6k.up.fddi

42spot.rs6k.up.tok

42spot.rspc.mp.ent

42spot.rspc.mp.tok

42spot.rspc.up.ent

42spot.rspc.up.tok

The amount of space used in the /tftpboot directory for boot images may become verylarge. An AIX 4.2.1 (or later) SPOT that supports network boot for all possible combinationsof platforms, kernel types, and network adapters may require as much as 60 MB in/tftpboot. If the same server serves multiple SPOTs, the space required in /tftpboot will beeven more because each SPOT creates its own set of boot images.

Network Boot Images for AIX 4.3 or later SPOTsIn AIX 4.3 or later, NIM creates by default only the boot images required to support themachines and network types that are defined in the environment. This situation shouldsignificantly reduce the amount of disk space used and the time required to create bootimages from SPOT resources.

Defining a SPOT Resource

The command line syntax for defining a SPOT resource is:

nim –o define –t spot –a Attribute = Value ... SPOTName

The following attributes are required for the SPOT resource:

–a location= Value.5 Specifies the parent directory under which the SPOT isto be created.

–a server= Value Specifies the name of the machine where the SPOT isto be created.

–a source= Value Identifies the source device for installation images tocreate and install the SPOT.

The following attributes are optional for the SPOT resource:

–a auto_expand= Value Expands the file system as needed when installing theSPOT. The default value is yes.

–a comments= Value Describes the SPOT.

–a debug= Value Builds debug–enabled network boot images. Thedefault value is no.

–a installp_flags= Value Specifies the flags that describe how installp shouldinstall software into the SPOT. The default value isagQX.


–a show_progress= Value Shows installp output as SPOT is installed. The defaultvalue is yes.


Note: The creation of a SPOT, by default, produces a large amount of output. Besure to scan the output to look for nonfatal errors and warnings that may notbe evident from a successful return code.

tmp Resource

A tmp resource represents a directory where client /tmp files are maintained. When thistype of resource is allocated to a client, NIM creates a subdirectory for the client’s exclusiveuse. This allocated subdirectory is subsequently initialized when you perform the dkls_initor dtls_init operation. After initialization, anytime the client performs a network boot, theclient NFS mounts this subdirectory over /tmp to gain access to the /tmp directory that hasbeen set up for its use. This subdirectory remains mounted over /tmp on the client as longas the client is running.

Note: Whenever this resource is deallocated, NIM removes the subdirectory thatwas created for the client’s use. Therefore, back up any files you want tosave in the client’s subdirectory before you deallocate a resource of thistype.

Defining a tmp Resource

The command line syntax for defining a tmp resource is:

nim –o define –t tmp –a Attribute = Value ... TmpName

The following attributes are required for the tmp resource:

–a location= Value Specifies the full path name of the directory whereclient /tmp directories will be created.

–a server= Value Specifies the name of the machine where the directoryfor the tmp resource will be created.

The following attributes are optional for the tmp resource:




Distributed NIM Resources

Usually, a NIM administrator will use the NIM master as the server for all resources. Thisstrategy keeps all resources together on one machine. However, there are several reasonsto distribute resources onto client machines:

• If the NIM environment requires several large resources to be defined, it may not bepossible to put them all on the same server because of disk space limitations. Creatingresources on different machines allows the burden of disk consumption to be distributedover several machines.

• Serving resources from different machines helps avoid bottlenecks when performing NIMoperations on large numbers of clients. Bottlenecks can occur on server machines or on


network gateways, so it may be beneficial to distribute resources across servers runningin different subnets.

• Multiple resources of the same type can be created on different machines to increase theavailability of resources when servers are taken offline for scheduled maintenance.

• Some SPOT resources at certain levels cannot be served by some machines at certainlevels. Specifically, SPOT creation is not supported when the level of AIX installed in theSPOT is higher than the level of AIX running on the server. When you are creatingSPOTs at multiple levels, it may be necessary to distribute the SPOTs on differentservers.

Distributing resources on different machines in the NIM environment is simply a matter ofspecifying the correct server information when the resource is defined. After the resourcesare created, they are used no differently than resources defined on the master.


NIM Operations

A large number of operations can be performed to manage a NIM environment and performsoftware installation and maintenance. The Web-based System Manager and SMITinterfaces are designed to hide much of the detail required for the command line interface.Therefore, this section only documents the operations for the command line. All of thisinformation applies to the other interfaces as well, but discussion of those interfaces isdeferred to the online contextual help available for those applications.

Most NIM operations are performed by running the nim command with various attributes foreach possible operation. The command line syntax is as follows:

nim –o OperationName –a Attribute = Value ... TargetName |

TargetNames

The NIM operations you can perform are:

• allocate on page 27-34

• alt_disk_install on page 27-34

• bos_inst on page 27-37

• change on page 27-42

• check on page 27-42

• cust on page 27-43

• deallocate on page 27-45

• define on page 27-45

• diag on page 27-45

• dkls_init on page 27-46

• dtls_init on page 27-47

• fix_query on page 27-47

• lppchk on page 27-48

• lppmgr on page 27-49

• maint on page 27-49

• maint_boot on page 27-50

• reboot on page 27-50

• remove on page 27-51

• reset on page 27-51

• select on page 27-51

• showlog on page 27-52

• showres on page 27-53

• sync_roots on page 27-54

• unconfig on page 27-54

• update on page 27-54


allocate

The allocate operation is used to make resources available to NIM clients for subsequentoperations.

The command line syntax for the allocate operation is as follows:

nim –o allocate –a ResourceType = ResourceName ... TargetName |

TargetNames

The target of an allocate operation may be a NIM client or group of NIM clients.

The following attribute can be specified for the allocate operation:

–a ResourceType=ResourceName(required)

Specifies the resource to allocate to theclient, for example,lpp_source=42_images.

When a resource is allocated to a client, an entry is added to the /etc/exports file on theresource server to NFS export the resource to the client. The allocation count for theresource is also incremented. When the allocation count is greater than 0, the resourcecannot be modified. During NIM operations, a client mounts and uses the resources thathave been allocated to it.

alt_disk_installThe alt_disk_install operation (available in AIX 4.3 or later) can be used to install amksysb image on a client system’s alternate disk or disks, or it can be used to clone aclient running rootvg to an alternate disk.

The command line syntax for the alt_disk_install mksysb operation is as follows:

nim –o alt_disk_install –a source=mksysb –a mksysb= mksysb_resource \

–a disk= target_disk(s) –a attribute=Value.... TargetName |

TargetNames

The command line syntax for the alt_disk_install rootvg clone operation is as follows:

nim –o alt_disk_install –a source=rootvg –a disk= target_disk(s) \

–a attribute=Value.... TargetName | TargetNames

The target of an alt_disk_install operation can be a standalone NIM client or a group ofstandalone NIM clients. The clients must also have the bos.alt_disk_install.rte filesetinstalled.

To display the alternate disk installation status while the installation is progressing, enter thefollowing command on the master:

lsnim –a info –a Cstate ClientName

OR

lsnim –l ClientName


The following are required attributes for alt_disk_install mksysb operation:

–a source=mksysb Specifies the type of alt_disk_install to perform.

–a disk= target_disk(s) Specifies the disks on the client system that themksysb image will be restored. This disk or thesedisks must not currently contain any volume groupdefinition. The lspv command should show thesedisks as belonging to volume group None. If youare specifying more than one disk, the disk namesmust be enclosed in a set of single quotes; forexample, ’hdisk2 hdisk3’.

–a mksysb= mksysb_resource Specifies the mksysb resource to use.

The following are required attributes for the alt_disk_install rootvg clone operation:

–a source=rootvg Specifies the type of alt_disk_install to perform.

–a disk= target_disk(s) Specifies the disks on the client system that themksysb image will be restored. This disk or thesedisks must not currently contain any volume groupdefinition. The lspv command shows these disks asbelonging to volume group None. If you arespecifying more than one disk, the disk names mustbe enclosed in a set of single quotes; for example,’hdisk2 hdisk3’.

The following are optional attributes that can be specified for both alt_disk_install mksysband the alt_disk_install rootvg clone operation:

–a concurrent =Value Specifies the maximum number of machines fromthe selected group that should be installing at anygiven time. This attribute is only valid when thetarget of the operation is a machine group. Ifspecified, NIM will monitor the progress of allmachines in the group and attempt to keep no moreor less than the number specified installing until allmachines in the group are installed.

–a set_bootlist= Value Specifies whether to set the bootlist to point to thenew rootvg when the install is complete. Value canbe yes or no, where yes is the default value. Thenext time the system is rebooted, it will boot fromthe newly installed alternate disk if Value is set toyes.

–a boot_client= Value Specifies whether to reboot the client when thealt_disk_install operation is completed. Value canbe yes or no, where no is the default value. Thisattribute would normally be set only if theset_bootlist attribute was also set to yes.

–a debug= Value Specifies whether to print debug (set –x) outputfrom the alt_disk_install script. Value can be yesor no, where no is the default value. This outputdoes not go to the screen, but is saved to the NIMlog, /var/adm/ras/nim.alt_disk_install, on theclient system. This file can be checked after thealt_disk_install has completed.


–a image_data= Value Specifies the image_data resource to use whencreating the new alternate rootvg and its logicalvolumes and file systems. The new volume groupcreated must be large enough to restore themksysb image or a copy of the running rootvg. Anexclude_files attribute can also be used with analt_disk_install rootvg clone to specify files ordirectories that should not be backed up.

–a resolv_conf= Value Specifies the resolv_conf resource to use forconfiguring the domain and name resolution on theclient system when the system is rebooted. This isthe /etc/resolv_conf file that will be copied into thealternate disk’s file system. This may be useful if themksysb image you are using has a different/etc/resolv_conf file than the one you want theclient to retain.

–a script= Value Specifies the script resource to call at the end of thealt_disk_install operation. This script is called onthe running system before the /alt_inst file systemsare unmounted, so files can be copied from therunning system to the /alt_inst file systems beforethe reboot. This is the only opportunity to copy ormodify files in the alternate file system because thelogical volume names will be changed to matchthose of rootvg, and they will not be accessible untilthe system is rebooted with the new alternaterootvg.

–a time_limit =Value, Specifies the maximum number of hours that shouldelapse before ceasing to initiate installation ofadditional members of the selected group ofmachines. This value can only be specified whenlimiting the number of concurrent operations on agroup.

–a verbose= Value Specifies whether to show files as they are beingbacked up for a rootvg clone, or to show files asthey are being restored for a mksysb install. Valuecan be yes or no, where no is the default value.The output goes to the alt_disk_install log on theclient, /var/adm/ras/alt_disk_inst.log.

The following are optional attributes that can be specified only for the alt_disk_installrootvg clone operation:

–a exclude_files= Value Specifies an exclude_files resource to use toexclude files and directories from the rootvg. Filesand directories specified in this file will not becopied to the new cloned rootvg.

–a filesets= Value Specifies the list of filesets to install into thealternate rootvg after the clone of the rootvg iscomplete.

–a fixes= Value Specifies the APARs to install into the alternaterootvg after the clone of the running rootvg. Thefixes are in the format ”IX123456” or”update_all”.


–a fix_bundle= Value Specifies the fix_bundle resource that lists theAPARs to install into the alternate rootvg after theclone of the running rootvg.

–a installp_bundle= Value Specifies an installp_bundle resource that listsfilesets to install into the alternate rootvg after theclone of the running rootvg.

–a installp_flags= Value Tells installp how to apply the filesets,installp_bundle, fixes, or fix_bundles attributes.The default value is installp_flags=–acgX.

bos_inst

The bos_inst operation is used to install the AIX BOS on standalone clients.

The command line syntax for the bos_inst operation is as follows:

nim –o bos_inst –a source= Value –a Attribute = Value ...

TargetName | TargetNames

The target of a bos_inst operation can be a standalone NIM client or a group of standaloneNIM clients.

The following NIM resources are required attributes that can be specified for the bos_instoperation to install and customize a machine:

–a lpp_source= ValueIdentifies the lpp_source resource to be used. The lpp_source resource isonly required for an rte installation. The lpp_source resource specifiedmust have the simages attribute set. However, if you are performing abos_inst operation using a mksysb resource and an lpp_sourceresource, then the simages attribute is optional. The lpp_source providessoftware for machine customization. It also provides the BOS image forinstallation if the source attribute is rte.

–a source= ValueIdentifies the source for BOS run–time files. Valid values are:

rte Installs from a BOS image in the lpp_source.

mksysb Installs the machine from a mksysb image.

–a spot= Value Identifies the SPOT resource to be used. The SPOT provides support fornetwork boot and operations in the boot environment.

The following NIM resources are optional attributes that can be specified for the bos_instoperation:

–a accept_licenses= ValueSpecifies whether license agreements should be accepted during BOSinstallation. Before the installation process can complete, this attribute mustbe set to yes. The default value is accept_licenses=no. If thebosinst_data resource resides on the NIM master, theACCEPT_LICENSES field in the bosinst_data resource can also be set toyes. You can also set the NIM_LICENSE_ACCEPT global environmentvariable to yes on the NIM master.

–a adapter_def= ValueSpecifies the directory containing secondary adapter definition files. Thenimadapters command parses a secondary–adapters stanza file to buildthe files required to add NIM secondary adapter definitions to the NIMenvironment as part of the adapter_def resource. The nimadapterscommand does not configure secondary adapters. The actual configuration


takes place during a nim –o bos_inst or nim –o cust operation thatreferences the adapter_def resource.

–a async= ValueSpecifies whether NIM should perform operations on group membersasynchronously and not wait for the operation to complete on one memberbefore beginning the operation on the next. The default value isasync=yes.

–a auto_expand= ValueIndicates whether to expand file systems when setting up a client for aforce_push installation. The default value is auto_expand=yes.

–a boot_client= ValueIndicates whether NIM should attempt to reboot the client immediately forBOS installation. The boot_client attribute is the converse of theno_client_boot attribute. The default value is boot_client=yes, indicatingthat NIM should attempt to reboot the client.

–a bosinst_data= ValueSpecifies the bosinst_data resource to use for nonprompted installation.

–a concurrent=ValueSpecifies the maximum number of machines from the selected group thatshould be installing at any given time. This attribute is only valid when thetarget of the operation is a machine group. If specified, NIM will monitor theprogress of all machines in the group and attempt to keep no more or lessthan the number specified installing until all machines in the group areinstalled.

–a filesets= ValueSpecifies a list of filesets to install on the target after BOS installation.

–a force_push= ValueIndicates whether or not a force_push installation should occur. Aforce_push should be used for installing machines that are running, but arenot configured with the NIM client fileset. See the force_push Attribute formore information.

–a group= ValueSpecifies the name of a resource group to use for installation. A resourcegroup can be specified as an alternative to specifying multiple resources asseparate attributes. If a resource group is specified, and it contains a SPOTand lpp_source, the spot and lpp_source attributes are no longerrequired.

–a image_data= ValueSpecifies an image_data resource to describe how physical and logicaldata is organized on the client.

–a installp_bundle= ValueSpecifies an installp_bundle resource that lists filesets to install on thetarget after BOS installation.

–a installp_flags= ValueTells installp how to apply the filesets specified by the filesets orinstallp_bundle attributes. The default value is installp_flags=–agQX.

–a mksysb= ValueProvides the run–time files for BOS and other filesets if the source attributeis mksysb. The level of BOS run–time files in the mksysb must be equal tothe level of the SPOT resource used for the installation.

If the level of the SPOT resource is greater than the level of the mksysbresource, then an lpp_source resource must be used and match the level


of the SPOT resource. When this situation occurs, an update operation isperformed by default.

–a no_client_boot= ValueIndicates whether the target should remain in the NIM environment afterinstallation completes. The default value is no, indicating that the targetsystem should remain in the NIM environment.

–a physical_loc= ValueSpecifies the physical location code or AIX location code of the installationdisk to the BOS installation process. This attribute allows you to specify thelocation code for the installation disk or disks on the command line, andallows you to have a generic bosinst.data file that does not containlocation code information.

To determine a disk’s physical location code, type the following:

lsdev –Cc disk –l hdisk0 –F ”name physloc”

–a preserve_res= ValueIndicates whether resources in non–rootvg file systems should bepreserved on the client system being installed. The default value ispreserve_res=no.

–a resolv_conf= ValueSpecifies the resolv_conf resource to use for configuring domain andname resolution on a client.

–a script= Value Specifies the script resource to be run on the target system after allsoftware has been installed.

–a set_bootlist= ValueIndicates whether NIM should set the bootlist of the client so that the clientboots over the network on the next reboot. Usually, set_bootlist would beyes if the client is not going to be rebooted immediately for installation(no_client_boot=yes or boot_client=no). The default value isset_bootlist=no.

–a show_progress= ValueIndicates whether status should be displayed for each group member whenthe installation target is a group of machines. The default value isshow_progress=yes.

–a time_limit= ValueSpecifies the maximum number of hours that should elapse before ceasingto initiate installation of additional members of the selected group ofmachines. This value can only be specified when limiting the number ofconcurrent operations on a group.

–a verbose= ValueDisplays information for debugging. Valid values are 1–5. Use verbose=5to show maximum detail. The default is to show no debugging output.

When a bos_inst operation is performed on a client, the following occurs:

On the SPOT server:

1. A link is created in /tftpboot to a boot image matching the platform type, kernel type,and network adapter of the client.

2. The /etc/bootptab file is updated with client information to allow the boot image to beused.

3. A ClientName.info file is created in /tftpboot to provide client–specific installation andconfiguration information in the boot environment.


4. The /etc/tftpaccess.ctl file is modified, if necessary, to allow access to the /tftpbootdirectory.

On the target system:

1. The bootlist is modified so the network adapter is the default boot device for normalmode boot, unless no_client_boot=yes, set_bootlist=no, and force_push=no arespecified.

2. The client is rebooted to begin the installation, unless no_client_boot=yes,boot_client=no, and force_push=no are specified.

When the client boots over the network adapter, it obtains the boot image from the SPOTserver. The boot image configures devices and sets up the machine for the BOS installation.The Client.info file is transferred to the client machine; and based on its contents, thenetwork adapter is configured, routes are added, and NIM resources are mounted in theboot environment. Processing control is then passed to the BOS installation program.

NIM BOS Installation Details

The BOS installation program requires access to an image that contains the BOS run–timefiles. This image is used by the BOS installation program to populate the target’s /usr filesystem. In the NIM environment, this image can come from one of the following resources:

• A BOS run–time image that is part of the lpp_source resource that has been allocatedto the target

• A SPOT resource that has been allocated to the target

• A mksysb image that has been allocated to the target

A spot and lpp_source are always required to support the bos_inst rte operation. Abos_inst mksysb operation only requires a spot resource be used.

To indicate which BOS image to use, specify the source attribute when performing thebos_inst operation. The source attribute may have one of the following values:

rte When an rte value (the default) is used for the source attribute, NIMdirects the BOS installation program to use the BOS run–time image that isin the lpp_source directory. This image contains only the BOS run–timefiles; it does not contain any optional software packages. Selecting an rtesource may increase the BOS installation time, because the BOSinstallation program installs the appropriate device support after populatingthe target’s /usr file system to make the target viable. The installation timemay also be increased due to additional installp activity during the NIMcustomization phase.

Note: The rte source must be used when performing BOSmigration installation.

mksysb Using mksysb as the source results in a target machine that has the sameconfiguration as the machine from which the mksysb image was created.This may save installation and configuration time. The mksysb imagescould be very large, and the installation will fail if the target does not haveenough disk space to accommodate the image.

After the installation is initiated from the master, the NIM master attempts to contact thetarget and execute a script that will force the system to reboot. The target system issues aBOOTP request to the server after it has shut down. The bos_inst operation is consideredcomplete even if the target does not immediately issue a BOOTP request. The target mustissue a BOOTP request to load a network boot image from the server to start theinstallation.

If the master is unable to contact the target system for any reason (for example, the systemis turned off, it is not a running NIM client, or there is a network problem), a message is


displayed and user intervention is then required at the target to issue the BOOTP requestusing the IPL ROM. See Booting a Machine Over the Network on page A-2.

By default ( no_nim_client=no ), NIM also includes the customization required for thetarget to remain a NIM client after the install. This customization includes the installation andconfiguration of the bos.sysmgt.nim.client fileset and its requisite filesets,bos.net.tcp.client and bos.net.nfs.client, so that the NIM master can communicate withand control the client after installation. The installp_flags are passed to the installpcommand for installing the software on the standalone client. The filesets attribute can beused to install a list of additional filesets or software packages from the allocatedlpp_source.

To display BOS installation status information while the installation is progressing, enter thefollowing command on the master:

lsnim –a info –a Cstate ClientName

OR

lsnim –l ClientName

Errors in the allocation of a nim_script or boot resource type are fatal errors because thenetwork BOS installation process cannot proceed without these resources. On the otherhand, any error encountered during the attempt to cause the target to issue a BOOTPrequest is a nonfatal error to NIM because, at that point, NIM has successfully initialized theenvironment to perform a network installation. As soon as the target has successfullyloaded its allocated network boot image, the BOS installation process begins.

force_push Attribute

When assigned a value of yes, the force_push attribute tells NIM that the target of thebos_inst operation does not necessarily have the bos.sysmgt.nim.client fileset installedand configured. NIM will attempt to NFS mount or copy the minimal client support to thetarget system to perform an unattended installation or migration of the base operatingsystem. If client support is copied to the target machine, NIM will automatically expand thenecessary file systems on the target unless the auto_expand attribute to bos_inst is set tono.

The force_push attribute requires that the client grant root rsh permissions to the masterand that the key on the client be in the normal position. The force_push attribute alsorequires that a bosinst_data file be allocated to the target machine to indicate that ano–prompt installation should occur. The force_push attribute is set to yes by setting theForce Unattended Installation Enablement? option to yes when using SMIT to perform thebos_inst operation.

boot_client Attribute

When assigned a value of no, the boot_client attribute is used to instruct NIM not toattempt to initiate the BOS installation on the target machine after setting up the installationwith the bos_inst operation. This allows a BOS installation to be set up while deferring theactual installation until the client is rebooted at a later time. Also, if the client is not a runningmachine, this attribute will avoid waiting for the reboot attempt to time–out or fail. If theinstallation of the client system is going to be initiated later from the server, the normal modeboot device list on the client must be set so that a network boot is attempted when the clientis rebooted. No attempt is made to modify the boot list when boot_client is set to no unlessthe force_push or set_bootlist attributes are specified and set to a value of yes. Theboot_client attribute is set to no by setting Initiate Boot Operation on Client to no whenusing SMIT to perform the bos_inst operation.


set_bootlist Attribute

The set_bootlist attribute can be used with the boot_client attribute to modify the bootdevice list on the client for normal mode so a network boot is attempted when the client isrebooted. It is not necessary to specify the set_bootlist attribute if the force_push attributeis set to yes or if boot_client is unspecified or set to yes. In both instances, the boot list willbe modified as the default. The only valid values for set_bootlist are yes and no. Theset_bootlist attribute is set to yes by setting Set Boot List if Boot not Initiated on Client?when using SMIT to perform the bos_inst operation.

preserve_res Attribute

The preserve_res attribute can be used to preserve the NIM database definitions forresources residing on a NIM client that is being reinstalled. When set to yes, any resourcesthat reside in file systems which are being preserved by the BOS installation process willalso be preserved.

change

The change operation is used to modify attributes of NIM objects. The command line syntaxis as follows:

nim –F –o change –a Attribute = Value ... TargetName |

TargetNames

–F (optional) Tells NIM to force the operation if the target is currently in use.

The target of a change operation can be any network, machine,resource, or group in the NIM environment. Not all attributes can bemodified on targets. Usually, the attributes are changed automaticallyas parts of other operations, so there is little need for you to use thechange operation explicitly.

check

The check operation is used to verify the usability of a machine or resource in the NIMenvironment.

The command line syntax for the check operation is as follows:

nim –F –o check –a debug= Value TargetName | TargetNames

The target of a check operation can be any NIM client, a group of NIM clients, a SPOTresource, or an lpp_source resource.


The flags and attributes that can be specified for the check operation are as follows:

–F (optional) Tells NIM to ”force” the operation if the target iscurrently in use. If the –F flag is specified when thetarget is a SPOT resource, it will force the SPOT ’snetwork boot images to be rebuilt. The –F flag istypically not required when performing the checkoperation on client machines.

–a debug= Value (optional) Builds a SPOT ’s network boot images in debug modeif debug=yes is specified. This attribute is only valid ifthe target is a SPOT resource. The default value isdebug=no. For more information on the debugattribute, refer to Producing Debug Output from aNetwork Boot Image on page 30-4.

When applied to NIM clients, the check operation updates the machine state (Mstate) ofthe client. A ping test is performed to check whether the client is reachable. After the checkoperation is performed, the client’s Mstate is set to either running or not running.

When applied to SPOT resources, the check operation performs root synchronization fordiskless and dataless clients and rebuilds the SPOT ’s network boot images, if necessary.

When applied to lpp_source resources, the check operation rebuilds the table of contents(.toc) file in the lpp_source directory. It also determines whether all filesets are included inthe resources to qualify the lpp_source for the simages attribute.

cust

The cust operation is used to install software filesets and updates on standalone clients andSPOT resources.

See Customizing NIM Clients and SPOT Resources for information on performing asoftware customization of standalone NIM clients.

The command line syntax for the cust operation is as follows:

nim –o cust –a Attribute = Value ... TargetName | TargetNames

The target of a cust operation can be a standalone NIM client, a group of standalone NIMclients, or a SPOT resource.

The following are required attributes that can be specified for the cust operation:

–a filesets= Value Specifies a list of filesets to install on the target. Thisattribute is required unless an installp_bundle is usedfor the operation.

–a installp_bundle= Value Specifies an installp_bundle resource that lists filesetsto install on the target. This attribute is required unlessthe filesets attribute is specified.

–a lpp_source= Value Identifies the lpp_source resource that will provide theinstallation images for the cust operation.


The following are optional attributes that can be specified for the cust operation:

–a accept_licenses= Value Specifies whether software licenses should beautomatically accepted during installation. Ifaccept_licenses=yes, the –Y flag is passed on theinstallp command and licenses are automaticallyaccepted. If accept_licenses=no, licenseprocessing is controlled by the installp_flags attribute.The default value is accept_licenses=no.

–a async= Value Specifies whether NIM should perform operations ongroup members asynchronously and not wait for theoperation to complete on one member before beginningthe operation on the next. The default value isasync=yes.

–a concurrent =Value Specifies the maximum number of machines from theselected group that should be installing at any giventime. This attribute is only valid when the target of theoperation is a machine group. If specified, NIM willmonitor the progress of all machines in the group andattempt to keep no more or less than the numberspecified installing until all machines in the group areinstalled.

–a fix_bundle= Value Contains a list of fixes to install on the target. Fixesshould be listed in the fix_bundle resource by APARnumber with one number per line.

–a fixes= Value Identifies a list of fixes to install on the target. Fixesshould be listed by APAR number. For example,fixes=”IX12345 IX54321 ”.

–a group= Value Specifies the name of a resource group to use for theinstallation. A resource group can be specified as analternative to specifying multiple resources as separateattributes. If a resource group is specified, and itcontains an lpp_source, the lpp_source attribute is nolonger required.

–a installp_flags= Value Identifies the flags that tell installp how to apply thefilesets specified by the filesets, installp_bundle,fixes, and fix_bundle attributes. The default value isinstallp_flags=agQX.

–a resolv_conf= Value Specifies a resolv_conf resource for configuringdomain and name resolution on a client.

–a script= Value Specifies a script resource to be run on the targetsystem after all software has been installed.

–a show_progress= Value Indicates whether status should be displayed whilesoftware is installed. The default value isshow_progress=yes.

–a time_limit =Value, Specifies the maximum number of hours that shouldelapse before ceasing to initiate installation ofadditional members of the selected group of machines.This value can only be specified when limiting thenumber of concurrent operations on a group.


deallocate

The deallocate operation is used to unlock and unexport resources when they are nolonger needed by NIM clients. It is generally unnecessary to perform explicit deallocationsafter NIM operations, because upon successful completion, operations will automaticallydeallocate resources from the clients.

The command line syntax for the deallocate operation is as follows:

nim –o deallocate –a ResourceType = ResourceName ... –a subclass=all

TargetName | TargetNames

The target of a deallocate operation may be a NIM client or group of NIM clients.

The following list includes all the attributes that can be specified for the deallocateoperation:

–a ResourceType=ResourceName Specifies the resource to deallocate from theclient, for example, lpp_source=42_images.This attribute is required.

–a subclass=all Specifies that all resources should bedeallocated from the target. This attribute isoptional.

When a resource is deallocated from a client, the /etc/exports file on the resource server ismodified to unexport the resource from the client. The allocation count for the resource isalso decremented.

define

Creates objects in the NIM environment. Networks, machines, and resources can becreated using the define operation.

The command line syntax for the define operation is as follows:

nim –o define –t ObjectType –a Attribute = Value ...

ObjectName

The attributes for the define operation vary for the different object types. For a completedescription of the attributes required to define the various NIM objects, see NIM Networks,NIM Machines, NIM Resources, and NIM Groups.

diag

The diag operation is used to prepare resources for a client to be network–booted intodiagnostics mode.

The command line syntax for the diag operation is as follows:

nim –o diag –a Attribute = Value ... TargetName | TargetNames

The target of a diag operation can be any standalone NIM client or group of standalone NIMclients.

The following are required attributes that can be specified for the diag operation:

–a spot= Value Specifies the SPOT resource to be used toprovide network boot and diagnostics support.


The following are optional attributes that can be specified for the diag operation:

–a group= Value Specifies the name of a resource group to use for theoperation. A resource group can be specified as analternative to specifying multiple resources as separateattributes.

–a verbose= Value Displays information for debugging. Valid values are 1–5.Use verbose=5 to show maximum detail. The default is toshow no debugging output.

dkls_init

The dkls_init operation is used to prepare resources for use by a diskless client.

The command line syntax for the dkls_init operation is as follows:

nim –o dkls_init –a Attribute = Value ... TargetName |

TargetNames

The target of a dkls_init operation can be any diskless NIM client or group of diskless NIMclients.

The following are required attributes that can be specified for the dkls_init operation:

–a dump= Value Specifies the dump resource that contains client dumpfiles.

–a paging= Value Specifies the paging resource that contains client pagingfiles.

–a root= Value Specifies the root resource that contains the client root (/)directories. The root resource must be served by the samemachine that serves the SPOT.

–a spot= Value Specifies the SPOT resource to be used to provide networkboot support and the /usr file system for clients.

The following are optional attributes that can be specified for the dkls_init operation:

–a group= Value Specifies the name of a resource group to use for theinstallation. A resource group can be specified as analternative to specifying multiple resources as separateattributes.

–a home= Value Specifies the home resource that contains client /homedirectories.

–a resolv_conf= Value Specifies the resolv_conf resource to configure DomainName Protocol name server information on the client.

–a shared_home= Value Specifies the shared_home resource that contains acommon /home directory for multiple clients.

–a size= Value Specifies the size in megabytes for client paging files.

–a tmp= Value Specifies the tmp resource that contains client /tmpdirectories.


The dkls_init operation populates client directories and creates client paging and dumpfiles. A network boot image is also allocated to the client. When the client boots over thenetwork, it obtains the boot image and is configured to mount the remaining resources.


dtls_init

The dtls_init operation is used to prepare resources for use by a dataless client.

The command line syntax for the dtls_init operation is as follows:

nim –o dtls_init –a Attribute = Value ... TargetName |

TargetNames

The target of a dtls_init operation can be any dataless NIM client or group of dataless NIMclients.

The following are required attributes that can be specified for the dtls_init operation:

–a dump= Value Specifies the dump resource that contains client dumpfiles.

–a spot= Value Specifies the SPOT resource to be used to provide networkboot support and the /usr file system for clients.

–a root= Value Specifies the root resource that contains the client root (/)directories. The root resource must be served by the samemachine that serves the SPOT.

The following are optional attributes that can be specified for the dtls_init operation:

–a paging= Value Specifies the paging resource containing client paging files.

–a group= Value Specifies the name of a resource group to use for theinstallation. A resource group can be specified as analternative to specifying multiple resources as separateattributes.

–a home= Value Specifies the home resource that contains client /homedirectories.

–a resolv_conf= Value Specifies the resolv_conf resource to configure DomainName Protocol name server information on the client.

–a shared_home= Value Specifies the shared_home resource that contains acommon /home directory for multiple clients.

–a size= Value Specifies the size in megabytes for client paging files.

–a tmp= Value Specifies the tmp resource that contains client /tmpdirectories.


The dtls_init operation populates client directories and creates client paging and dumpfiles. A network boot image is also allocated to the client. When the client boots over thenetwork, it obtains the boot image and is configured to mount the remaining resources.

fix_query

The fix_query operation is used to display whether specified fixes are installed on a clientmachine or a SPOT resource.

The command line syntax for the fix_query operation is as follows:

nim –o fix_query –a Attribute = Value ... TargetName |

TargetNames

The target of a fix_query operation can be any standalone NIM client, group of standaloneNIM clients, or SPOT resource.


The following are optional attributes that can be specified for the fix_query operation:

–a fix_bundle= Value Specifies a fix_bundle resource containing a list of fixkeywords. This attribute is required unless the fixesattribute is specified for the operation.

–a fixes= Value Specifies a list of keywords for the fix_query operation.Fix keywords are APAR numbers used to identifysoftware updates that can span multiple filesets. Thisattribute is required unless a fix_bundle is used for theoperation.


–a fix_query_flags= Value Tells the fix_query operation how to displayinformation. Valid flags are those used by the instfixcommand.

–a show_progress= Value Indicates whether status should be displayed as theoperation is performed. The default value isshow_progress=yes.

Note: There are no required attributes for the fix_query operation.

lppchk

The lppchk operation is used to verify that software was installed successfully by runningthe lppchk command on a NIM client or SPOT resource.

The command line syntax for the lppchk operation is as follows:

nim –o lppchk –a Attribute = Value ... TargetName | TargetNames

The target of a lppchk operation can be any standalone NIM client, a group of standaloneNIM clients, or a SPOT resource.

The following are optional attributes that can be specified for the lppchk operation:


–a filesets= Value Specifies a list of filesets on the target on which thelppchk operation will be performed.

–a lppchk_flags= Value Tells the lppchk command how to perform softwareverification.


–a verbose= Value Displays information for debugging. Valid values are1–5. Use verbose=5 to show maximum detail. Thedefault is to show no debugging output.

Note: There are no required attributes for the lppchk operation.


lppmgrThe NIM lppmgr operation helps to manage base installation images and update images inan lpp_source. Although the lppmgr command is a separate command, it does use NIMobjects as parameters. By having the lppmgr operation in NIM, the lppmgr command iscalled by NIM to be executed on lpp_source resources on other servers, and allows NIM todo sufficient checking of the lpp_source before and after lppmgr is executed. The format ofthe operation will be as follows:

The format of the command is as follows:

nim –o lppmgr –a lppmgr_flags=<flags> <lpp_source_object>

The NIM lppmgr operation is also available in SMIT using the nim_lppmgr fast path.

The lppmgr operation does not check the lppmgr_flags attribute for conflicts.

Note: Do not use the –p flag for prompting to move or remove installationimages.

To list the names of duplicate filesets which should be removed with space usageinformation, type the following:

nim –o lppmgr –a lppmgr_flags=”–lsb” lpp_source1

For more information on the lppmgr command, see the AIX 5L Version 5.2 CommandsReference.

maint

The maint operation is used to uninstall software filesets and commit and reject updates onstandalone clients and SPOT resources.

The command line syntax for the maint operation is as follows:

nim –o maint –a Attribute = Value ... TargetName | TargetNames

The target of a maint operation can be a standalone NIM client, a group of standalone NIMclients, or a SPOT resource.

The following are required attributes that can be specified for the maint operation:

–a installp_flags= Value Identifies the flags that tell installp what to do with theinstalled software.

The following are optional attributes that can be specified for the maint operation:


–a filesets= Value Specifies a list of filesets to be maintained on thetarget.



–a installp_bundle= Value Specifies an installp_bundle resource that contains alist of filesets to be maintained on the target.

–a show_progress= Value Indicates whether status should be displayed asmaintenance is performed. The default value isshow_progress=yes.

maint_boot

The maint_boot operation is used to prepare resources for a client to be network–bootedinto maintenance mode.

The command line syntax for the maint_boot operation is as follows:

nim –o maint_boot –a Attribute = Value ... TargetName |

TargetNames

The target of a maint_boot operation can be any standalone NIM client or group ofstandalone NIM clients.

The following are required attributes that can be specified for the maint_boot operation:

–a spot= Value Specifies the SPOT resource to be used to providenetwork boot and maintenance mode support.

The following are optional attributes that can be specified for the maint_boot operation:

–a group= Value Specifies the name of a resource group to use for theoperation.


After the maint_boot operation is performed, the client must be rebooted over the networkto load the network boot image and enter maintenance mode.

reboot

The reboot operation is used to reboot a NIM client machine.

The command line syntax for the reboot operation is as follows:

nim –o reboot –a Attribute = Value ... TargetName | TargetNames

The target of a reboot operation can be any standalone NIM client or group of standaloneNIM clients.

The following are optional attributes that can be specified for the reboot operation:

–a inst_warning= Value Indicates whether a warning should be displayed towarn users that the machine will be rebooted. Thedefault value is inst_warning=yes.

Note: There are no required attributes for the reboot operation.


remove

The remove operation is used to remove objects from the NIM environment. The commandline syntax is as follows:

nim –o remove TargetName | TargetNames

The remove operation does not take any attributes. The target of this operation can be anynetwork, machine, resource, or group in the NIM environment.

reset

The reset operation is used to change the state of a NIM client or resource, so NIMoperations can be performed with it. A reset may be required on a machine or resource ifan operation was stopped before it completed successfully.

The command line syntax for the reset operation is as follows:

nim –F –o reset TargetName | TargetNames

The target of a reset operation can be any NIM client, a group of NIM clients, or a SPOTresource.

The following list includes all the flags and attributes that can be specified for the resetoperation:

–F (optional) Tells NIM to ”force” the operation if the target iscurrently in use.

When applied to NIM clients, the reset operation updates the control state (Cstate) of theclient. After the reset operation is performed, the client’s Cstate is set to ready, and it ispossible to perform NIM operations on the client. Although the Cstate of the client is resetby the operation, resources are not deallocated automatically. For information ondeallocating resources, see deallocate on page 27-45.

When applied to SPOT resources, the reset operation updates the resource state (Rstate)of the SPOT. After the reset operation is performed, the SPOT ’s Rstate is set to ready, andyou can use the SPOT in NIM operations.

select

The select operation is used to include and exclude group members from operationsperformed on the group.

The command line syntax for the select operation is as follows:

nim –o select –a Attribute = Value ... TargetName | TargetNames

The target of a select operation must be a group of NIM clients.

The following are optional attributes that can be specified for the select operation:

–a exclude= Value Specifies the name of the group member to excludefrom operations on the group.

–a exclude_all= Value Indicates that all members of the group should beexcluded from operations on the group. Valid valuesare yes and no.

–a include= Value Specifies the name of the group member to include inoperations on the group.


–a include_all= Value Indicates that all members of the group should beincluded in operations on the group. Valid values areyes and no.


To display the group members that are included and excluded from operations, use thelsnim –g GroupName command syntax.

showlog

The showlog operation is used to list software installed on a NIM client or SPOT resource.

The command line syntax for the showlog operation is as follows:

nim –o showlog –a Attribute = Value ... TargetName |

TargetNames

The target of a showlog operation can be any standalone NIM client, a group of standaloneNIM clients, or a SPOT resource.

The following are optional attributes that can be specified for the lppchk operation:

–a full_log= Value Indicates whether the entire log is displayed or only thelast entry. The default value is full_log=no.

–a log_type= Value Specifies the type of log to display. The log typessupported for both standalone clients and SPOTresources are:

bootMachine’s boot log

bosinstOutput from the BOS installation program

devinstOutput from the installation of key system anddevice–driver software

lppchkLog of the output from the lppchk operation executedon a standalone NIM client

nimerrErrors encountered during execution of the nimcommand

niminstOutput from the installation of user–specifiedsoftware (including installation of NIM client softwareduring a bos_inst operation)

scriptOutput from any configuration script resourcesallocated for a bos_inst operation.




Note: There are no required attributes for the showlog operation.

showres

The showres operation is used to display the contents of a resource. The contentsdisplayed will be appropriate for the type of resource on which the operation is run.

The command line syntax for the showres operation is as follows:

nim –o showres –a Attribute = Value ... TargetName

The target of a showres operation may be a SPOT, lpp_source, script, bosinst_data,image_data, installp_bundle, fix_bundle, resolv_conf, exclude_files, or an adapter_defresource.

The following are optional attributes that can be specified for the showres operation:

–a client= Value Specifies which client’s secondary adapter configuration file is displayedfrom an adapter_def resource. This attribute is only applicable when thetarget of the operation is an adapter_def resource.

–a filesets= ValueSpecifies a list of filesets for which information should be displayed. Thisattribute is only applicable to lpp_source and SPOT targets.

–a installp_flags= ValueSpecifies flags that tell the installp command how to format the display offilesets. This attribute is only applicable to lpp_source and SPOT targets.

–a instfix_flags= ValueSpecifies flags that tell the instfix command how to format the display offixes. This attribute is only applicable to lpp_source targets.

–a lslpp_flags= ValueSpecifies flags that tell the lslpp command how to format the display ofinstalled software. This attribute is only applicable to SPOT targets.

–a reference= ValueSpecifies a reference machine or SPOT resource for fileset comparison.This attribute is only applicable when the target of the operation is anlpp_source. Available filesets in the lpp_source are compared againstinstalled filesets in the reference machine or SPOT. If the showresoperation is performed from a NIM client, the reference attribute isautomatically set to the name of the client.

–a resource= ValueSpecifies the name of the resource whose contents should be displayed.This attribute is only necessary when the showres operation is performedfrom a NIM client.

–a sm_inst_flags= ValueSpecifies flags that tell the sm_inst command how to format the display offilesets. This attribute is only applicable to lpp_source and SPOT targets.This attribute must be used in conjunction with the reference attribute andis normally used only within the SMIT application.

Note: There are no required attributes for the showres operation.

• When the target of the showres operation is a SPOT, the list of filesets installed in theSPOT is displayed.

• When the target of the showres operation is an lpp_source, the list of filesets containedin the lpp_source is displayed.

• For all other resources that are valid targets for the showres operation, the charactercontents of the files are displayed.


sync_roots

The sync_roots operation is used to verify that diskless and dataless clients have thecorrect root files for the SPOT resource they use.

The command line syntax for the sync_roots operation is as follows:

nim –F –o sync_roots –a num_parallel_syncs= Value TargetName

The target of a sync_roots operation must be a SPOT resource.

The following are optional flags and attributes that can be specified for the sync_rootsoperation:

–a num_parallel_syncs= Value Specifies the number of client root directories tosimultaneously synchronize with the SPOT ’s rootfiles. Valid values are numeric. The default value isnum_parallel_syncs=5.

–F Specifies that NIM should force the operation.

A sync_roots operation can be performed automatically when the check operation isperformed on a SPOT.

unconfig

The unconfig operation is used to unconfigure the NIM master. The unconfig operationmust be performed before the NIM master can be reconfigured or the NIM master filesetcan be uninstalled. Attention: Performing the unconfig operation removes all informationfrom the NIM database and should be used with caution.

The command line syntax for the unconfig operation is as follows:

nim –o unconfig master

The target of the unconfig operation must be the NIM master.

No attributes can be specified for the unconfig operation.

The unconfig operation completely unconfigures the NIM master by performing thefollowing:

• Removes the nimesis and nimd daemon entries from the System Resource Controller(SRC)

• Removes all data from the nim_attr and nim_object databases

updateThe NIM update operation updates lpp_source resources by adding and removingpackages. The format of the command is as follows:

nim –o update –a packages=<all | list of packages with levels optional> \

[–a gencopy_flags=<flags>] ] [–a installp_bundle=<bundle_file>] \

[–a smit_bundle=<bundle_file>] [–a rm_images=<yes>] \

[–a source=<dir | device | object>] <lpp_source_object>

The NIM update operation is also available in SMIT using the nim_update fast path.

The source attribute must be a directory or device that is local to the server of the targetlpp_source resource or an existing NIM lpp_source resource. The default operation is toadd packages to the target lpp_source. If the rm_images attribute is present, the operationwill remove packages from the lpp_source. A user must specify either the source orrm_images attribute and must specify the packages, installp_bundle, or smit_bundleattribute, but not more than one.


Generally, the all keyword means to perform a multi–volume installation when the source isa CD–ROM. However, the update operation will only do a single volume copy (equivalent topassing the gencopy –S flag).

To add packages to an lpp_source resource, run the following:

# nim –o update –a packages=all –a source=/tmp/inst.images lpp_source1

To remove packages from an lpp_source resource, run the following:

# nim –o update –a packages=”bos.games 5.1.0.25 bos.sysmgt.nim” –a

rm_images=yes lpp_source2


NIM Groups

NIM groups are essentially lists of machines and resources. Groups can be used in NIMoperations to simplify repetitive administrative tasks.

Machine Groups

Machine groups are used to represent collections of machines of similar types. Themachine types in a group must all be the same (for example, standalone, diskless, ordataless) and of the same architecture, because some NIM operations are restricted tocertain target types. The first member added to a group determines the architecture andtype of machine the group can contain. By having multiple machines defined as members ofa single group, you can perform a single operation on all machines by specifying the groupas the target. NIM iterates through the list of machines in the group, and performs theoperation on each member, in turn.

Group members can be excluded from NIM group operations by marking them for exclusionbefore performing the operation. Excluding a member marks the member list in the grouprepresentation, so NIM skips the member when it iterates through the list. Excluding amember does not change the definition of the client in the NIM database. For information onmarking group members for inclusion and exclusion, see Including and Excluding a GroupMember from Operations on the Group.

Machines can be added or removed from groups, as well as be members of multiplegroups. When all members of a group are removed, the group definition in the NIMdatabase is automatically deleted. For information on adding and removing group members,see Adding New Members to Machine Groups and Removing Members from MachineGroups.

The command line syntax for defining a machine group is:

nim –o define –t mac_group –a Attribute = Value ...

MachineGroupName

where the following attributes are optional:

add_member= Value Specifies the name of a NIM client to add to the machinegroup. NIM automatically converts this attribute to amember attribute with an appropriate sequence number.

member= Value Specifies the name of a NIM client to add to the machinegroup. This attribute requires a sequence number.

Operations performed on machine groups are, by default, performed asynchronously on thenon–excluded members of the group. NIM does not wait for an operation to complete onone group member before initiating the operation on the next member. When performingoperations asynchronously, it is not possible for NIM to display all the output as it occurs oneach client. Therefore, you should use the lsnim command to check the states of the groupmembers to determine how far, and how successfully, the operations have executed. Iferrors do occur, the log files on client machines can be viewed using the NIM showlogoperation.

To change the behavior of NIM group operations from asynchronous to synchronous, usethe async=no attribute when running the nim command.


The number of machines permitted in a machine group is not explicitly limited by NIM.However, the following factors limit the number for practical reasons:

Operation being Performed Operations that are not resource–intensive (such as themaint or showlog operations) may be performed on agroup containing any number of machines. Operationsthat are resource–intensive (such as cust or bos_inst)are limited by the throughput of the network, the diskaccess throughput of the installation servers, and theplatform type of servers.

NFS Export Limitations The maximum number of hosts to which a file ordirectory may be exported with root permissions islimited by NFS to 256. Also, the length of a line in anexports file has an upper limit which could determinethe maximum number of machines permitted in agroup. For information on how to increase the numberof machines to which a resource can be allocated, referto Exporting NIM Resources Globally.

Resource Groups

Resource groups are used to represent collections of NIM resources. A resource group cancontain multiple installp_bundle and script resources, and one resource from each of theother types. If a resource group is allocated or specified for use in a NIM operation, allapplicable resources in the group are allocated to the target. The use of resource groupscan save NIM administrators from having to repeatedly specify the same set of resourcesindividually, when the allocation of a single resource group would suffice.

The command line syntax for defining a resource group is:

nim –o define –t res_group –a default= Value \

–a ResourceType = ResourceName ... ResourceGroupName

where the following attributes are optional:

default= Value Specifies whether a resource group should be madethe default. The default value is default=no.

ResourceType Specifies the type (for example, spot, lpp_source,script, etc.) and name of the resource to add to thegroup. One resource of each type may be specified,except for script and installp_bundle resources,which may have multiple resources participate in anoperation.

The allocation of individual resource group members can be overridden by specifyingadditional resource attributes for the members to be changed.

For example, the resource group, res_grp1, contains the spot1, lpp_source1,bosinst_data1, script1, and resolv_conf1 resources. To use the resource group toperform an rte bos_inst operation on client1, but using no bosinst_data resource, andusing resolv_conf2 instead of resolv_conf1, use the following command:

nim –o bos_inst –a source=rte –a group=res_group1 \

–a bosinst_data= –a resolve_conf=resolv_conf2 client1

A resource group can be specified as the default set of resources to use for all NIMoperations. This is done by setting the master’s default_res attribute to the name of theresource group that will be the default. When a default resource group is defined, theapplicable member resources will always be automatically allocated during NIM operations,unless they are specifically overridden.


To set the default resource group to res_group1, enter:

nim –o change –a default_res=res_group1 master

or enter:

nim –o change –a default=yes res_group1

To stop using a default resource group, enter:

nim –o change –a default_res=master

or enter:

nim –o change –a default=no res_group1

28-1Sample Files

Chapter 28. Sample Files

This chapter contains information about the following sample files:

• script Resource File on page 28-1

• Definition File for the nimdef Command on page 28-2

script Resource File

The following is an example of a customizing script that configures the target’s TCP/IPdomain name resolution and routing.

The resolv_conf resource should be used when installing clients running the latest versionof AIX.

#!/bin/ksh CUSTOMIZING SCRIPT to set the hostname,

# establish the nameserver and DNS domain name,

# and configure the routing table for the

# target standalone client

# Truncate the host name

# if the host name is set to the fully qualified host name

#

#NOTE: This procedure will NOT result in a truncated host name if

#the bos installation operation is installing a mksysb image

#(ie. –a source=mksysb) unless the bos_inst operation is

#instructed not to configure the target as a NIM client upon

#completion (ie. unless –a no_nim_client=yes is specified)

#

chdev –l inet0 –a hostname=$(/usr/bin/hostname | cut –d. –f1)

# Set Name server and Domain Name

if [[ –f /etc/resolv.conf ]]

then

/usr/sbin/namerslv –E ’/etc/resolv.conf.sv’

fi

/usr/sbin/namerslv –a –i ’9.101.1.70’

/usr/sbin/namerslv –c ’enterprise.ca’

# Flush routing table and add default route

/etc/route –n –f

odmdelete –o CuAt –q ”name=inet0 and attribute=route”

chdev –l inet0 –a route=net,,’0’,’9.101.1.70’


Definition File for the nimdef Command

The following is an example of a definition file for the nimdef command:

# Set default values.

default:

machine_type = standalone

subnet_mask = 255.255.240.0

gateway = gateway1

network_type = tok

ring_speed = 16

platform = rs6k

machine_group = all_machines


# Take all defaults.

lab1:


# Take all defaults and specify 2 additional attributes.

# The machine ”lab2” uses IPL ROM emulation, and will be added to

# the machine groups ”all_machines” (by default) and ”lab_machines”.

lab2:

ipl_rom_emulation = /dev/fd0

machine_group = lab_machines


# Take all defaults, but do not add the machine to the

# default group.

lab3:

machine_group=


# Take all defaults, but do not add ”lab4” to the default group

# ”all_machines”.

# Instead add it to the groups ”lab_machines” and ”new_machines”.

lab4:

machine_group =

machine_group = lab_machines

machine_group = new_machines

# Change the default ”platform” attribute.

default:

platform = rspc

# define the machine ”test1”

# Take all defaults and include a comment.

test1:

comments = ”This machine is a test machine.”

29-1Error and Warning Messages

Chapter 29. NIM Error and Warning Messages

This chapter contains information about Network Installation Management (NIM) error andwarning messages, with suggestions for resolving specific problems.

If an error condition is detected when a NIM command is executed, the command returns anerror message. If a NIM command returns a warning message, this indicates that either aless severe problem was encountered by NIM, or a problem was encountered in acommand called by NIM, and the severity of the problem cannot be readily determined byNIM. In the latter case, additional messages or output from the command often reveal thenature of the problem.

All NIM error messages begin with 0042 and are followed by a three–digit error code.Notes:

1. If you require usage information for a NIM command, type the command without anyparameters or with a question mark as a parameter (for example, nim –? ). Additionalinformation can be obtained from the lsnim command, which provides several options todisplay NIM help and usage information. For more information, refer to the –q, –O, and–P options of the lsnim command. You can also use the lsnim –p –a command todisplay information for all NIM classes, subclasses, types, and attributes. For example, todetermine the list of valid values for an attribute, enter:

lsnim –p –a AttributeName

2. In some cases, a nim or nimclient operation that is being blocked because an object isin a particular state may be permitted with the use of the force option (the –F flag).However, by using the force option, you may adversely affect part of the NIMenvironment by forcing an operation that should only proceed after other actions arecomplete. Use error messages that are displayed without using the force option todetermine if the force operation is a reasonable action.

3. If you believe that your problem is the result of a software defect, or if the User Actionsprovided here do not provide adequate resolution to a problem, contact your point ofsale.

Information about each message listed in this chapter is organized in the following manner:

Message Indicates the warning or error message ID number returned by thecommand

Explanation Describes what is likely to have caused the message to be displayed

User Action Suggests a possible resolution to the problem

Note: If a User Action for a given error or warning specifies using the lsnim command forrecovery hints, and if you are operating from a NIM client, use nimclient –llsnimOperations, substituting the suggested lsnim options as appropriate.

Message 0042–001

Explanation An error was detected by an underlying NIM method (asubcommand). This message describes where the error occurredwith respect to the NIM client or master and may be useful introubleshooting the problem. The messages that are displayedsubsequent to this error are normally the true source of the problem.

User Action Read the additional information and error messages, and refer totheir explanation and recovery hints as appropriate.


Message 0042–002

Explanation An interrupt signal has been received, perhaps because the userentered Ctrl–C or used the kill command on a NIM process.

User Action The NIM operation that was active has been interrupted. Perform theoperation again.

Note:This error is expected if it occurs after the nimclient –o bos_instoperation is performed on a client.

Message 0042–003 and 0042–004

Explanation An error has been returned from a system call.

User Action Fix the condition that caused the system call to fail and perform theoperation again.

Message 0042–005

Explanation The Object Data Manager (ODM) has returned an error.

User Action Fix the ODM problem and perform the NIM operation again.

Message 0042–006

Explanation Generic error message used for rarely occurring NIM errors.

User Action Phrases contained in this error message are constructed from debuginformation and from messages returned by commands called byNIM. If the content of the message does not give insight into the truecause of failure, contact your point of sale.

Message 0042–007

Explanation An internal NIM error has occurred.

User Action Try the operation again.

Message 0042–008

Explanation NIM has attempted to establish socket communications with aremote machine, and it has refused the connection.

User Action If the failing operation occurred on the master, verify that the masterhas rsh permissions on the client and that inetd is active on theclient; otherwise, verify that the nimesis daemon is active on themaster. If the failing operation was the niminit command on theclient, a possible cause of failure is that the master does not have anetwork object that corresponds to the client’s network. A networkobject that represents the client’s network needs to be added to thedatabase on the master; then a route needs to be added from themaster’s network to the client’s network.

If the failure occurs during operations initiated from a client, using thenimclient command, or during a NIM installation of the baseoperating system, the cpuid attribute on the client’s machinedefinition may be obsolete (for example, if the machine’s systemplanar was recently replaced). To guarantee that this is not the case,erase the cpuid from the machine definition by issuing the followingfrom the master:

nim –Fo change –a cpuid= ClientName


Message 0042–011

Explanation The /etc/niminfo file is not accessible.

User Action The niminfo file is required by all NIM commands and methods. Thisfile is created when the bos.sysmgt.nim.master andbos.sysmgt.nim.client packages are configured. If this file is notavailable, this indicates that the NIM package has not been initializedor that this file has been deleted. To create the niminfo file, executethe nimconfig command on the master or the niminit command onthe client. To recreate a deleted or corrupted niminfo file, enter fromthe master:

nimconfig –r

OR enter from the client:

niminit –aname= ClientName –amaster= MasterHostName

–amaster_port= MasterPortValue

Message 0042–012

Explanation The specified command may only be executed on the master.

User Action Execute the desired operation on the NIM master.

Message 0042–013

Explanation The global lock used for synchronized access to the NIM databasecould not be obtained.

User Action Try the operation again. If the same error is returned, verify thatthere are no active NIM commands. If this is true, remove the/var/adm/nim/glock file and try the operation again. If the file doesnot exist and the error persists, contact your point of sale.

Message 0042–014

Explanation An internal NIM error has occurred.

User Action Perform the remove operation on the NIM object followed by theappropriate define operation.

Message 0042–015

Explanation A syntax error has been detected.

User Action Refer to the appropriate man page for the NIM command and tryagain using valid syntax.

Message 0042–016

Explanation An invalid option has been specified.


Message 0042–017

Explanation An invalid value was specified for an option argument.



Message 0042–018

Explanation A required option was not supplied.


Message 0042–019

Explanation An option that requires an argument was specified without itsargument.

User Action Refer to the appropriate man page for the NIM command and tryagain, specifying the missing argument.

Message 0042–20

Explanation An operand was required but not supplied. Usually, the operand isthe NIM object to which a given operation is being applied (that is, aNIM name for a network, machine or resource object that is thetarget of the NIM operation).

User Action Refer to the appropriate man page for the NIM command and tryagain using valid syntax. If you do not know the name of an operand,and if the failing operation was targeted toward an existing NIMobject, enter:

lsnim –l –t ObjectType

OR

lsnim –l

to determine the operand name.

Message 0042–021

Explanation A NIM attribute was required for the operation.

User Action Specify the missing attribute. If the failing command is the nim ornimclient command, to obtain a list of attributes, enter from themaster:

lsnim –q ObjectName

OR

lsnim –q –t ObjectType

OR enter from the clients:

nimclient –l lsnimOptions

For the other NIM commands, see the appropriate NIM man page.

Message 0042–022

Explanation A value was specified that exceeds the bounds of acceptable values.

User Action Supply a value within the acceptable bounds.

Message 0042–023

Explanation The specified value is not valid.


User Action Try the command again with a valid value. To determine the validvalues for classes of objects and operations as they pertain to thoseobjects, enter:

lsnim –Pc ObjectClass

AND

lsnim –POc ObjectClass

where ObjectClass is one of machines, networks, or resources.

Message 0042–024

Explanation An invalid NIM object type was specified.

User Action Specify a valid NIM object type. See user actions for error 023 forlsnim options to determine a valid object type.

Message 0042–025

Explanation The specified operation cannot be supplied to the specified NIMobject.

User Action Specify an operation that can be applied to the object. Enter lsnim–O ObjectName for a list of valid operations that can be applied tothe object.

Message 0042–027

Explanation The specified object is missing an attribute that is required tocomplete the specified operation.

User Action Redefine the object that is missing an attribute by performing theremove operation followed by the define operation.

Message 0042–028 and 0042–029

Explanation The specified information cannot be supplied in the current context.

User Action Try the operation again without supplying the offending attribute.

Message 0042–030

Explanation A sequence number was opened to an attribute that doesn’t allowsequence numbers.

User Action Try the operation again without a sequence number on the offendingattribute.

Message 0042–031

Explanation An internal NIM error has occurred. NIM is unable to generate aunique object ID.

User Action Try the operation again.

Message 0042–032

Explanation The specified value for the attribute is not unique and it must be.

User Action Supply a unique value for the attribute.

Message 0042–033


Explanation The specified value is not unique and it must be. An attribute with asequence number requires a unique value.

User Action Supply a unique value.

Message 0042–034

Explanation The specified value is not unique and it must be.

User Action Supply a unique value.

Message 0042–035

Explanation NIM was attempting to access an attribute that had the specifiedcharacteristics, but the attribute doesn’t exist.

User Action Make sure the attribute exists and retry the operation.

Message 0042–036

Explanation The define operation failed for a resource because the specifiedserver does not have a standalone configuration.

User Action Try the operation again using a NIM client that is a standalonemachine.

Message 0042–037

Explanation The NIM state of the specified object prevents the operation fromsucceeding.

User Action NIM states are used to synchronize activity among NIM objects. Toperform the desired operation, the state of the specified object mustbe changed. If the specified object is in an unexpected state, checkthe system to make sure another user or process is not manipulatingthe object. Use the reset operation to set the object to a known stateand try the operation again.


Message 0042–038

Explanation An object that NIM would operate on is already locked and thuscannot be operated on.

User Action NIM object locks are used to synchronize activity among NIMobjects. These locks are temporary, so try the operation again aftersome delay. The value of the lock is the process ID of a NIM processthat is using the lock. If the lock persists and no NIM commands areactive, reset all NIM locks by stopping the nimesis daemon, thenrestarting it.

Message 0042–039

Explanation The operating system version or release level of the specified objectis unacceptable.

User Action Perform the desired operation on objects that have the appropriateoperating system version and release levels.

Message 0042–040

Explanation A NIM object could not be removed because it is being used bysome other NIM object.

User Action Remove all references to the object to be removed before theremove operation is specified. If NIM states are such that youcannot remove references to the object and you want to remove theobject anyway, provide the –F flag to the remove operation.

Message 0042–041

Explanation A specified value has already been defined to NIM.

User Action Specify a value that isn’t already known to NIM.

Note::If /etc/niminfo is the value and the NIM command producing thiserror is niminit, this means that niminit has already beenperformed. If you want to reinitialize your NIM master or client,deinstall the appropriate fileset, and then reinstall and reconfigurethe NIM master or client fileset.

Message 0042–042

Explanation The specified machine could not be reached with the ping commandfrom the master.

User Action If the operation you were attempting to perform requires that thetarget machine be running and that it can be reached, then verifythat the machine is currently running. If not, turn it on; otherwise,perform network diagnostic procedures to determine why the mastercould not reach the target machine.

Message 0042–043

Explanation The remove operation cannot be performed, because the targetmachine currently serves a NIM resource that has been allocated foruse. Performing the operation at this time could lead to processingfailures on clients that are attempting to use the served resources.

User Action You need to deallocate all resources that the target serves beforeyou can remove the machine.


Message 0042–044

Explanation You have specified a NIM attribute without an accompanying value.Most NIM attributes can only be specified with a value assigned tothem in the form of attr=value.

User Action Retry the operation with a value assigned to the specified attribute.

Message 0042–045

Explanation Some NIM attributes can be added to an object’s definition morethan once. In these cases, a sequence number is used to uniquelyidentify each attribute of that type. In this case, you have specifiedan attribute of this type without its required sequence number and,therefore, NIM is unable to determine which attribute you areattempting to specify.

User Action Verify the sequence number and try the operation again.

Message 0042–046

Explanation NIM was unable to perform an operation on the specified file. Thismay be due to the permissions on the file. The file usually needsread, write, and, in some cases, execute permissions for root.

User Action Change the permissions of the specified file and try the operationagain.

Message 0042–047

Explanation Some types of NIM resources may only be used by specific machinetypes. In this case, you attempted to allocate a NIM resource to atype of machine that is not allowed to use that type of resource.

User Action Specify a resource type that the machine is allowed to use whenperforming allocation for the target machine.

To determine the valid resource types, enter:

lsnim –p –s ResourceSubclassForMachineType

To view the subclasses that are available, enter: lsnim –p –S

Message 0042–048

Explanation When resource allocation is requested, NIM verifies that thedesignated client has the potential to communicate with the server ofthe resource. NIM does this by checking the NIM routing betweenthe network that the client’s primary interface connects to and all thenetworks that the server connects to. In this case, a NIM route ismissing between the client and the server.

User Action Either establish a NIM route between the client and the server orchoose a different resource to allocate.

Message 0042–049

Explanation Only one resource of this type may be allocated to the client and onehas already been allocated.

User Action Choose the resource that you want to use and deallocate thecurrently allocated resource of this type if you want to use the newone.


Message 0042–051

Explanation NIM was unable to resolve a host name to an IP address or the otherway around.

User Action All host names that are used in the NIM environment must beresolvable. Perform the appropriate network administration tasks toensure that the specified host name is resolvable and try theoperation again.

Message 0042–052

Explanation One or more NIM resources are still allocated to the machine thatyou have requested to be removed from the NIM environment. Toremove a machine, it cannot have any resources allocated to it.

User Action Deallocate all resources that have been allocated to the targetmachine and try the operation again.

Message 0042–053

Explanation You have specified the name of a NIM object that does not currentlyexist in the NIM environment. NIM can only operate on objects thathave been defined to NIM.

User Action Verify that you have spelled the name of the object correctly and thatit has already been defined. The name of a target machine for a NIMoperation must be the NIM name, not the host name. Enter:

lsnim –l –t ObjectType

OR

lsnim –l

to obtain listings of currently defined objects in the NIM environment.If you need to define the object, use the define operation.

Message 0042–055

Explanation Many NIM operations require a source for installable images. Youhave specified a source that cannot be used for this operation.Examples of valid sources for NIM operations are:

•

• /dev/rmt0, /dev/cd1 for lpp_source definition

• rte, spot, mksysb for bos_inst operation

User Action Try the operation again using a source that the operation can use.

Message 0042–056

Explanation You have specified the same attribute assignment more than once.

User Action Try the operation again using only one instance of the attributeassignment.

Message 0042–058

Explanation You have attempted to allocate a SPOT to a client whose primarynetwork interface type or platform is not supported by the SPOT. Fora client to use a SPOT, the SPOT must support the network interfacetype and platform of the client’s primary interface.


User Action Install the appropriate device support into the SPOT, which will allowthe SPOT to support the client’s primary interface type and platform,or choose a different SPOT that supports the client’s primaryinterface type and platform.

Message 0042–059

Explanation In an attribute assignment (in the form of attr = value ), thevalue you have specified represents a NIM object whose typeconflicts with the object type of the specified attr.

User Action Try the operation again using the attr that corresponds to the type ofobject that value represents.

Message 0042–060

Explanation You have specified multiple attribute assignments for an attribute thatmay only be specified once.

User Action Try the operation again, using only one instance of the attribute.

Message 0042–061

Explanation You have requested an operation to be performed on a NIM resourceobject that is currently allocated for client use. NIM is not allowingthis operation to be performed because it may interrupt the client’suse of the resource.

User Action Try the operation again when the resource is not allocated for clientuse. If necessary, try the force option (–F flag) to disregard thepreventive check by NIM. In some cases, NIM will allow theoperation to be performed.

Message 0042–062

Explanation The NIM object that was operated on is missing something that isrequired for its definition to be complete.

User Action List information about the object using the lsnim command. Eachitem that is missing from the object’s definition will be represented bya missing attribute. Perform the appropriate NIM operation that willadd the missing item to the object’s definition. For a SPOT, if networkboot images are missing, apply the check operation to the SPOT. Ifsoftware filesets are missing from a SPOT, allocate an lpp_sourcethat contains the required filesets and apply the cust operation to theSPOT.

Message 0042–063

Explanation Some NIM operations require access to one or more NIM resourcesto complete successfully. This access is granted through theallocate operation. In this case, you have not allocated all theresources that are required for this operation.

User Action Allocate all the required resources and try the operation again. For alist of required and optional resources for a given operation, enter:

lsnim –q Operation ObjectName

OR

lsnim –q Operation –t ObjectType


Message 0042–064

Explanation The machine that is the target of the requested operation currentlyserves a NIM resource that is allocated for client use. The requestedoperation cannot be performed until all resources that the targetserves have been deallocated for use.

User Action Deallocate all resources that the target serves and try the operationagain.

Message 0042–065

Explanation You have specified a name that is reserved for NIM internal use only.

User Action Try the operation again using a different name. To determine whatnames are reserved, enter:

lsnim –a reserved

Message 0042–066

Explanation You have specified one or more characters that are not allowed inNIM object names. NIM uses regular expressions to perform many ofits operations, so any character that has special meaning for regularexpressions cannot be used (for example, ^). Also, any characterthat has special meaning to the shell cannot be used (for example,/).

User Action Try the operation again using valid characters.

Message 0042–067

Explanation You have requested an operation to be performed on a NIM objectthat has been reserved for NIM internal use only.

User Action Try the operation again, using a NIM object that is not reserved. Todetermine what objects are reserved, enter:

lsnim –a reserved

Message 0042–069

Explanation The requested operation cannot be performed at this time because itconflicts with the current NIM state of the target. NIM uses states tosynchronize NIM activity so that operations don’t interfere with eachother.

User Action Try the operation again when the state changes or, if necessary, tryusing the force option (–F flag). In some cases, NIM will allow you tooverride this state checking.

If you encounter this error as a result of trying to remove, using thereset operation, the boot resource from a client that incorrectly hasa state of ”ready for a NIM operation”, you can remove the bootresource from the NIM master by entering:

/usr/lpp/bos.sysmgt/nim/methods/m_dealloc_boot

client_name

where client_name is the name of the NIM object for the client.


Message 0042–073

Explanation To perform customization on a machine, NIM constructs a shell scriptthat is executed on the target. To construct this script, some type ofresource that can be used for customization must be used. In thiscase, NIM could not create the customization script because noresources have been allocated to the target that could be used forcustomization purposes.

User Action Allocate one or more resources that can be used for customizationand try the operation again. To display the subclass of resources thatcan be used for customization, enter:

lsnim –p –s cust_res

Message 0042–074

Explanation You have specified an attribute assignment in which the valuerepresents a relative path name. NIM only allows absolute pathnames (that is, path names that begin with /) to be used.

User Action Try the operation again, using an absolute path name.

Message 0042–075

Explanation The requested operation requires that a NIM resource be exportedfor a machine’s use. In this case, NIM attempted to export theresource but an error was returned by an NFS utility.

User Action Fix the error condition that the NFS utility reported and try theoperation again.

Message 0042–076

Explanation You have specified a port number that is already in use.

User Action Try the operation again, using a port number that is currently notbeing used. Check the /etc/services file.

Note: NIM uses both the specified port number and its successor.Therefore, ensure that the port number after the specifiedport number is also free.

Message 0042–077

Explanation The niminit command is used to join the NIM environment. Whenexecuted, this command attempts to add routing information that theNIM master has determined the client needs to participate in the NIMenvironment. In this case, one or more of the required routes couldnot be added.

User Action Perform the appropriate network diagnostic task to determine whythe route could not be added.

Message 0042–078

Explanation You have specified a change to a NIM routing attribute in which thedestination network is different from its current value. This is notallowed because only the gateway field of the routing attribute maybe changed.


User Action If you are trying to change the connectivity between NIM networks,then you must remove the current NIM route by supplying a NULLvalue for the appropriate routing attribute. Otherwise, specify thesame destination network when attempting to change the gatewayfield of the routing attribute.

Message 0042–079

Explanation In the NIM environment, one resource may depend on another forinformation. In this case, an allocated resource has a dependency onthe resource you have specified for deallocation.

User Action Deallocate the resource that is dependent on the resource causingthe error.

Message 0042–081

Explanation NIM uses NFS to make remote resources available for client use. Toavoid NFS export errors, NIM enforces some restrictions on where aresource can be defined. In general, a NIM resource cannot bedefined within a directory that is already a NIM resource. Conversely,a NIM resource cannot be defined for a directory that alreadycontains an existing NIM resource.

User Action Move the resource to a location that adheres to NIM export rules andtry the operation again.

Message 0042–083

Explanation Each network communications adapter has an associated networkhardware address that is unique. In this case, you attempted todefine a NIM network interface using a network hardware addressalready being used by a NIM machine object.

User Action Only one NIM interface attribute may be defined for each networkcommunications adapter a client might have. If you are attempting toadd another interface definition, then verify that the hardwareaddress is correct. If so, then you must first change the interfaceattribute that is currently using that address. If not, try the operationagain with the correct hardware address.

Message 0042–084

Explanation The machine has already been configured to be a NIM master.

User Action If you want to reconfigure the machine as a NIM master, enter nim–o unconfig master, then deinstall and reinstall the masterfileset. You may then run the nimconfig command.

Message 0042–086

Explanation You have attempted to add a NIM route between two NIM networksthat already have a NIM route between them. Only one NIM routecan be specified between any two NIM networks.

User Action If you are attempting to change NIM routing, delete the existing NIMroute and try the operation again.


Message 0042–093

Explanation NIM attempted to create a directory, and the mkdir commandreturned an error.

User Action Fix the error reported by the mkdir command and try the operationagain.

Message 0042–109

Explanation To complete the requested operation, NIM requires information aboutone or more file systems about which it was unable to obtaininformation.

User Action Verify that the file systems exist. If not, either specify the correct pathname when performing the NIM operation or redefine the NIMenvironment so that all the participating file systems exist.

Message 0042–111

Explanation When a sequence number is specified for a NIM attribute, it must bewithin a specific range. You have specified a sequence number thatfalls outside of the acceptable bounds.

User Action Try the operation again using a sequence number that is within theacceptable bounds.

Message 0042–113

Explanation To complete the requested operation, NIM requires information aboutthe size of one or more objects, which NIM was unable to determine.

User Action If the object is a file or directory that does not exist, then create thefile or directory and try the operation again.

Message 0042–118

Explanation You have requested to change characteristics of a NIM network onwhich there is currently one or more active NIM operations. NIM isnot allowing the change because changing the networkcharacteristics at this time could result in failures in the activeoperations.

User Action Wait until the NIM resources allocated to machines that use thenetwork being changed have been deallocated and try the operationagain.

Message 0042–121

Explanation An invalid value has been specified.

User Action Try the operation again, using a valid value.

Message 0042–124

Explanation An NFS option was specified that is not supported.

User Action Try the operation again using valid NFS options. Refer to NFSProblem Determination in AIX 5L Version 5.2 System ManagementGuide: Communications and Networks.


Message 0042–129

Explanation An invalid resource type was specified for this operation.

User Action Use the lsnim –q Operation –t TargetType command to view a list ofrequired and optional resources for Operation when applied toTargetType.

Message 0042–130

Explanation You have specified an attribute that cannot be used for thisrequested operation.

User Action Try the operation again, without using the attribute you specified.

Message 0042–131

Explanation You have specified two or more attributes that conflict with eachother.

User Action Try the operation again, using only one of the attributes.

Message 0042–132

Explanation You have specified a value for an attribute assignment that is invalidin the context in which the operation is being performed.

User Action Try the operation again, using a different value for the attributeassignment.

Message 0042–133

Explanation The physical entity that is represented by the NIM resource objectyou have requested to be deleted could not be deleted.

User Action Delete the file or directory, using the rm command.

Message 0042–134

Explanation The operation you requested requires the designated target toreboot using a network boot image. NIM has automatically initializedthe environment to enable the target to do this; however, NIM wasunable to force the target to load the network boot image.

User Action Intervention at the target is required. Follow the procedures forinitiating a BOOTP request.

Message 0042–135

Explanation To synchronize NIM operations that can be initiated from a client oron the master, NIM keeps track of which machine (the client or themaster) is used to allocate the first resource to the client; thismachine is said to be in control. For example, if the first resourceallocation occurs from the client, then the client is in control. Once amachine has control, it remains in control until all resources for thatclient have been deallocated. You have requested an operation to beperformed from a machine that is currently not in control of thespecified target.

User Action Perform the desired operation from the machine that is in control ofthe target, or from the controlling machine deallocate the resources(to remove the control), or override this behavior by using the force(–F flag) option when performing the operation from the master.


Message 0042–136

Explanation The requested operation cannot be performed because a NIM routedoes not exist between two machines that participate in thisoperation.

User Action Establish a NIM route between the networks.

Message 0042–137

Explanation The /etc/niminfo file contains information about the NIMenvironment that all NIM commands require. In this case, the/etc/niminfo file is missing some information that is required tocontinue, which indicates that the file has been corrupted.

User Action Reinitialize the NIM environment.

Message 0042–138

Explanation Unable to update the rhost file.

User Action Edit the $HOME/.rhosts file for root on the client machine to add anentry for the host name of the NIM master.

Message 0042–139

Explanation The process of installing a machine prevents any attached disksfrom being used as the source for installable images. You haveallocated a resource to the target of the install operation that isserved by the target itself.

User Action Deallocate the resource, allocate another resource of this type that isserved by another machine, and try the operation again.

Message 0042–140

Explanation You have requested that a machine object be removed from the NIMenvironment and this has been done; however, NIM was unable toremove the /etc/niminfo file on the machine that has been removedfrom the NIM environment.

User Action Remove the /etc/niminfo file from the machine that was removedfrom the NIM environment.

Note: Verify that the.rhost permissions for the master have beenremoved from the client.

Message 0042–141

Explanation By specifying an attribute assignment with a NULL value, you haverequested NIM to remove the specified attr. However, in this case,the specified attr is not currently part of the specified object’sdefinition.

User Action Try the operation again, using an attribute that is part of the object’sdefinition.

Message 0042–142

Explanation All attribute values must be unique. You have specified a value in anattribute assignment that already exists.


User Action Try the operation again, using a unique value for the attribute.

Message 0042–143

Explanation Some NIM attributes can only be added to an object’s definitiononce. In this case, you have specified an attribute of this type whenone already exists for the specified object.

User Action Only one attribute of this type can be used in the object’s definition.Perform the change operation on the object if you want to replacethe current value with a new one.

Message 0042–144

Explanation Some NIM attributes require a unique sequence number so that NIMcan distinguish between multiple attributes of that type. In this case,you have specified a sequence number that is already being used.

User Action Try the operation again, using a sequence number that is notcurrently being used. To display the sequence number that are beingused, enter:

lsnim –a AttributeName ObjectName

Message 0042–145

Explanation You have specified an attribute that does not exist in the NIMenvironment.

User Action Try the operation again, using a valid NIM attribute. To display a listof valid attribute names, enter:

lsnim –p –s info_subclass

Message 0042–146

Explanation You have specified an object type that does not exist in the NIMenvironment.

User Action Try the operation again, using a valid NIM object type. On the NIMmaster, the lsnim command can be used to display the valid NIMobject types.

Message 0042–147

Explanation You have attempted to execute a NIM command on the NIM masterthat can only be executed on NIM clients.

User Action Execute the command on a NIM client.

Message 0042–148

Explanation The information contained in the specified attribute is no longer valid.

User Action Change the information in the attribute to reflect valid informationand try the operation again.


Message 0042–150

Explanation Any directory used to store NIM resources must be local to themachine that serves those resources. This is required because NIMcan only NFS export local directories. In this case, you havespecified a directory that is not local to the designated server of thedirectory. NIM has obtained this information from the file system ofthe designated server and the vfstype listed corresponds to valuesin the /usr/include/sys/vmount.h file.

User Action Either copy the desired resources onto the designated server andperform the operation again, or specify the correct server whenperforming the operation.

Message 0042–151

Explanation For NIM to use a file, it must be of a specific type. In this case, youhave specified a file whose type cannot be used by NIM. NIM hasobtained this information from the file system of the designatedserver of the file and the file type corresponds to values in the/usr/include/sys/mode.h file.

User Action Change the file type of the file and try the operation again.

Message 0042–152

Explanation When an installp operation is performed on a SPOT, the rootdirectories of all diskless and dataless clients that use that SPOTmust be synchronized with the changes made within the SPOT. Inthis case, one or more errors occurred when performing the rootsync operation on a root directory.

User Action Investigate why some of the root syncs failed and perform theoperation again. The nim.installp log for the client root is located inRootResrcParentDir / ClientName /var/adm/ras.

Message 0042–153

Explanation For NIM to use a file, it must have specific file permissions. In thiscase, you have specified a file whose permissions conflict with thoserequired by NIM. NIM has obtained this information from the filesystem of the designated server of the file, and the value of the filepermissions comes from the /usr/include/sys/mode.h file.

User Action Change the file permissions of the file and try the operation again.

Message 0042–154

Explanation For NIM to use a file, it must exist. You have specified a file that doesnot exist.

User Action Create the file and try the operation again.

Message 0042–155

Explanation For NIM to keep diskless and dataless root directories in sync withtheir corresponding SPOTs, NIM requires that the client’s rootdirectory be served from the same machine as its SPOT. In thiscase, you have requested a resource to be allocated that violatesthat requirement.


User Action Try the operation again using resources that do not violate the NIMrequirement.

Message 0042–156

Explanation You have requested an operation to be performed that involves adirectory that does not exist.

User Action Create the missing directory and try the operation again.

Message 0042–157

Explanation The operation you have requested could not be performed becausea required file could not be accessed.

User Action Create the missing file and try the operation again. For example:

• If the missing file is a boot image with a name whose format isSpotName.NetworkInterface.Platform (for example,myspot.tok.up ), recreate the boot image by performing thecheck operation on the SPOT.

• If the missing files are directories with which root or pagingresources are associated, delete the resource definition with theremove operation, create the directories, and then redefine theresource.

• If a SPOT ’s image.template file is missing, this indicates that theSPOT has been corrupted or was not constructed successfully. Torecover, you may need to remove and rebuild the SPOT with theremove and define operations.

Message 0042–158

Explanation The operation you have requested requires NIM to modify a file thatit was unable to modify successfully.

User Action Check the file permissions on the file and try the operation again.

Message 0042–159

Explanation Required software is missing which prevents the target machinefrom acting as a SPOT server.

User Action Install the missing software and retry the operation.

Message 0042–160

Explanation The operation you requested requires the construction of networkboot images and NIM was unable to do that.

User Action Fix the problem that prevented the network boot images from beingconstructed and try the operation again.

Message 0042–161

Explanation There is insufficient free disk space to complete the requestedoperation.

User Action Increase the amount of available space, as detailed in the errormessage.


Message 0042–162

Explanation To perform the requested operation, NIM requires an lpp_sourcetype resource object that has the simages attribute as part of itsdefinition. This attribute is used to designate that an lpp_sourcecontains the total set of optional packages that are required tosupport NIM install operations. In this case, you have not supplied anlpp_source that fulfills this requirement.

User Action Try the operation again using an lpp_source that has the simagesattribute in its definition.

Message 0042–163

Explanation NIM coordinates access between a client and the server of theresource. To do this, NIM must identify a network interface that canbe used by the client. This becomes a complex problem when theserver has more than one network interface. NIM uses a connectivityalgorithm to establish which network interface to use. This errormessage occurred because the connectivity algorithm detected aproblem with the client’s routing and the interface the algorithm hasselected to use. NIM does not allow the interface on the server thatthe client uses as a gateway to be used to serve resources becausethe operation requiring the resource could fail.

User Action If the server has other network interfaces that are not known to NIM,change the server machine object to add the interfaces.

Define a NIM route between the client’s primary network and one ofthe other networks to which the server connects.

Message 0042–164

Explanation Some NIM operations do not allow the source of installable imagesto be a CD–ROM. NIM is not always able to construct anenvironment that supports the use of a CD–ROM for the operationbeing performed. This is true for the operation you tried to perform.

User Action Try the operation again using a different source for installableimages.

Message 0042–165

Explanation Some attributes can only be specified together; others are mutuallyexclusive. In this case, you specified one or more attributes thatconflict.

User Action Try the operation again, omitting the attribute that was in conflict. Forexample, the ring_speed and cable_type attributes cannot be usedwith the same if attribute; the one you should use depends on thetype of network interface referenced by the corresponding ifattribute.


Message 0042–166

Explanation The if attribute specifies network interface information, whichincludes a reference to the network object that the interface connectsto. In this case, you have omitted a required attribute which isassociated with the if attribute.

User Action Try the operation again, including the required attribute. Forexample, the ring_speed attribute corresponds with the Token–Ringnetwork interface, and the cable_type attribute corresponds with theEthernet network interface.

Message 0042–167

Explanation The device which you have specified as the source for the IPL ROMemulation, does not contain a valid, bootable image of the IPL ROMemulation.

User Action If the specified device has media in it, this media either does notcontain the IPL ROM emulation, or the media has been corrupted.Remake the IPL ROM emulation, and try the operation again. If thespecified device has no media in it, make the IPL ROM emulation,put it in the device, and try the operation again.

Message 0042–168

Explanation You have specified that the originating and destination network arethe same. Machines that are on the same network do not needrouting to communicate; therefore, adding a route from a network toitself is not allowed.

User Action Specify a different originating and destination network when adding aNIM route.

Message 0042–169

Explanation You have allocated an lpp_source, but you have not specified whichfilesets are to be installed using that lpp_source.

User Action Specify the filesets to install using the filesets attribute in thecommand, or by allocating an installp_bundle that contains a list ofthe filesets to install.

Message 0042–170

Explanation You entered a platform type that is not known to NIM.

User Action The valid platform types are rs6k, rs6ksmp, and rspc. Correct theplatform type attribute and try the operation again.

Message 0042–171

Explanation Not all platform types are supported on all configuration types. Forexample, the diskless configuration type is not supported on theplatform type rs6ksmp.

User Action Use the correct platform type and try the operation again.


Message 0042–172

Explanation You have specified the incorrect name of the machine object for theNIM client machine. When the niminit command is used to rebuildthe niminfo file, the master registration process checks the CPU IDof the machine with the value stored in the NIM database for thenamed machine. If the stored value does not match the valuepassed by niminit, this message is issued.

User Action Use the correct name and try the command again.

Message 0042–173

Explanation You specified that the installp command should expand file systems(using the –X flag) while specifying that NIM should not auto expand(using the auto_expand attribute). This is not an allowablecombination for the command invoked.

User Action Use either the –X flag or the auto_expand attribute, but not both.

Message 0042–174

Explanation You specified an invalid value for an attribute whose only validvalues are yes and no.

User Action Retry the operation with a value of yes or no for the attributeindicated.

Message 0042–175

Explanation An unexpected result has been returned from a command that NIMtried to execute.

User Action Fix the problem that caused the executed command to fail and trythe operation again.

If the command failed due to a shortage of space, its error messagesindicating this should be displayed. Expand the indicated file system,(for most NIM operations use the auto_expand attribute) and retrythe operation. If a space failure occurred during SPOT creation, andif the bosboot command failed to make boot images as a result,increase the free space and run the check operation.

If the command listed by NIM in this message is the installpcommand, check the nim.installp log for failure and recoveryinformation. (For standalone client operations, this is located in the/var/adm/ras directory of the client. For SPOT cust and maintoperations, this is located in SPOTParentDir /SPOTName/usr/lpp/bos/inst_root/var/adm/ras on the SPOT. For diskless anddataless clients, this is located in RootResrcParentDir / ClientName/var/adm/ras.

Message 0042–176

Explanation The resource cannot serve as a support image (simages)lpp_source. When an lpp_source serves as a support imageresource, it contains a minimal set of software packages forfacilitating installation and the use of the base operating system.


User Action No action is necessary if this resource does not need to serve as asupport images lpp_source. If the resource needs to be a supportimages lpp_source, add the missing software to the lpp_source. Ifthe lpp_source is a directory, you can do this by copying the missingpackages to the location of the lpp_source and running the checkoperation.

Message 0042–177

Explanation The operation you requested could not be completed due toinsufficient free space in one or more file systems.

User Action Make more space available if possible, by extending the file systemdisplayed. For most NIM operations, the auto_expand attribute isavailable to automatically expand file systems.

Message 0042–178

Explanation The if attribute is made up of four fields. The fourth field is optional inmost cases. In this case. the network object that you specified (infield one) has more than one type of network. In this case, NIMrequires that the fourth field has a value that specifies the logicaldevice name of the network adapter.

User Action Add the appropriate value to the if attribute, and try the operationagain.

Message 0042–179

Explanation You are attempting to remove an if or other_net_type attribute onwhich one or more NIM clients have a dependency.

User Action If this is not a mistake, remove the NIM clients that are dependent onthe network, or remove the if attribute from the NIM client objectdefinition.

Message 0042–180

Explanation The address of the machine that is being defined is not connected tothe network that is represented by the specified network object.

User Action Define a network object that represents the physical network towhich the machine is connected. Use this network object whendefining the machine.

Message 0042–181

Explanation The fix_query_flags attribute has an illegal value. Use lsnim –Pafix_query_flags for a list of legal values.

User Action Determine the correct flags and retry the operation.

Message 0042–182

Explanation A resource of one type cannot be allocated for the current operationat the same time as a resource of another type. Allocate one or theother, but not both.

User Action The resources specified are mutually exclusive. Determine whichone is needed for the operation, and omit the other.


Message 0042–183

Explanation An attribute cannot be specified for the current operation when atype of resource is allocated. Use one or the other, but not both.

User Action The attribute and the resource specified are mutually exclusive.Determine which one is needed for the operation, and omit the other.

Message 0042–184

Explanation The network address (net_addr) or subnet mask (snm) cannot bechanged for the network, because NIM clients are currently definedas being connected to that network. Remove the client definitionsbefore changing the network.

User Action The nimdef command can be used to quickly redefine NIM clientsafter they have been removed to update the network definition.

Message 0042–185

Explanation Failed to link or copy files. Check permissions and file system space.

User Action Verify that space and inodes are available for the files and linksspecified in the error message.

Message 0042–186

Explanation Failed to copy setup programs. Either start NFS on the client or free1000 512–byte blocks in the file system.

User Action Programs required to set up the operation could not be copied to theclient system. Either start NFS on the client, or increase space in thefile system specified in the error message.

Message 0042–187

Explanation Failed to expand file system.

User Action Attempt to manually expand the file system specified in the errormessage, then retry the operation.

Message 0042–188

Explanation Failed to NFS mount.

User Action Verify that NFS is running on both the resource server and the clientspecified in the error message. Retry the operation when the NFSproblems have been resolved.

Message 0042–189

Explanation Failed saving existing boot image. Check space in the file system.

User Action Increase space in the file system specified by the error message,and retry the operation.

Message 0042–190

Explanation The key is not in the NORMAL position. Unattended installationcannot complete unless the key is in the NORMAL position.

User Action Turn the key on the client machine to the NORMAL position and retrythe operation.


Message 0042–191

Explanation Unable to write the IPLROM emulation.

User Action The mkboot command failed to write the IPLROM emulation on theclient. Boot the client manually over the network to begin the BOSinstallation.

Message 0042–192

Explanation Unable to find boot logical volume.

User Action Verify that a boot logical volume is defined for the machine. NIMattempts to use the lslv –l hd5 command to determine the bootlogical volume.

Message 0042–193

Explanation The client does not have an.rhosts entry for the master, or the clienthost ID is not resolvable.

User Action Verify that the client host name is resolvable by the master. Thenverify that an entry exists for the master in the $HOME/.rhosts filefor root on the client machine.

Message 0042–194

Explanation The client does not allow NIM push operations. Remove/etc/nimstop on %s if push operation is necessary.

User Action On the client machine, run the nimclient –p command to re–enablemaster push permissions.

Message 0042–195

Explanation Unable to order boot device list.

User Action An error was returned by the bootlist command on the client. If anetwork boot must be performed for a bos_inst, diag, ormaint_boot operation, manually set the boot list and reboot theclient, or follow the normal procedure to boot the client over thenetwork.

Message 0042–196

Explanation The set_bootlist attribute is only valid when used in combinationwith the no_client_boot or boot_client attributes.

User Action Only specify the set_bootlist attribute to the nim command whenchanging the default behavior with the no_client_boot orboot_client attributes.

Message 0042–197

Explanation If the target machine has more than one interface for a givennetwork type, the network adapter’s logical device name must bespecified in the if1 attribute of the target machine’s NIM definitionwhen using the force_push attribute.


User Action Modify the client’s if1 attribute using the NIM change operation.Change the if1 attribute to include one of the client’s networkadapter logical device names listed in the error message.

Message 0042–198

Explanation When converting a machine’s /usr file system to a SPOT, the bosimage on the media (lpp_source) being used to create the SPOTmust match the bos image that was used to install the machine.

User Action When defining the /usr SPOT, use the same installation media thatwas used to install the machine originally. For example, if a machinewas originally installed with AIX 4.3.2 and then updates were appliedto bring the machine to AIX 4.3.3, the installation media that shouldbe used when defining the /usr SPOT on the machine would stillneed to be the AIX 4.3.2 product media.

Message 0042–199

Explanation The no_client_boot and boot_client attributes may not be specifiedtogether.

User Action To avoid the possibility of giving conflicting instructions to the NIMcommand, do not supply both the no_client_boot and boot_clientattributes in the same NIM operation.

Message 0042–204

Explanation The mk_image and source attributes are only valid when specifiedtogether.

User Action When creating a mksysb resource from a running client machine,use the mk_image=yes attribute to indicate that a mksysb shouldbe created, and use the source= ClientName attribute to specify thename of the client that is to be backed up.

Message 0042–205

Explanation The bos.sysmgt.sysbr fileset must be installed on the client toperform the system backup. You may install this fileset with the NIMcust operation.

User Action Install the bos.sysmgt.sysbr fileset on the client machine beforeretrying the operation.

Message 0042–206

Explanation There is already a resource allocated.

User Action Only one resource of the type specified can be allocated to theclient. Deallocate the first resource before attempting to allocate theother.

Message 0042–207

Explanation Unable to allocate a resource to a client.

User Action Look for other NIM error messages that may accompany this errorand which may provide more information about the problem. Verifythat the resource specified is NFS–exportable to the client.


Message 0042–208

Explanation Unable to lock a client. This could mean that the client is alreadylocked, or the name given does not refer to a valid NIM client.

User Action If another NIM operation is being performed on the same client, waitfor the process to complete before retrying the operation. If no otherNIM operations are being performed, stop and restart the nimesisdaemon to remove locks.

Message 0042–209

Explanation The mksysb_flags attribute contains an illegal value. Use the lsnim–Pa mksysb_flags command to get a list of legal values.

User Action Specify the correct values for the mksysb_flags attribute, and retrythe operation.

Message 0042–210

Explanation The maximum space required for the backup is greater than theamount of free space in the target file system. To ignore spacerequirements, use the –F flag when defining the mksysb resource.

User Action Either increase the space of the target file system where themksysb is to be created, or use the –F flag as specified in the errormessage.

Message 0042–211

Explanation The member already exists in group.

User Action No additional action is required, since the member is already addedto the group.

Message 0042–212

Explanation The member was not added to the group, because it is not a validNIM name.

User Action The name of a member to add to a group was invalid. Verify that themember was specified correctly.

Message 0042–213

Explanation The group was not created, because it did not contain any validmembers.

User Action A group must contain at least one member. Redefine the group withvalid members to add it to the NIM environment.

Message 0042–214

Explanation Unable to add a member to a group.

User Action Look for other NIM error messages that may accompany this errorand which may provide more information about the problem.

Message 0042–215

Explanation An invalid log type for the showlog operation was specified.

User Action Specify one of the valid log types listed in the error message.


Message 0042–216

Explanation An invalid log type for the showlog operation was specified for aSPOT.


Message 0042–217

Explanation An invalid log type for the showlog operation was specified for adiskless or dataless machine.


Message 0042–218

Explanation The log file is either empty or does not exist.

User Action No information is available in the log file for the machine or SPOTspecified.

Message 0042–219

Explanation The object is incompatible with the group.

User Action The object cannot be added to the group, because its type is notallowed in the group. Machine groups can only contain one type ofNIM client, and that type is determined by the first member added.Resource groups can only contain members whose types areresources.

Message 0042–220

Explanation You cannot have more than one resource of the specified type in aresource group.

User Action You must remove the current member with the specified type fromthe resource group before the new member with the same type canbe added.

Message 0042–221

Explanation The group GroupName is being removed, because its singleremaining member was removed during this operation.

User Action A group cannot be empty. Redefine the group with at least onemember if it should remain in the NIM environment.

Message 0042–222

Explanation An unknown error occurred allocating resources to the machine.

User Action Look for other NIM error messages that may accompany this errorand which may provide more information about the problem. Verifythat the resource specified is NFS–exportable to the client.

Message 0042–223

Explanation Invalid input file. The file either cannot be read, is empty, or containsno valid entries.


User Action Verify that the file specified in the error message is the correct file forthe operation.

Message 0042–224

Explanation The limit on the length of a line in an NFS exports file was exceeded.The export operation cannot be performed.

User Action Manually edit the /etc/exports and /etc/xtab files to remove anyobsolete entries. The number of hosts to which NIM can NFS–exporta resource can also be increased by setting therestrict_nfs_exports attribute to no on the master by running thenim –o change –a restrict_nfs_exports=no master command.

Message 0042–225

Explanation An error occurred while updating the exports file. Check forcorruption in the file.

User Action Manually edit the /etc/exports and /etc/xtab files to fix any filecorruption problems. Attempt to determine why NIM was unable tosuccessfully update the files. Check file and directory permissions,and verify that file systems are not full.

Message 0042–226

Explanation A timeout occurred while attempting to initiate the operation on theclient. The operation may not have started successfully.

User Action If the operation that was performed was bos_inst, the client onlyneeds to be rebooted manually over the network to begin theinstallation. For all other operations, the problem is most likely due tonetwork communication problems between the master and the client.Verify that the client is reachable by the master and that rshpermission is still granted by the client to the master.

Message 0042–227

Explanation The state of the machine indicates that it may not be ready forcertain NIM operations.

User Action Check to see if any NIM operations are still being performed on themachine. If not, reset the state of the machine with the nim –Foreset MachineName command. This returns the machine to theready state so NIM operations can be performed on it. The resetoperation does not deallocate resources, so deallocate resources ifnecessary using the nim deallocate operation.

Message 0042–228

Explanation Invalid release level.


User Action The release level of the resource is incomplete, or incorrectlyspecified. The level of the resource can be obtained by running thelsnim –l ResourceName command and viewing the version,release, and mod attributes. To correct the problem, either recreatethe resource, or modify the NIM database to contain the correct levelusing the command on the NIM master:/usr/lpp/bos.sysmgt/nim/methods/m_chattr –a Attribute = ValueResourceName, where Attribute is version, release, or mod; Valueis the correct value; and ResourceName is the name of the resourcewith the incorrect level specification.

Message 0042–229

Explanation When installing a system using a mksysb as the source for theinstallation, the level of the SPOT used for the installation mustmatch the level of the mksysb image being installed. The releaselevels of the SPOT and the mksysb do not match.

User Action Create a SPOT that matches the level of the mksysb beinginstalled, and use that SPOT when performing a mksysb BOSinstallation. The level of mksysb and SPOT resources can beobtained by running the lsnim –l ResourceName command andviewing the version, release, and mod attributes.

Message 0042–230

Explanation When installing a system using a mksysb as the source for theinstallation, the level of the SPOT used for the installation shouldmatch the level of the mksysb image being installed. If thisconvention is not followed, the installation may not completesuccessfully.

User Action Create a SPOT that matches the level of the mksysb beinginstalled, and use that SPOT when performing a mksysb BOSinstallation. The level of mksysb and SPOT resources can beobtained by running the lsnim –l ResourceName command andviewing the version, release, and mod attributes.

Message 0042–231

Explanation A temporary list of software that should be installed is created andused for this operation. The list could not be created.

User Action Check previous error messages to understand why the erroroccurred. Correct the problem and try the operation again.

Message 0042–232

Explanation A temporary installp_bundle resource is created and used for thisoperation. The temporary resource could not be created.

User Action Check previous error messages to understand why the creation ofthe resource failed. Correct the problem and try the operation again.

Message 0042–233

Explanation The operation cannot be performed because the NIM Master isalready initialized.

User Action Unconfigure the NIM Master and try the operation again.


Message 0042–234

Explanation You cannot restore a NIM database backup onto a machine that hasan earlier level of the NIM master fileset installed. For example, aNIM database backup of a system with level 4.2.0.0 of the NIMmaster cannot be restored to a system that has a level of the NIMmaster lower than 4.2.0.0.

User Action Install a level of the NIM master fileset that is at the same level or alater level than that from which the backup was created. Thenattempt to restore the NIM database backup.

Message 0042–235

Explanation An image source was not specified for creating the SPOT.

User Action Specify a device containing installation images or specify anlpp_source with the simages attribute for creating the SPOT.

Message 0042–236

Explanation A name for the lpp_source and/or a directory to contain thelpp_source was not specified for the lpp_source that will becreated.

User Action Specify a name and a directory for the lpp_source and try theoperation again.

Message 0042–237

Explanation A name for the SPOT and/or a directory to contain the SPOT wasnot specified for the SPOT that will be created.

User Action Specify a name and a directory for the SPOT and try the operationagain.

Message 0042–238

Explanation A parent directory was not specified for the diskless and datalessmachine resources that will be created.

User Action Specify a directory for the diskless/dataless machine resources andtry the operation again.

Message 0042–239

Explanation A name for the resource and/or directory to contain the resource wasnot specified for the resource that will be created.

User Action Specify a name and a directory for the resource and try the operationagain.

Message 0042–240

Explanation A parent directory was not specified for the diskless and datalessmachine resources that will be created.

User Action Specify a directory for the diskless/dataless machine resources andtry the operation again.


Message 0042–241

Explanation The size and/or volume group was not specified for the creation of anew file system to contain a NIM resource.

User Action Specify both the size and volume group for the file system and trythe operation again.

Message 0042–242

Explanation The size and/or volume group was not specified for the creation of anew file system to contain diskless and dataless machine resources.

User Action Specify both the size and volume group for the file system and trythe operation again.

Message 0042–243

Explanation An attempt was made to create the same file system twice: once foran lpp_source and once for a SPOT.

User Action Specify a different directory for either the lpp_source or the SPOT.This will cause different file systems to be created for the resources.If a new file system really should be created to contain bothresources, then only specify that the file system should be createdfor one of the resources, but specify the same directory for bothresources.

Message 0042–244

Explanation An attempt was made to create the same file system twice: once foran lpp_source and once for diskless/dataless machine resources.

User Action Specify a different directory for either the lpp_source or thediskless/dataless resources. This will cause different file systems tobe created for the resources. If a new file system really should becreated to contain both sets of resources, then only specify that thefile system should be created for one of the resources, but specifythe same directory for both resources.

Message 0042–245

Explanation An attempt was made to create the same file system twice: once fora SPOT and once for diskless/dataless machine resources.

User Action Specify a different directory for either the SPOT or thediskless/dataless resources. This will cause different file systems tobe created for the resources. If a new file system really should becreated to contain both sets of resources, then only specify that thefile system should be created for one of the resources, but specifythe same directory for both resources.

Message 0042–246

Explanation Not enough space on the volume group to create the specified filesystem.

User Action Specify a different volume group for the file system to be created andtry the operation again.


Message 0042–247

Explanation Creation of the file system failed.

User Action Check the previous output for error messages to understand whatcaused the file system creation to fail. Correct the error and try theoperation again.

Message 0042–248

Explanation An error occurred during file system creation.

User Action Check the previous output for error messages to understand whatcaused the file system creation to fail. Correct the error and try theoperation again.

Message 0042–249

Explanation NIM master initialization failed.

User Action Check the previous output for error messages to understand whatcaused the configuration of the NIM master to fail. Correct the errorand attempt to reinitialize the master. The most frequent cause ofthis failure is that the master is already initialized. The master can beunconfigured with the nim –o unconfig master command andreinitialized. However, this should be done with extreme caution,since unconfiguring the master will remove all definitions from theNIM database.

Message 0042–250

Explanation Unable to continue with configuration.

User Action Check the previous output for error messages to understand whatcaused the configuration to fail. Correct the error and attempt toconfigure the system again from the point of failure.

Message 0042–251

Explanation A route cannot be added to the network, because a required defaultroute is missing. Add a default route to the network, and try thisoperation again.

User Action Add a default route to the network specified in the error message,and retry the operation.

Message 0042–252

Explanation Unable to locate a matching network.

User Action The find_net keyword was used in the if attribute of the machine.However, no matching network was found. Either define the networkprior to defining the machine interface, or use the net_definitionattribute in conjunction with the find_net keyword to define thenetwork while the interface is being defined.

Message 0042–253

Explanation You cannot use the net_definition attribute when the find_netkeyword is not specified as the first field of the if attribute.


User Action The net_definition attribute is invalid when using a known networkin the if attribute. Specify the find_net keyword in the if attribute, oromit the net_definition attribute, and retry the operation.

Message 0042–254

Explanation Invalid format for the specified value of net_definition. The value ofthe attribute should be as follows:

NetTypeNetwork type (for example, tok, ent, fddi, etc.).

snmNameDotted decimal subnet mask for the network.

Client_gwNameOptional default gateway IP address or host name used by themachine being defined to communicate with the master.

Master_gwNameOptional default gateway IP address or host name used by themaster to communicate with clients on other subnets.

NetNameOptional name given to the NIM definition created for the network.(Otherwise, a unique default name is used.)

If you want to specify NetName and if Client_gwName orMaster_gwName are not applicable, specify 0 in their place. IfClient_gwName is 0, Master_gwName cannot be nonzero.

User Action Correct the syntax error, and retry the operation.

Message 0042–255

Explanation The master already has a default route, and the gateway youspecified as being the default for the master is different from thatwhich is already defined. Use the change operation if you want tomodify the master’s default gateway.

User Action To change the default gateway for a network, use the followingcommand:

nim –o change –a routing X =”default GtName ”

NetName

where X is the sequence number for the routing attribute; GtNameis the default gateway to use; and NetName is the name of themaster’s network.

Message 0042–256

Explanation A default route already exists for the network. You can modify thedefault gateway, but you cannot define more than one default route.

User Action To change the default gateway for a network, use the followingcommand:

nim –o change –a routing X =”default GtName ”

NetName

where X is the sequence number for the routing attribute; GtNameis the default gateway to use; and NetName is the name of thenetwork to modify.


Message 0042–257

Explanation You cannot specify the net_definition attribute without specifyingthe if attribute when changing a machine definition.

User Action The net_definition must reference a machine interface, so specifyan if attribute when using the net_definition attribute.

Message 0042–258

Explanation You cannot specify the net_definition attribute when creating ormodifying more than one if attribute in the same change operation.Use two separate operations.

User Action To avoid ambiguity, manipulate only one machine interface (ifattribute) at a time when using the net_definition attribute.

Message 0042–259

Explanation The value of default_res specified on the master’s databasedefinition is not a valid NIM resource group.

User Action Specify a valid NIM resource group as the default resource. Obtain alist of resource groups by running the lsnim –t res_groupcommand.

Message 0042–260

Explanation The default attribute is only applicable when manipulating aresource group.

User Action Setting the default=yes/no attribute on a resource group makes itthe default set of resources to use in NIM operations. The defaultattribute is invalid when used as an attribute in other NIM operations.

Message 0042–261

Explanation Illegal use of the async attribute. This attribute can only be specifiedfor the lppchk operation when the target is a standalone machine ora group of standalone machines.

User Action Omit the async attribute when performing the lppchk operation,unless the target is a standalone machine or a group of standalonemachines.

Message 0042–262

Explanation The file name of the client definition file is missing for this operation.

User Action Specify the client definition file that should be used to add machinesto the NIM environment. For more information, see NetworkInstallation Management Commands Reference on page 23-31.

Message 0042–263

Explanation The netboot_kernel attribute can only be assigned a value of up ormp.

User Action Correct the value specified for the netboot_kernel attribute.


Message 0042–264

Explanation The image source that was used to define the lpp_source is missingone or more requested packages.

User Action Installation images were not copied into the lpp_source directory.The source for installation images may not contain all of the filesetsspecified to populate the lpp_source. Copy the missing installationimages to the lpp_source directory, and then perform the NIMcheck operation on the lpp_source.

Message 0042–265

Explanation The image source that was used to define the lpp_source is missingone or more items from the list of default packages.

User Action Installation images were not copied into the lpp_source directory.The source for installation images may not contain all of the defaultfilesets used to populate the lpp_source. Copy the missinginstallation images to the lpp_source directory, and then perform theNIM check operation on the lpp_source.

Message 0042–266

Explanation Requested packages are missing from the defined lpp_source.

User Action Installation images were not copied into the lpp_source directory.The fileset names may have been specified incorrectly, or the sourcefor installation images may not contain all of the specified filesets.Copy the missing installation images to the lpp_source directory,and then perform the NIM check operation on the lpp_source.

Message 0042–267

Explanation The defined lpp_source does not have the simages attribute,because one or more packages are missing.

User Action Copy the missing installation images to the lpp_source directory,and perform the NIM check operation on the lpp_source to add thesimages attribute.

Message 0042–268

Explanation The operation cannot be performed, because all members of thetarget group specified are currently excluded from operations on thegroup. You must unmark (or include) excluded group membersbefore proceeding.

User Action Perform the NIM select operation on the group to include membersin further operations.

Message 0042–269

Explanation Only one type of verification can be performed at a time whenverifying installed filesets on a NIM client.

User Action Disable or deselect all but one verification option and try theoperation again.


Message 0042–270

Explanation The operation is only supported on SPOTs and NIM clients installedwith a version and release level of AIX 4.2 or greater.

User Action The NIM client fileset on the target is at an earlier level and does notsupport the attempted operation. The client software on the targetmust be upgraded before the operation can be performed.

Message 0042–271

Explanation A resource matching the type is already allocated. You cannotallocate more than one resource of this type to a machine.

User Action Deallocate the first resource before attempting to allocate thesecond. It may be necessary to reset the machine before theresource can be deallocated.

Message 0042–272

Explanation A value specified is not a valid value for default_re because it is nota valid NIM resource group.

User Action Specify a different resource group for the default_res attribute, orcorrect the resource group in question.

Message 0042–273

Explanation A value specified cannot be used as the location for the mksysbimage because it is a directory. You must specify the filename wherethe mksysb image currently resides or will reside after creation.

User Action Specify a file name instead of a directory for the location of themksysb resource.

Message 0042–274

Explanation The –e flag in the mksysb_flags attribute and the exclude_filesattribute cannot be specified together. Specify the –e flag with themksysb_flags attribute to exclude the files in /etc/exclude.rootvgfrom the backup, or specify an exclude_files attribute.

User Action Do not specify both the –e mksysb flag and an exclude_filesresource when performing this operation.

Message 0042–275

Explanation Unable to obtain possession of a lock file. If no NIM operations arecurrently in progress, remove the file and repeat the operation.

User Action Use the ps –ef | grep nim command to list the running NIMprocesses on the system. If any NIM processes other than thenimesis daemon are running, wait for them to finish and thenremove the file specified by the error message.

Message 0042–276

Explanation A fileset must be installed before this operation can be performed.


User Action Install the fileset listed in the error message before retrying theoperation. Generally, the fileset needs to be installed on the clientsystem. However, depending on the operation being performed, theNIM master may also need to have the fileset installed before theoperation will succeed.

Message 0042–277

Explanation Diskless and dataless machines cannot be defined with a primarynetwork install interface residing on a generic NIM network. It ispresumed that a network adapter defined on a generic NIM networkdoes not support network boot.

User Action To define the systems as diskless or dataless clients, they must firstbe connected to a NIM network that is known to support networkboot, such as ethernet, token–ring, or FDDI.

Message 0042–278

Explanation The interface specified does not correspond to a network adapterthat is known to support network boot. As a result, the NIM masterhas been defined on a generic NIM network. Networkboot–dependent operations, such as base operating systeminstallation, will not be possible on any NIM client whose primarynetwork install interface is defined on the same network as the NIMmaster.

User Action Operations that rely on network boot capability cannot be performedon clients on generic NIM networks. Such operations must beperformed using local media on the system.

Message 0042–279

Explanation The interface specified maps to a subnet which has been defined asa generic NIM network. It will not be possible to perform networkboot–dependent operations, such as base operating systeminstallation, on the machine definition created by this operation.

User Action Operations that rely on network boot capability cannot be performedon clients on generic NIM networks. Such operations must beperformed using local media on the system.

Message 0042–280

Explanation Specify a complete date and time for the scheduled operation in theform: YYMMDDhhmm.

User Action Use the format described in the error message to correctly schedulea date and time for the operation.

Message 0042–281

Explanation The /usr file system on the specified server cannot be converted to aNIM SPOT. Either the RM_INST_ROOTS variable was set to yes ina bosinst.data file during initial installation of the machine or inurid–r was subsequently invoked. The only way to create a SPOT onthis machine is to specify the location to be something other than/usr or reinstall the machine and then create a SPOT in /usr.


User Action The system is unable to support the creation of a /usr SPOT. Anon–/usr SPOT may be created on the system by specifying adifferent value for the location attribute.

Message 0042–282

Explanation The BOS installation has been enabled but could not be initiated,because the following file was not found on the target. To start theinstallation, do one of the following:

1. Initiate a network boot operation from the targ

2. Correct the state of the target with NIM’s reset operation andinvoke the bos_inst operation again using one of the following:

a. The Force Push option (–a force_push=yes)

b. After installing and configuring the bos.sysmgt.nim.client fileseton the target.

User Action The NIM client fileset is not properly installed and configured on thetarget system. Follow the directions specified in the error message tocorrect the problem.

Message 0042–283

Explanation The existence of a file on the server indicates that a NIM SPOT maystill be mounted in a subdirectory which will be removed by thisoperation. Before attempting the operation again, unmount theSPOT ’s directory along with any other directories that may bemounted beneath the directory being removed.

Failure to do so will result in loss of data on the SPOT server.

User Action A SPOT operation failed, and NIM was unable to unmount all thedirectories mounted into the SPOT. Manually unmount the directoriesspecified in the error message before retrying the operation. Themount command can be used to list the directories mounted on thesystem, and the unmount command can be used to unmountdirectories. Use the –f option with the unmount command ifnecessary to force the unmount.


30-1Network Installation Management Troubleshooting

Chapter 30. NIM Troubleshooting

This chapter suggests solutions for network boot problems and describes procedures forproducing debug output for NIM BOS installations. Refer to NIM Error and WarningMessages on page 29-1 for information about error messages.

Debugging a Network Boot Problem

If a client machine is unable to network boot from its boot server, there may be a problem inone or more of the network boot stages. The network boot stages are listed in the followingtasks:

• Verifying Network Communication Between the Client and Server

• Obtaining the Boot Image from the Server

• Running the Boot Image on the Client.

Verifying Network Communication Between the Client and ServerBefore initiating the network boot on the client, do the following to verify networkcommunication between the client and the server:

1. Perform a ping test from the client bootp menus.

2. If the ping test fails, verify that the client, server, and gateway addresses are specifiedcorrectly.

3. If the addresses are correct, try to ping the server from a different machine in the client’ssubnet.

If the server can be pinged from another machine, the network adapter on the boot clientmay be faulty.

4. If the server cannot be pinged from another machine in the client’s subnet, there may berouting problems between the client and the server, or network communications on theserver may be faulty. For information on network–debugging procedures, refer to TCP/IPProblem Determination in the AIX 5L Version 5.2 System Management Guide:Communications and Networks.

Obtaining the Boot Image from the Server1. If the ping test is successful, perform a network boot of the client. When a network boot

is initiated on a client, a bootp request packet is sent from the client to the server. Theserver then replies with a packet to the client. The client machine displays the number ofpackets sent and received for the bootp request. If a packet is sent from the client, butnone is received, another packet will be sent.

If bootp packets continue to be sent but not received, the boot server may not beresponding to the request.


2. From the bootp server, view the /etc/bootptab file on the server. It should contain anentry for the client machine with the following information:

hostname_of_client

bf= boot_file

ip= client_ip_address

ht= network_type

sa= boot_server_address

sm= client_subnet_mask

ha= network_adapter_hardware_address (required only if bootp

requests are sent by broadcasting)

If an entry does not exist, either the NIM command used to set up the current operationfailed, or the machine was reset before the boot operation could occur. Rerun the NIMbos_inst, diag, or maint_boot operation to prepare the server for the client bootrequest.

If the entry exists in /etc/bootptab, verify that the specified data is correct. If a fieldcontains incorrect data, the information that was used to define the machine or networkin the NIM database was probably incorrect. Correct this problem by resetting the clientmachine, correcting the invalid data in the client or network definition, retrying the NIMoperation, and rebooting the client.

3. If the /etc/bootptab file is correct, verify that the inetd daemon is running. If it is notrunning, start it and retry the network boot from the client. If the inetd daemon is running,it should automatically start the bootpd daemon when the bootp request is received atthe server.

4. If the bootpd daemon is not started, verify that the bootps entry in the /etc/inetd.conffile is not commented out. If it is commented out, uncomment it and restart inetd with therefresh –s inetd command. Retry the network boot from the client.

5. If a bootp reply is still not received at the client, manually start the bootpd daemon indebug mode:

a. Comment out the bootps entry from the /etc/inetd.conf file on the server.

b. Stop all running bootpd processes.

c. Restart inetd using the refresh –s inetd command.

d. Start bootpd from the command line, using the /usr/sbin/bootpd –s –d –d –dcommand.

6. Retry the network boot from the client. If no output is displayed from the running bootpdcommand, the client bootp request is not reaching the server. Verify that the addressesspecified in the bootp menus are correct. If they are correct, perform network debuggingprocedures to determine why the packet is not reaching the server.

If the server receives the client bootp request, the running bootpd command displaysoutput matching the client data in the /etc/bootptab file. Verify that the specifiedaddresses are correct. This information is sent back to the client in the bootp reply.

7. If the client is still not receiving the bootp reply, perform network–debugging proceduresto determine why the reply packet is not reaching the client.

After the client receives the bootp reply, it will tftp the boot image from the server.

The number of tftp packets transferred to the client will be displayed at the clientmachine.

The boot image has been successfully retrieved at the client machine when the LEDshows 299 on rs6k –platform machines or when the bottom third of the screen turnsgray on other platform machines.

8. If the tftp of the boot image does not complete successfully, the client may be trying toget the wrong boot image. Verify that the client definition in the NIM database shows thecorrect platform and kernel type. If the data is incorrect, correct it, reset the clientmachine, rerun the NIM operation, and reboot the client over the network.


9. Verify that the /tftpboot directory on the boot server contains a link with the client nameto the correct boot image. If the link does not exist, reset the client machine, rerun theNIM operation, and reboot the client over the network.

10.If the link with the client name is pointing to the correct boot image and the tftp of theboot image does not complete successfully, the boot image may be corrupted.Re–create the boot image by performing a NIM check operation with the force flag onthe SPOT. If the client is not an rs6k –platform machine, also make sure the client hasthe latest version of the firmware installed.

Running the Boot Image on the Client

After the client machine has successfully received the boot image from the server, the mostcommon errors encountered are hangs with the LED showing 608, 611, or 613. Somemachines may not have LED displays. Debugging such problems on these machines willrequire using debug–enabled boot images. For information on building debug boot images,see Producing Debug Output from the BOS Installation Program on page 30-5.

608

Explanation tftp retrieve of client info file failure.

Action If a 608 hang is encountered, verify that the ClientName.info fileexists in the /tftpboot directory. If it does not exist, retry the NIMoperation to create it. If it does exist, verify that tftp access to the/tftpboot directory is not restricted in the /etc/tftpaccess.ctl file. It isalso possible that the network adapter was not configured properly inthe boot environment. Use debug–enabled network boot images tolook for errors in the boot environment. If the client is not an rs6k–platform machine, make sure that it has the latest version offirmware installed.

611

Explanation Remote mount of NFS file system failure.

Action 611 hangs occur when the client machine is unable to mount aresource from a server. Ensure that NFS is running on the resourceserver. Verify that the resources specified for the operation areexported properly by checking the /etc/exports and /etc/xtab fileson the server. Also, confirm that the resources have permissions setcorrectly for reading. Debug–enabled network boot images can alsobe used to determine exactly which mount command is failing onthe client.

613

Explanation Failure setting up route tables.

Action 613 hangs usually occur because a route is incorrectly defined for anetwork in the NIM database. Verify that the correct gateways arespecified between networks, and all gateways are functional. Usedebug–enabled network boot images to determine which routescould not be defined.


Producing Debug Output for NIM BOS Installations

Due to problems in the network or in the NIM configuration, clients may fail to boot or installproperly. When this happens, it may be necessary to produce debug information in order todetermine the cause of the problem. If a client machine fails to configure properly from thenetwork boot image, debug output from the boot image can be obtained by building thedebug–enabled image and attaching a tty to the client system. This will display thecommands and output that are run while the client is configured before further processing isdone by AIX.

If the system has been booted from the network boot image, but failures are still occurringduring a BOS installation, it may be necessary to collect debug information from the BOSinstallation program. The commands and output from the BOS installation program willautomatically be displayed on the tty if the boot image was built debug–enabled. If the bootimage was not built for debugging, output can be obtained by either setting a value in abosinst.data file or by entering special codes at the installation menus.

When problems arise during a NIM BOS installation, you will most likely get system hangs.Viewing the debug output can be useful, because you will be able to see the commands thatfailed. The problem may be a misconfiguration of the network adapter or an inability toperform an operation from the client to the server. By examining the debug output, you candetermine what failed and make corrections to avoid the error in the future.

You will see the showled command running in the debug output. This command displaysstatus values on the LEDs on the front of the machine. Frequently, known problems andsolutions are referenced by the LED value that is displayed when a problem occurs. Somemachines do not have LEDs for displaying such information. Therefore, when debuggingproblems on such machines, give special attention to observing the values that theshowled commands are displaying.

Obtaining debug information from a network installation can save you time in determiningthe root cause of a problem. Usually, the problem will be an incorrect definition in the NIMenvironment that can be found without the debug information. However, with the debuginformation, you can significantly reduce the scope of the investigation.

Producing Debug Output from a Network Boot ImageTo create debug versions of the network boot images, do the following:

1. Use the Web-based System Manager or SMIT interfaces or run the following command:

nim –Fo check –a debug=yes SPOTName

where SPOTName is the name of your SPOT.

2. Obtain the address for entering the debugger by doing the following:

From Web–based System Manager:

a. From the NIM Resources container, double–click the SPOT resource to open theproperties notebook.

b. Click the Boot Image Information tab in the properties notebook to obtain the address.

Alternatively, you can use the following command to get the address:

lsnim –a enter_dbg SPOTName


where SPOTName is the name of your SPOT. The displayed output will be similar to thefollowing:

Write down the enter_dbg address for the client you are going to boot. For example, ifyour client is an chrp –uniprocessor machine, you would write down the address160b7c.

3. Attach a tty device to your client system (port 1).

4. Set up and perform the NIM operation that will require the client to boot over thenetwork. Boot the client over the network.

5. After the client gets the boot image from the SPOT server, the debug screen will appearon the tty. At the > prompt, enter:

st Enter_dbg_Value 2

where Enter_dbg_Value is the number you wrote down in step 2 asyour machine type’s enter_dbg value. Specifying a 2 at the address ofthe enter_dbg value prints the output to your tty.

6. Type g (for go ) and press Enter to start the boot process.

7. Use Ctrl–s to temporarily stop the process as you watch the output on the tty. Use Ctrl–qto resume the process.

8. To rebuild your boot images in non–debug mode, use the following command:

nim – Fo check SPOTName

where SPOTName is the name of your SPOT.

If the boot image is left in debug mode, every time a client is booted from these bootimages, the machine will stop and wait for a command at the debugger ”>” prompt. If youattempt to use these debug–enabled boot images and there is not a tty attached to theclient, the machine will appear to be hanging for no reason.

Producing Debug Output from the BOS Installation Program

There are two ways to obtain debug output from the BOS installation program. Method Ainvolves entering a special value at one of the installation menus and Method B uses abosinst_data resource to tell the installation program to display debug output. Bothmethods are described as follows:

Method A: To Produce Debug Output Without Using a bosinst_data Resource1. To enable debugging for the BOS installation program, start by performing all the

processing you would normally do to install a client.

Because you are not using a bosinst_data resource, you will be prompted to supplyinformation about the installation to the BOS installation program.

2. Select your console.

3. Select your language.

4. The Welcome to Base Operating System Installation and Maintenance menu isdisplayed. Instead of selecting one of the options, type 911 at the prompt and pressEnter.

5. Continue the normal procedure for selecting options and specifying data until theinstallation begins. Debug output will be sent to the client’s display while the installationproceeds.


Method B: To Produce Debug Output When Using a bosinst_data Resource1. To enable debugging for the BOS installation program, set the value BOSINST_DEBUG =

yes in the control_flow stanza of the bosinst.data file that you are using for yourbosinst_data resource.

A minimum bosinst.data file for debugging purposes would contain the following lines:

control_flow:

BOSINST_DEBUG = yes

2. In addition to the processing you would normally do to install a client, include themodified bosinst_data resource as a resource for the operation.

After the client boots over the network, it will use the bosinst_data resource to obtainsettings for the installation. If the only data specified in your bosinst.data file isBOSINST_DEBUG = yes, you will be prompted for the remaining required informationbefore the installation will continue. Debug output will be sent to the client’s display whilethe installation continues.


Port Number Conflicts with NIM and Other ApplicationsWhen the NIM Master is configured, two port numbers are selected to be used by thenimesis daemon for client communications. The default port numbers are 1058 and 1059. Ifeither port is taken by another application, the nimesis daemon will not run and nimclientcommands will fail with an error similar to the following:

0042–006 nimclient: (To master) rcmd connection refused

If the nimesis daemon cannot be started, it may be necessary to stop the other applicantson the system to free the port.

Rebooting the system will usually eliminate the problem, because when a machine isbooted, the nimesis daemon is started very early by init and the likelihood that the portsare taken will be very small.


A-1Appendixes

Appendix A. Network Boot

Note that in the examples, tok0 and ent0 are adapter names. Do not use networknames, such as tr0, en0, or et0.

If an rs6k machine is not running, it is possible to determine whether IPL ROM emulation isrequired by booting the machine with the key turned to Secure. If the LEDs on the front ofthe machine eventually stop at 200, no emulation is needed.

To create IPL ROM emulation, see Creating IPL ROM Emulation Media on page A-6. If youare using NIM on machines that must use IPL ROM emulation to boot from a networkadapter, you should always initiate the boot once from the IPL menus from a systemconsole on the client. This writes the necessary addresses to NVRAM, avoiding a problemwith seeing alternating LEDs 227 and 229 during the network boot on older hardware. Afterinitiating the network boot/install from the client via this method once, the problem isautomatically corrected and subsequent network boot/installation may be initiated from theNIM master.

The platform and kernel type of a client determines the procedure required to boot themachine over the network.

To determine the platform of a running machine, use the bootinfo –p command if themachine is running AIX Version 4.2 or later. If the machine is running AIX 4.1, use thebootinfo –T command.

To determine the kernel type of a running machine, use the bootinfo –z command.

A-2 Installation Guide and Reference

Booting a Machine Over the Network

If you are booting an rs6k machine with an up kernel, use Method A. If you are booting anrs6k machine with an mp kernel, use Method B. For some models of rspc machines, youmay use Method C. For all other platforms and kernel types, follow the procedures in yourhardware documentation to perform the network boot.

Method A1. Begin with your machine turned off.

2. If your client requires IPL ROM emulation, insert the emulation disk into the diskette driveof the client, and turn on the machine with the hardware key in the Service position.When the bootp menus display, continue with step 3.

If your client does not require emulation, turn the key to the Secure position and turn onthe machine. Watch the LEDs on the front of the machine. They will eventually stopchanging and display 200. Then, change the key position to Service and quickly pressthe reset (yellow) button. When the bootp menus display, continue with step 3.

Note: On model numbers 570, 580, 58H, 59H, 591, and 595, the systempowers on in the Secure mode, the power–on light does not come on,and the LED remains blank. The system performs no further operationsuntil the key is set to the Normal or Service position. Refer to thedocumentation that came with your particular hardware model for moreinformation about performing a network boot of the machine.

3. From the bootp main menu, choose the Select BOOT (Startup) Device option.

4. In the next menu, select the boot device.

Select the network adapter to be used. Choose the adapter with the correct network type(Ethernet, Token–Ring, etc.) and adapter characteristics (thick cable, twisted pair, 16 Mbdata rate, 4 MB data rate, etc.).

5. Set or change the network addresses.

Note: You do not need to type the ’.’ characters in the IP addresses, but youmust specify any leading ‘0’ characters that make up parts of theaddresses.

Specify the IP address of:

– The client machine you are booting in the client address field.

– Your SPOT server in the bootp server address field.

– Your client’s gateway in the gateway address field. After you specify theaddresses, enter 99 to save the addresses and return to the main menu. If nogateway is used by the client to communicate with the boot server, you can leave thisfield empty.

If broadcasting will be used to obtain a boot image, leave these IP addresses empty.

6. From the main menu, select the Send Test Transmission (PING) option.

7. Verify that the displayed addresses are the same as the addresses you specified for yourboot device.

If the addresses are incorrect, enter 99 to return to the main menu. Then, go back tostep 3.

If the addresses are correct, select the START THE PING TEST option.

A-3Appendixes

If the ping test fails, verify that the addresses are correct, and perform network problemdetermination if necessary. If the ping test completes successfully, enter 99 to return tothe main menu.

8. From the main menu, select the Exit Main Menu and Start System (BOOT) option.

9. Turn the hardware key to the Normal position, and press Enter to boot your client overthe network.

Method B (Booting Micro Channel–Based, Symmetric MultiprocessorSystems)

1. Turn the key mode switch to the Secure position.

2. Turn the power switch on the system unit to the On position.

3. When the LED displays 200, turn the key mode switch to the Service position.

4. Press the Reset button once.

The LED persistently displays 260, 261, or 262, and The Maintenance Menu screenappears.

5. Select the System Boot option on the Maintenance Menu screen.

6. Select the Boot from Network option from the sub–menu. The MAIN MENU isdisplayed.

7. Select the Select BOOT (Startup) Device option on the MAIN MENU screen.

8. Select the network adapter from which the machine will boot. If there are multiplenetwork adapters installed, type 88 and press the Enter key to view the other entries.Type a number from the list and press the Enter key.

Note: If you are using a Token–Ring network, select the number thatcorresponds to the correct ring speed for your environment.

9. If a network adapter is selected, the SET OR CHANGE NETWORK ADDRESSESscreen is displayed next. The hardware address for the network adapter is displayed inthe hardware address field. Record the hardware address for defining the NIM machineobject.

If this client and the BOOTP server are on the same LAN, leave the IP address fields aszeros for the BOOTP request to be broadcasted over the LAN. If there are multipleBOOTP servers on the LAN or the client is on a different network to the server, enter theclient and server IP addresses. Type in the IP addresses using leading zeros to pad thenetwork address fields, for example, 009.101.002.050. If this machine must use agateway to reach the server, enter the IP address for the gateway.

Type 99 and press the Enter key to save the address information and return to theMAIN MENU.

10.(This step is optional.) Select the Send Test Transmission (PING) option on the MAINMENU to test the network connection between the client and the server systems. Type 3and press the Enter key to start the ping test. If the ping test was not successful, checkthat the IP addresses are correct and that the physical network connections are sound. Ifthe ping test was successful, type 99 and press the Enter key to return to the MAINMENU.

11.Select the Exit Main Menu and Start System (BOOT) option.

12.Follow the instructions on the screen to turn the key mode switch to the Normal positionand press the Enter key.

The BOOTP request will be issued, followed by a TFTP transfer of the network boot image.


Method C (Booting an rspc Platform Machine)1. Begin with your machine turned off.

2. If your system requires a System Management Services (SMS) diskette, insert it into thediskette drive of the client and turn on the machine. If you do not insert an SMS disketteat this time and one is required, you will be prompted to insert one later.

3. A graphics image is displayed on your screen. Press the F4 key as icons begin to displayfrom left to right on the bottom of your display.

Note: If the last icon is displayed prior to pressing the F4 key, the normalmode boot list is used instead of the System Management Servicesdiskette.

4. The System Management Services menu displays on your screen. Select the Utilitiesoption.

5. From the System Management Services Utilities menu, select the Remote InitialProgram Load Setup option.

6. From the Network Parameters screen, select the IP Parameters option.

7. Set or change the values displayed so they are correct for your client system.

Note: You do not need to specify any leading ‘0’ characters, but you mustspecify the ‘.’ characters in the IP addresses.

8. Specify the IP address of:

– The client machine you are booting in the client address field.

– Your SPOT server in the bootp server address field.

– Your client’s gateway in the gateway address field.

Note: If broadcasting will be used to obtain a boot image, leave these IPaddress fields empty.

9. Specify the subnet mask for your client machine if you are prompted for one in thesubnet mask field. All machines in your subnet have the same subnet mask.

10.After you specify the addresses, press Enter to save the addresses and continue.

11.The Network Parameters screen is displayed. Select the Ping option.

12.Select the network adapter to be used as the client’s boot device.

13.Verify that the displayed addresses are the same as the addresses you specified for yourboot device.

14.If the addresses are incorrect, press Esc until you return to the main menu. Then, goback to step 5.

15.If the addresses are correct, press Enter to perform the ping test. The ping test may takeseveral seconds to complete.

16.If the ping test fails, verify that the addresses are correct, and perform network problemdetermination if necessary. If the ping test completes successfully, press Enter toacknowledge the success message. Then, press Esc until you return to the SystemManagement Services menu.

17.From the System Management Services menu, choose the Select Boot Devices option.

18.Select the network adapter to be used for the network boot from the list of displayedbootable devices. Be sure to select the correct network type (Ethernet, Token–Ring, etc.)and adapter characteristics (thick cable, twisted pair, 16 Mb data rate, 4 Mb data rate,etc.). After making your selection, the machine will boot over the network.

A-5Appendixes

Note: When performing a BOS installation on a NIM client with a ”rspc” platform,the machine may fail to boot from the network adapter if network traffic isheavy.

If the network boot was initiated from the NIM Master, the machine will eventuallyboot from the disk. If the network boot was initiated from the SMS (SystemManagement Services) menus on the NIM client, the machine will return control tothe SMS menus.

Contact your service representative to receive a firmware update to correct thisproblem.


Creating IPL ROM Emulation Media

Use this procedure to create the IPL ROM emulation media on the NIM master for machinesthat do not have a BOOTP–enabled IPL ROM.

1. Insert a formatted diskette or a tape into the appropriate drive on the NIM master.

2. Enter:

bosboot –T rs6k \ –r /usr/lpp/bos.sysmgt/nim/methods/IPLROM.emulation \

–d DeviceName –M both

where DeviceName can be fd0, /dev/fd0, rmt0, or /dev/rmt0. This operation requires thatthe devices.base.rte fileset be installed on the machine upon which the emulationmedia is being created.

3. Insert the IPL ROM emulation media in the appropriate drive on the target machine.

From Web-based System Manager1. From the NIM container, from the NIM menu, select Create IPL ROM Emulation Media.

2. Use the dialog to complete the task; all fields are required.

From SMITIPL ROM emulation can also be created using the smit iplrom fast path.

G-1Glossary

Glossary

/usr file system. Contains files and programs necessary for operating the machine.

/tmp file system. A shared storage location for files.

/var file system. Contains files that are variable on a per–client basis, such as spool andmail files.

/ file system. The root file system; contains files that contain machine–specific configurationdata.

APAR. Authorized program analysis report. A report of a problem caused by a suspecteddefect in a current, unaltered release of a program.

applet. A program, intended for delivery over the Internet, which can be included in anHTML page, just as an image can be included.

apply. When a service update is installed or applied, it enters the applied state andbecomes the currently active version of the software. When an update is in the appliedstate, the previous version of the update is stored in a special save directory. This allowsyou to restore the previous version, if necessary, without having to reinstall it. Software thathas been applied to the system can be either committed or rejected. The installp –scommand can be used to get a list of applied products and updates that are available to beeither committed or rejected. See also commit on page *** on page G-1 and reject on page*** on page G-5.

Base Operating System (BOS). The collection of programs that controls the resources andthe operations of the computer system.

boot device. The device that assigns the fixed disk within the root volume group (rootvg)that contains the startup (boot) image.

bosinst.data. The file that controls the actions of the BOS installation program.

bundle. A collection of software products available for installation.

CD–ROM. High–capacity, read–only memory in the form of an optically read compact disc.

clean up. The clean–up procedure instructs the system to attempt to remove softwareproducts that were partially installed. The system also attempts to revert to the previousversion of the removed product. If the system successfully reverts to the previous version, itbecomes the currently active version. If this cannot be done, then the software product ismarked as broken. After the clean up procedure is complete, you can attempt to install thesoftware again.

client. In a distributed file system environment, a system that is dependent on a server toprovide it with programs or access to programs.

commit. When you commit software updates, you are making a commitment to that versionof the software product. When you commit a product update, the saved files from allprevious versions of the software product are removed from the system, thereby making itimpossible to return to a previous version of the software product. Software updates can becommitted at the time of installation by using either the Web-based System Manager orSMIT interface (or by using the –ac flags with the installp command). Note that committingalready applied software does not change the currently active version of the softwareproduct. It merely removes saved files for the previous version of the software product.Once a new version of a product update is committed, you cannot reject it if you want toreturn to the previous version of the code. To return to the previous version of the code, youmust reinstall the base level of the software product and reapply any associated updates.You should not commit software updates until you are sure the update does not cause other

G-2 Installation Guide and Reference

problems or regressions. Compare to apply on page *** on page G-1 and contrast withreject on page *** on page G-5 and remove on page *** on page G-5.

complete overwrite installation. An installation method that completely overwrites anexisting version of the Base Operating System that is installed on your system. Thisprocedure might impair recovery of data or destroy all existing data on your hard drives. Besure to back up your system before doing a complete overwrite installation.

Configuration Assistant. A graphical interface application used to performpost–installation system configuration tasks.

configure. To describe to a system the devices, optional features, and program productsinstalled on a system.

console device. During the installation of the Base Operating System (BOS), the systemconsole is the display device at the system on which you are installing the software.

corequisite. A product or update that must be installed concurrently with another specifiedproduct or update.

daemon. A program that runs unattended in the background to perform a standard service.Some daemons trigger automatically to perform their task and others operate on a timed orperiodic basis.

dataless. A workstation without local file systems or local boot images that accesses someof its resources remotely. Dataless clients use a local disk used for paging and dumpdevices.

dependent. A software product that requires another product or update to be installedbefore or at the same time it is installed. Contrast with prerequisite (page *** on page G-4).

destination disk. The disk to which you are installing.

directory. A type of file containing the names and controlling information for other files orother directories.

diskless. A workstation without local file systems or local boot images that accesses someof its resources remotely. Diskless clients boot remotely from a diskless server and use theserver for remote paging.

display. A computer output screen on which visual information is displayed.

display device. See display (page *** on page G-2).

environment. (1.) The settings for shell variables and paths that are set when the user logsin. These variables can be modified later by the user. (2.) A named collection of logical andphysical resources used to support the performance of a function.

environment variable. (1.) A variable that describes the operating environment of theprocess. Common environment variables describe the home directory, command searchpath, the terminal in use, and the current time zone (the HOME, PATH, TERM, and TZvariables, respectively). (2.) A variable that is included in the current software environmentand is therefore available to any called program that requests it.

file. The collection of related data that is stored and retrieved by an assigned name.Contrast with special file (page *** on page G-6).

file system. The collection of files and file management structures on a physical or logicalmass storage device, such as a diskette or minidisk.

file tree. The complete directory and file structure of a particular node, starting at the rootdirectory. A file tree contains all local and remote mounts performed on directories and files.

fileset. An individually installable option or update. Options provide specific function andupdates correct an error in, or enhance, a previously installed option.

fixed disk. (1.) A flat, circular, nonremovable plate with a magnetizable surface layer onwhich data can be stored by magnetic recording. A rigid magnetic disk used in a fixed–disk

G-3Glossary

drive. (2.) The term fixed disk is also used loosely in the industry for boards and cartridgescontaining microchips or bubble memory that simulate the operations of a fixed–disk drive.

full path name. The name of any directory or file expressed as a string of directories andfiles beginning with the root directory. See also path name (page *** on page G-2).

graphical user interface. A type of computer interface consisting of a visual metaphor of areal–world scene, often a desktop. Within that scene are icons, representing actual objects,that the user can access and manipulate with a pointing device.

hard disk. See fixed disk (page *** on page G-2).

hardware. The physical equipment of computing and computer–directed activities. Thephysical components of a computer system. Contrast with software (page *** on pageG-6).

host. (1.) The primary or controlling computer in a communications network. (2.) Acomputer attached to a network.

host name. The Internet address of a machine in the network. Also known as the host ID.

HTML. HyperText Markup Language is the tagging language that a web browser uses tointerpret and display documents.

hypertext. A way of presenting information online with connections between one piece ofinformation and another. These connections are called hypertext links. Thousands of thesehypertext links enable you to explore additional or related information throughout the onlinedocumentation. See also hypertext link (page *** on page G-3).

hypertext link. A connection between one piece of information and another. See alsohypertext (page *** on page G-3).

icon. A picture or graphical representation of an object on a display screen to which a usercan point to with a device, such as a mouse, to select a particular operation or perform acertain action.

initial program load (IPL). (1.) The initialization procedure that causes an operating systemto commence operation. (2.) The process by which a configuration image is loaded intostorage at the beginning of a work day or after a system malfunction. (3.) The process ofloading system programs and preparing a system to run jobs.

input device. The device that is the source of the software you are installing. The inputdevice can be a tape drive, CD–ROM drive, diskette drive, or a directory.

Installation Assistant. An application used to perform system configuration tasks.

installation image. An installation image contains a copy of the software you are installingin backup format, as well as copies of other files the system needs to install the softwareproduct.

Internet address. The numbering system used in TCP/IP internetwork communications tospecify a particular network or a particular host on that network with which to communicate.Internet addresses are commonly denoted in dotted decimal form.

IPL. See initial program load (page *** on page G-3).

license password. The key that allows a software product to be used. A string encodedwith license information for a software product.

locale. A subset of a user’s environment that defines conventions for a specified culture,such as time formatting, numeric formatting, monetary formatting, and characterclassification, conversion,and collation.

logical partition (LP). (1.) One to three physical partitions (copies). The number of logicalpartitions within a logical volume is variable. (2.) A fixed–size portion of a logical volume. Alogical partition is the same size as the physical partitions in its volume group. Unless thelogical volume of which it is a part is mirrored, each logical partition corresponds to, and its


contents are stored on, a single physical partition. See also logical volume (page *** onpage G-4).

logical volume (LV). A collection of physical partitions organized into logical partitions allcontained in a single volume group. Logical volumes are expandable and can span severalphysical volumes in a volume group. See also logical partition (page *** on page G-3),volume group (page *** on page G-6), and migration installation. (page *** on page G-4)

maintenance level update. The service updates that are necessary to upgrade the BaseOperating System (BOS) or an optional software product to the current release level. Seealso service update (page *** on page G-5).

migration installation. An installation method for upgrading AIX 3.2 or later to the currentrelease while preserving the existing root volume group. This method preserves the /usr,/tmp, /var, and / (root) file systems, as well as the root volume group, logical volumes, andsystem configuration files. Migration is the default installation method for any machine thatis running AIX 3.2 or later. See also root volume group (page *** on page G-5) and logicalvolume (page *** on page G-4).

monitor. (1.) A device that observes and verifies operations of a data processing system.(2.) Synonym for display.

mount. To make a file system accessible.

name server. A host that provides name resolution for a network. Name servers translatesymbolic names assigned to networks and hosts into the efficient Internet addresses usedby machines.

Network File System (NFS). A distributed file system that enables users to access files anddirectories located on remote computers and treat those files and directories as if they werelocal. NFS is independent of machine types, operating systems, and network architecturesthrough the use of remote procedure calls (RPC).

Network Installation Management (NIM). An environment that provides installation andconfiguration of software within a network interface.

new installation. An installation method used when the fixed disk or disks you are installingBOS onto are empty. A fixed disk is considered empty if it does not contain any data or if itcontains data not in a volume group.

NIM. See Network Installation Management (page *** on page G-4).

Object Data Manager (ODM). A data manager intended for the storage of system data.The ODM is used for many system management functions. Information used in manycommands and SMIT functions is stored and maintained in the ODM as objects withassociated characteristics.

option. An installable unit of a software package. Software product options are separatelyinstallable units that can operate independently from other options of that software package.

optional software. Also referred to as optional software products. Software that is notautomatically installed on your system when you install the Base Operating System (BOS).Optional software can be products packaged and sold with BOS. Optional software can alsobe separately purchased software products that are specially ordered and not sold as partof BOS. In either case, BOS must be installed on your system before you can install optionalsoftware.

package. An installable unit of a software product. Software product packages areseparately installable units that can operate independently from other packages of thatsoftware product.

paging. (1.) The action of transferring instructions, data, or both between real storage andexternal page storage. (2.) Moving data between memory and a mass storage device as thedata is needed.

path name. A file name specifying all directories leading to the file. See also full path name(page *** on page G-3).

G-5Glossary

physical volume. The portion of a single unit of storage accessible to a single read/writemechanism; for example, a drum, a disk pack, or part of a disk storage module.

preinstalled. Software that is installed by the manufacturer and ready to use.

prerequisite. A software product or a service update that must be installed before anothersoftware product or service update is installed. If you attempt to install software products orservice updates without the required prerequisite software, a system message displays thenames of required prerequisite software. Contrast with dependent (page *** on page G-2).

preservation installation. An installation method used when a previous version of theBase Operating System (BOS) is installed on your system and you want to preserve theuser data in the root volume group. However, this method overwrites the /usr, /tmp, /var,and / (root) file systems, so any user data in these directories is lost. System configurationmust be done after doing a preservation installation.

Preventive Maintenance Package (PMP). A maintenance level update for your system. APMP includes updates for the Base Operating System (BOS) and for each optional softwareproduct that is installed on your system.

primary language. The primary locale you want your system to use for screen information.

Problem Management Record (PMR). A number assigned by a support center to areported problem.

product. A software product is made up of software packages that are separatelyinstallable.

reboot. To reinitialize the execution of a program by repeating the initial program load (IPL)operation.

reject. To cause portions of applied updates from becoming permanent parts of the product,based on the results of a test period. When you reject an applied service update, theupdate’s files are deleted and the software vital product data (SWVPD) information ischanged to indicate that the update is no longer on the system. The previous version of thesoftware, if there is one, is restored and becomes the active version of the software.Contrast with apply (page *** on page G-1) and commit (page *** on page G-1).

remove. For a software option, the deletion of the option and all of its applied or committedupdates from the system. The software vital product data (SWVPD) information is changedto indicate that the option has been removed from the system. Depending on the option,system configuration information is also cleaned up, although this is not always complete. Ifa previous version, release, or level of the option is on the system, the system does notrestore the previous version. Only an option with its updates can be removed. Updatescannot be removed by themselves. See also commit (page *** on page G-1).

requisite. A software product or a service update that must be installed with anothersoftware product or service update. If you attempt to install software products or serviceupdates without the required software, a system message displays the names of requiredsoftware.

root user authority. The unrestricted ability to access and modify any part of the operatingsystem, usually associated with the user who manages the system.

root volume group (rootvg). A volume group containing the Base Operating System(BOS). See also migration installation. (page *** on page G-4)

server. On a network, the computer that contains the data or provides the facilities to beaccessed by other computers on the network.

service update. Software that corrects a defect in or adds new function to the BaseOperating System (BOS) or to an optional software product. See also maintenance levelupdate (page *** on page G-4).

SMIT. See System Management Interface Tool (page *** on page G-6).


software. Programs, procedures, rules, and any associated documentation pertaining to theoperation of a system. Contrast with hardware (page *** on page G-2).

source. A system, a program within a system, or a device that makes a request to a target.Contrast with target (page *** on page G-5).

special file. Used in the operating system to provide an interface to input/output devices.There is at least one special file for each device connected to the computer. Contrast withdirectory (page *** on page G-1) and file (page *** on page G-2).

stacked tape. A bootable tape with multiple software images.

System Management Interface Tool (SMIT). A set of menu–driven services that facilitatesthe performance of such system tasks as software installation and configuration, deviceconfiguration and management, problem determination, and storage management. SMIT isprovided in both a character–based curses interface and an AIXwindows–based graphicaluser interface.

target. A system, a program within a system, or a device that interprets, rejects, or satisfies,and replies to requests received from a source. Contrast with source (page *** on pageG-3).

Transmission Control Protocol/Internet Protocol (TCP/IP). A communicationssubsystem that allows you to set up local area and wide area networks.

Universal Coordinated Time (UCT). The standard term for worldwide time–telling that hasthe same meaning as Greenwich Mean Time.

update. See service update (page *** on page G-5).

upgrade. Software that fixes a defect in a previously released software product.

verify. The verify procedure instructs the system to verify the software you are installing.The system confirms that your software files are the correct length and contain the correctnumber of digits and characters. If any errors are reported, it might be necessary to installthe software product again. The verification process can add a significant amount of time tothe installation process.

volume group (VG). A set of one or more physical volumes from which space can beallocated to one or more logical volumes. A collection of 1 to 32 physical volumes(read–write fixed–disk drives) of varying size and type. See also logical volume (page *** onpage G-4).

Web–based System Manager. A graphical user interface (GUI) tool for managing systems.Based on the OO (Object Oriented) model, Web-based System Manager enables users toperform administration tasks by manipulating icons representing objects in the system, asan alternative to learning and remembering complex commands.

Index X-1

Index

Symbols/ file system

messages, 17-21root part, 16-2

/dev directory, 14-15/dev/ipldevice file, 17-21/etc/exclude.rootvg file, 14-5/etc/niminfo file, recovering, 25-12/etc/objrepos directory, after installing from system

backup, 14-15/tmp file system

free space in, 2-23, 14-3messages, 17-20, 17-21size during installation from backup, 14-15

/tmp/disk.image file, 17-20/tmp/unix file, 17-20/tmp/vgdata/rootvg directory, 14-20/usr file system, 27-28

messages, 17-19, 17-21troubleshooting when full, 17-11user part, 16-2

/usr/share file system, 16-2

Aaccessing an unbootable system, 17-8adapter_def resource, 27-15

defining, 27-15additional topics, dynamic host configuration

protocol, interacting with, 26-10advanced configuration, 25-1

adding another network type, 27-14backing up the NIM database, 25-13booting diagnostics, 25-16booting in maintenance mode, 25-18creating additional interface attributes, 25-3defining /usr vs. non–/usr SPOTs, 25-5defining a heterogeneous network, 27-12defining an lpp_source on CD–ROM vs. Disk,

25-8establishing a default route, 25-9establishing a static route, 25-10recovering the /etc/niminfo file, 25-12removing machines, 25-2restoring the database and activating the

master, 25-14unconfiguring the master, 25-15

advanced installationcontrolling the master or client, 24-2group member

excluding, 24-9including, 24-9

logsviewing boot, 24-18viewing configuration, 24-18viewing installation, 24-18

lpp_sourcecopying software, 24-16

maintaining software, 24-16removing software, 24-16running the check operation, 24-17

lppchk operationadding new members, 24-7defining, 24-6removing members, 24-8resetting, 24-4verifying installation, 24-19

resource groupallocating, 24-10defining, 24-10

resource groups, defining default, 24-10resource servers, using clients, 24-5SPOT

maint operation, 24-14managing software, 24-12rebuilding network boot images, 24-15sting software updates by keywordsting

software updates by keyword, 24-13sting softwaresting software, 24-12

standalone clientsting software updates by keywordsting

software updates by keyword, 24-13sting softwaresting software, 24-12

standalone clientsmaint operation, 24-14managing software, 24-12

advanced tasks, installation, 24-1all devices and kernels, 11-6allocate, resource group, 24-10allocate operation, 27-34allocating resources, resource groups, 24-10alt_disk_install, 23-29alternate disk installation, 15-1

cloning, 15-2data access, 15-6dynamic logical partitioning, 15-7examples, 15-7mksysb installation, 15-1phased installation, 15-3using SMIT, 15-7

Alternate Disk Migration Installation, 15-4American Standard Code for Information

Interchange, 9-1applying optional software

definition of, 12-8description, 12-1

ASCII Installation Assistant, 9-1introduction to tasks, 9-1

ASCII procedures, 12-1ASCII terminals

setting communications options, 14-17setting display and keyboard options, 7-2,

14-17setting options, 7-2

ATM Networks, 27-10converting generic networks into, 23-17

Installation Guide and ReferenceX-2

ATM networks, installing to clients, 23-17attributes

disk space, 14-15if, 25-3if1, 25-3if2, 25-3other_net_type, 27-12

Bbackup image, 14-15

adding a diskless or dataless client, 23-24adding a standalone client, 23-6changing installation modes, 14-19clients and SPOT resources, customizing,

23-19configuring the master, 23-3creating basic installation resources, 23-1,

23-3, 23-29diskless and dataless clients, configuring the

master and creating resources, 23-21diskless or dataless machine

initializing and booting, 23-26uninitializing, 23-28

mksysb install, 23-12non–prompted install, 23-15rte install, 23-10

backup, of system, 14-2exclude files, 14-4introduction, 14-6mounting and unmounting file systems, 2-23,

14-3procedure

lsmksysb command, 14-12lssavevg command, 14-12prerequisites, 2-23, 14-3preview information about a backup, 14-12root volume group, 2-24, 14-4st files in a system imagest files in a

system image, 14-14st information about filesets in a system

imagest information about filesets in asystem image, 14-13

verifying backup, 14-11verifying system backups, 14-13view the backup log, 14-13

binary compatibility, 8-2boot logs, view, 24-18boot resource, 27-16booting

diagnostics, 25-16over router, 26-5

booting the systemproblems with, 17-8procedure, 7-1, 8-5, 14-17

BOS installationcloning, 2-25, 14-16system backup, from, 14-15

BOS maintenance mode, accessing, 17-8BOS menus

installation and setting screen, 5-3installation summary screen, 5-2welcome screen, 5-2

BOS run–time image, source for, 27-40

bos.sysmgt.nim.master, removing, 26-2bos_inst operation, 27-37

ATM adapters, 23-17paging space, 26-6using the boot_client attribute, 27-41using the force_push attribute, 27-41using the preserve_res attribute, 27-42using the set_bootlist attribute, 27-42

bosboot, troubleshooting, 17-20, 17-21device problems, 17-20space problems, 17-20

bosinst.data file, 11-2ACCEPT_LICENSES variable, 11-5ALL_DEVICES_KERNELS variable, 11-6ALT_DISK_INSTALL_BUNDLE variable, 11-6ALWAYS_ALLOW variable, 11-10BOSINST_DEBUG variable, 11-5BOSINST_LANG variable, 11-9BUNDLES variable, 11-4CONNECTION variable, 11-8CONSOLE variable, 11-2COPYDIR variable, 11-10CREATE_JFS2_FS variable, 11-6CULTURAL_CONVENTION variable, 11-9CUSTOMIZATION_FILE variable, 11-4description, 10-1DESKTOP variable, 11-5DUMPDEVICE variable, 11-9ENABLE_64BIT_KERNEL variable, 11-6ERROR_EXIT variable, 11-4EXISTING_SYSTEM_OVERWRITE variable,

11-3FORCECOPY variable, 11-10GRAPHICS_BUNDLE variable, 11-6HDISKNAME variable, 11-9HTTP_SERVER_BUNDLE variable, 11-6IMPORT_USER_VGS variable, 11-6INSTALL_DEVICES_AND_UPDATES variable,

11-6INSTALL_METHOD variable, 11-2KERBEROS_5S_BUNDLE variable, 11-6KEYBOARD variable, 11-9LOCATION variable, 11-9MESSAGES variable, 11-9NETSCAPE_BUNDLE variable, 11-6nonprompted BOS installation, 11-2PHYSICAL_LOCATION variable, 11-8PRIMARY variable, 11-10procedure for using, 10-2PROMPT variable, 11-2prompted mode, with, 17-10PVID variable, 11-8REMOVE_JAVA_118 variable, 11-6RM_INST_ROOTS variable, 11-3RUN_STARTUP variable, 11-3SAN_DISKID variable, 11-8SECONDARY variable, 11-10SERVER_BUNDLE variable, 11-6SIZE_MB variable, 11-8SIZEGB variable, 11-9TCB variable, 11-4

bosinst.data sample file, 11-11

Index X-3

bosinst_data, 27-16defined, 27-16defining, 27-16overview, 27-16

bundles, 12-2, 16-3definition of, 12-2examples of, 16-3types of, 16-3

CCD or DVD

creating backups CD or DVD, 14-7ISO9660 format, 14-7

CD/DVDbootable, 14-6non–bootable, 14-6

cdrecord, 14-6cense acceptancecense acceptance, 11-5cense agreementscense agreements, 5-4censed programscensed programs, 12-2

packaging of, 12-2selection criteria for installation, 12-2

censes, softwarecenses, software, function of, 12-2change operation, 27-42check operation, 27-42cleaning up failed software installation, 2-26, 12-10client

determining control, 24-2diskless or dataless, adding, 23-24operations, 27-2tasks performed from, 25-1

client machine, verifying status of, 23-8client operations, 25-1clients

dataless, 27-5initializing, 27-8optional resources, 27-6required resources, 27-6

defining, 27-2diskless, 27-5

initializing, 27-8optional resources, 27-6required resources, 27-6

standalone, 27-5managing software, 27-5network booting, 27-5

standalone, adding, 23-6cloning, 2-25, 14-16cloning using Alternate Disk Installation, Alternate

Disk Installation, Alternate Disk Installation, 2-17commands

nim_clients_setup, 23-31nim_master_setup, 23-31nimclient, 25-1

committing service updatesdefinition of, 12-8introduction, 12-1

communicationsASCII terminals options, 7-2setting options for ASCII terminals, 14-17

compatibility, 8-2concepts, NIM, 27-1concurrency control, 24-21

configuration assistantconfiguring online documentation, 9-1documentation, 9-1web browser, installing, 9-1web server, installing, 9-1

configuration logs, view, 24-18configuration tasks, basic, 23-1configuration, system, 9-1

access remote resources, 9-1add license passwords, 9-1back up the system, 9-1change language environment, 9-1configure printer, 9-1create user accounts, 9-1date and time, 9-1exit and log in, 9-1install optional software, 9-1introduction to, 9-1set root password, 9-1st of tasksst of tasks, 9-1

control operations, definition of, 27-33control status, master or client, 24-2Create and Install a Software Bundle, Create and

Install a Software Bundle, software bundle, 2-12,2-21

creating software packages, 16-2cust operation, 27-43

asynchronous behavior, 26-3customizing BOS installation

bosinst.data file, 10-1introduction, 17-8procedure, 10-2, 17-8when system will not boot, 17-8

Ddataless clients, 27-5

initializing, 27-8managing software, 27-9resource

boot, 27-6dump, 27-6home, 27-6paging, 27-6resolv_conf, 27-7root, 27-6shared_home, 27-6SPOT, 27-6tmp, 27-7

resourcesoptional, 27-6required, 27-6

deallocate operation, 27-45debug, BOS installation, 11-5debug mode

installing BOS, 5-2NIM, 30-4NIM BOS installation, 30-4using a bosinst.data file for NIM BOS

installation, 30-6default routes, creating, 25-9define

machine group, 24-6resource group, 24-10


define operation, 27-45diag operation, 25-16, 27-45diagnostics

booting, 25-16loading from network, for diskless and dataless

machines, 25-17directories

/dev, 14-15/etc/objrepos, 14-15/tmp/vgdata/rootvg, 14-20

disk, specifying for BOS installationCD–ROM, DVD–ROM or tape, 7-4system backup, 14-19

disk spacemessages, 17-19planning for master machine, 23-3

diskless and dataless, managing software, 27-9diskless and dataless clients

creating resources to support, 23-21migrating, 26-7

diskless and dataless tasks, booting diagnostics,25-16

diskless clients, 27-5initializing, 27-8managing software, 27-9resource

boot, 27-6dump, 27-6home, 27-6paging, 27-6resolv_conf, 27-7root, 27-6shared_home, 27-6SPOT, 27-6tmp, 27-7

resourcesoptional, 27-6required, 27-6

diskless or dataless clientadding, 23-24initializing and booting, 23-26uninitializing, 23-28

disks, hard (fixed), 7-4displays, setting options for ASCII terminals, 7-2,

14-17distributed resources, 27-31dkls_init operation, 27-46dtls_init operation, 27-47dump resource, 27-17

defined, 27-17defining, 27-17overview, 27-17

DVD–RAMcreating backups DVD–RAM and UDF, 14-9Universal Disk Format, 14-9

dynamic host configuration protocol, interactingwith, 26-10

Eefix management, 12-19

efix control file, 12-29emgr command, 12-20epkg command, 12-29

installing and managing efixes, 12-20packaging efixes, 12-29

electronic license agreements, 5-4emergency fix management, see also efix

management, 12-19environment, changing language, 7-4epkg command, 12-29error conditions, 17-1, 30-1error messages

attempt to create bootable tape failed, 17-21check available disk space, 17-19error occurred during bosboot, 17-20format, 17-13hard disks not accessed, 17-18hard disks not configured, 17-18invalid or no boot device specified, 17-20NIM, 29-1no disks are available, 17-22not enough file space to create:

/tmp/disk.image, 17-20not enough file space to create: /tmp/unix,

17-20unable to expand file system /usr, 17-19

error recovery, 17-1, 30-1exclude files from system backup, 14-4exclude_files, 27-17


exporting resources, number of hosts, 26-2eznim, 22-1

Ffb_script, 27-18


FDDI, router, 26-5file systems

/tmp, 14-15free space in, 2-23, 14-3messages, 17-20, 17-21

/usrmessages, 17-19, 17-21troubleshooting when full, 17-11usr part, 16-2

/usr/share, 16-2mounting and unmounting, 2-23, 14-3router

messages, 17-21root part, 16-2

files/dev/ipldevice, 17-21/etc/exclude.rootvg, 14-5/etc/niminfo, 25-12/tmp/disk.image, 17-20/tmp/unix, 17-20/usr, 27-28bosinst.data

examples of, 11-11explanation of, 10-1introduction, 10-1procedure for using, 10-2

Index X-5

prompted mode, with, 17-10examples

bosinst.data, 11-11definition file for nimdef command, 28-2script resource, 28-1

image.data, 10-2, 14-15map, 14-20preserve.list, 10-2readme, viewing, iiisample, 28-1

filesets, 12-2, 16-2fix_bundle, 27-19


fix_query operation, 27-47fixed disks, 7-4fixes

sting for SPOTsting for SPOT, 24-13sting for standalone clientsting for standalone

client, 24-13

Ggeninstall command, 12-14, 16-1graphical user interface, sting for standalone

clientsting for standalone clientprerequisites, 12-3procedural overview, 12-1

graphical user interfaces, Installation Assistant,introduction to tasks, 9-1

group, resourceallocate, 24-10define, 24-10

groupsestablishing, 27-56machine, 27-56

defining, 24-6resource, 27-57

GUIs, 9-1

Hhard disks, 7-4

diagnostics, diskless and dataless, 25-16location codes of, 7-4specifying for CD/DVD–ROM or tape

installation, 7-4specifying for system backup installation, 14-19unaccessible, 17-18unconfigured, 17-18, 17-22

heterogeneous networks, defining, 27-12home resource, 27-19


Iif attribute, creating additional, 25-3if1 attribute, 25-3if2 attribute, 25-3image.data file, 10-2, 14-15image_data, 27-20

defined, 27-20defining, 27-20

overview, 27-20initiating

BOOTP request on diskless and datalesssystems, A-2

BOOTP request on standalone machine, A-2install_all, SMIT fast path, 12-5install_all_updates command, 12-7installation

alternate disk, 15-1change method of, 7-3verifying with lppchk operation, 24-19

installation (BOS), customizing with thebosinst.data file, 10-1

Installation Assistant, 9-2introduction to tasks, 9-1

installation images, mksysb configuration onbackup tape, 17-2

installation logs, view, 24-18installation methods

definition of, 7-3specifying, 7-3

installation resources, creating, 23-3installation screens (BOS)

Change Disk(s) Where You Want to Install, 7-4,14-19

Installing Base Operating System, 7-5, 8-6specifying system console, 7-3, 8-6, 14-18System Backup Installation and Settings

(BOS), 14-19installation tasks, advanced, 24-1installation, nonprompted, specifying with the

bosinst.data file, 10-1installing AIX

nonprompted new and complete overwriteinstallation, 2-9

using the CD to manually install a standalonesystem, new and complete overwriteinstallation, 2-2

installing BOSdebug mode, 5-2new and complete overwrite, 7-1preservation, 7-1

installing BOS from CD or DVD–ROM, procedure,specifying destination disk, 7-4

installing BOS from CD or tape, procedurebooting (starting) the system, 14-17initiating the installation, 14-17

installing BOS from CD, DVD or tape, customizingthe installation, 10-1

installing BOS from CD–ROM, procedurechanging language environment, 7-4prerequisites for, 7-1

installing BOS from CD–ROM or tape,troubleshooting, 17-13

installing BOS from CD/DVD–ROM, procedurebooting (starting) the system, 7-1initiating the installation, 7-1introduction to, 7-1

installing BOS from CD/DVD–ROM or tape,procedure

booting (starting) the system, 8-5initiating the installation, 8-5introduction to, 8-4, 8-5


installing BOS from DVD–ROM, procedure,prerequisites for, 7-1

installing BOS from system backupintroduction to, 14-15procedure, 14-16resolving reported problems, 17-3source system, 14-15target system, 14-15troubleshooting, 17-2

installing BOS using Web–based System Manager,14-16

system backup, 14-16installing optional software

applying, 12-1, 12-8cleaning up failed installation, 2-26, 12-10committing, 12-1, 12-8introduction to, 12-1prerequisites, 12-3procedural overview, 12-1procedure (graphical interface), 12-4procedure (SMIT), 12-5

accessing SMIT, 12-5status messages, 12-6

rejecting, 12-1, 12-9removing, 12-1, 12-9selection criteria, 12-2software licenses, 12-2software packaging, 12-2status messages (SMIT), 12-6troubleshooting, 2-26, 12-10, 17-19

installp format, creating software packages, 16-2installp_bundle, 27-21


InstallShield MultiPlatform, 12-14installing a package, 12-14response files, 12-16response files and NIM, 12-19silent installation, 12-16, 12-19uninstalling a package, 12-15

interface attribute, 25-3creating additional, 25-3

introduction to NIMcreating additional, definition of, 20-1diskless, definition of, 20-1network objects, definition of, 20-1resources, definition of, 20-1standalone, definition of, 20-1

IP address, determining, 27-12IPL ROM, emulation

creating media, A-6determining if needed, A-2

ISMP, see InstallShield MultiPlatform, 12-14

Kkeyboards

changing, 7-4setting, 7-4setting options for ASCII terminals, 7-2, 14-17

Llocale, 7-4location codes, of the hard disk, 7-4

logical volumes, accessing, 17-8introduction, 17-8procedure, 17-8

logsboot, viewing, 24-18configuration, viewing, 24-18installation, view, 24-18

lpp_source, 27-21copying software, 24-16defined, 27-21defining, 27-22maintaining software, 24-16overview, 27-21removing software, 24-16running the check operation, 24-17

lppchk operation, 27-48lppmgr command, 12-11lppmgr operation, 27-49lsmksysb command, 14-12lssavevg command, 14-12

defined, 27-33defining, 24-6, 27-56diskless or dataless

initializing and booting, 23-26uninitializing, 23-28

operations, 24-7, 24-9st ofst of, 27-33

Mmachines, 27-2maint_boot operation, 24-14, 27-49, 27-50

accessing (BOS), 17-8applying, 12-8asynchronous behavior, 26-3clients, standalone, 27-5committing, 12-8concepts defined, 12-7, 12-11maintain software in SPOT, 24-14maintain software on standalone clients, 24-14rejecting, 12-9removing, 12-9SPOT, 24-12standalone clients, 24-12using, 25-19

map files, 14-20activating, 25-14backing up NIM database, 25-13configuring, 23-3disabling push permissions, 24-2

activate the master, 25-14back up NIM database, 25-13restore NIM database, 25-14

removing, 26-2removing master fileset, 26-2unconfiguring, 25-15

messagesNIM error, 29-1NIM warning, 29-1system and error, 17-13

migratingclients, diskless and dataless, 26-7NIM SPOTs, 26-7

migrating installing AIX, migrating a system to theAIX 5.2, Migration, 2-6

Index X-7

migrating to new version, procedure, prerequisitesfor, 8-4

migration installation, definition of, 5-1mkcd command, 14-6mkinstallp command, 16-2mkisofs, 14-6mksysb, 27-23

alternate disk installation, 23-29backup images on CD/DVD, 14-6cloning, 2-25, 14-16defined, 27-23defining, 27-23installation from, 14-15overview, 27-23resolving reported problems, 17-3source for BOS run–time image, 27-40system backup tapes, 17-2troubleshooting installation from, 17-2

mksysb install, performing, 23-12monitors, setting options for ASCII terminals, 7-2,

14-17

Nname resolution, 26-4network, heterogeneous, defining, 27-12network boot, procedures for, A-1network booting, clients, standalone, 27-5network objects, clients

creating interface attributes, 25-3establishing a route between networks, 25-10

network types, supported, 27-10networks

ATM, 23-17defining, 27-10defining heterogeneous, 27-12NIM, 27-10

new and complete overwrite installation, 7-1definition of, 5-1

NIMalternate disk installation, 23-29client requests, tuning, 26-18configuration, basic, 23-1configure using EZNIM, 2-20error messages, 29-1introduction, 20-1Kerberos 5, 24-20Kerberos authentication, 24-20machines, 27-2networks, 27-10nimesis daemon, 26-18operations, basic, 23-1overview, 20-1response files and InstallShield MultiPlatform

products, 12-19SPOTs, migrating, 26-7warning messages, 29-1

NIM attributes, 27-12NIM concepts, 27-1NIM database

backing up, 25-13restoring, 25-14

NIM environment, 27-2defining, using the nimdef command, 26-8

NIM eznim, 22-1NIM groups, 27-56NIM networks, 27-10

defining, 27-10IP address, determining, 27-12routes, 27-12

NIM object definitions, name requirements, 26-9NIM objects, definitions, name requirements, 26-9NIM operations, 25-16

allocate, 27-34bos_inst, 27-37change, 27-42check, 27-42cust, 27-43deallocate, 27-45define, 27-45diag, 27-45diagnostics, booting, 21-2dkls_init, 27-46dtls_init, 27-47fix_query, 27-47lppchk, 27-48lppmgr, 27-49maint, 27-49maint_boot, 27-50maintenance mode, booting, 21-2reboot, 27-50remove, 27-51reset, 27-51resources, 21-2select, 27-51showlog, 27-52showres, 27-53software, removing, 21-2sync_roots, 27-54unconfig, 27-54update, 27-54

NIM output, suppressing, 26-3NIM resources, 27-15NIM routes, 27-12nim_script resource, 27-24nimclient command, 25-1nimdef command

NIM environment, defining, 26-8sample definition file, 28-2

non–prompted install, performing a, 23-15nonprompted installation, changing to prompted,

14-19nonprompted installation, customizing for, 10-1nonprompted mode, overriding, 17-10nonroot volume group, definition of, 14-2

Ooperations

allocate, 27-34basic, 23-1BOS run–time image, selecting source, 27-40bos_inst, 27-37change, 27-42check, 27-42cust, 27-43deallocate, 27-45define, 27-45


diag, 27-45dkls_init, 27-46dtls_init, 27-47excluding a group member, 24-9fix_query, 27-47including a group member, 24-9lppchk, 27-48lppmgr, 27-49maint, 27-49maint_boot, 27-50NIM

diag, 25-16machine, 27-33performed from client, 25-1

on client machines, 27-2performing, 27-33reboot, 27-50remove, 27-51reset, 27-51select, 27-51showlog, 27-52showres, 27-53st ofst of, 27-33sync_roots, 27-54types, 27-33unconfig, 27-54update, 27-54

optional softwarecleaning up failed installation of, introduction,

2-26, 12-10definition of, 12-1

optionslanguage environment, 7-4nonprompted installation, specifying with the

bosinst.data file, 10-1setting communications (ASCII), 7-2, 14-17setting display (ASCII), 7-2, 14-17setting monitor (ASCII), 7-2, 14-17specifying installation disk (BOS)

CD–ROM, DVD–ROM or tape, 7-4system backup, 14-19

specifying installation language, 7-3, 8-6specifying installation method (BOS), 7-3specifying system console, 7-3, 8-6, 14-18system configuration, 9-1

other_net_type attribute, 27-12output, NIM, suppressing, 26-3overview

defined, 27-24definition of, 12-2installp, 16-1

software filesets, 16-2ISMP, 16-1NIM, 20-1, 27-1overview, 27-24RPM, 16-1

Ppaging resource, 27-24

defining, 27-25port conflicts, nimesis daemon, 30-7post_migration command, 8-3pre_migration command, 8-3

preservation installation, 7-1definition of, 5-1

preserve.list file, 10-2preserve_res, 27-42problems, recovering from, 17-1, 30-1procedures

accessing BOS maintenance, 17-8advanced configuration, 25-1

adding another network type, 27-14backup up the NIM database, 25-13booting diagnostics, 25-16booting in maintenance mode, 25-18creating additional interface attributes, 25-3defining a heterogeneous network, 27-12defining an lpp_source on CD–ROM vs.

Disk, 25-8establishing a default route, 25-9establishing a static route, 25-10recovering the /etc/niminfo file, 25-12removing machines from the NIM

environment, 25-2restoring the database and activating the

master, 25-14unconfiguring the master, 25-15

advanced installationadding new members, 24-7allocating a resource group, 24-10controlling the master or client, 24-2copying software to an lpp_source, 24-16defining a machine group, 24-6defining a resource group, 24-10defining default resource groups, 24-10excluding a group member, 24-9including a group member, 24-9maintaining software in an lpp_source,

24-16maintaining software on a SPOT, 24-14removing members, 24-8removing software from an lpp_source,

24-16resetting machines, 24-4running the NIM check operation, 24-17standalone clients and SPOT resources,

managing software, 24-12sting software in a SPOTsting software in a

SPOT, 24-12sting software on a standalone clientsting

software on a standalone client, 24-12sting software updates by keywordsting

software updates by keyword, 24-13using clients as resource servers, 24-5verifying installation with lppchk operation,

24-19viewing logs, 24-18

advanced installation, managing softwareadding a diskless or dataless client, 23-24adding a standalone client, 23-6clients and SPOT resources, customizing,

23-19configuring the master, 23-3creating basic installation resources, 23-3creating resources to support

diskless/dataless clients, 23-21

Index X-9

diskless or dataless machine, initializingand booting, 23-26

diskless or dataless machine, uninitializing,23-28

mksysb install, performing, 23-12non–prompted install, 23-15rebuilding network boot images for a

SPOT, 24-15rte install, performing an, 23-10

customizing BOS installation, 10-2defining /usr vs. non–/usr SPOTs, 25-5identifying boot device, 17-21installing BOS from CD/DVD–ROM, 7-1installing BOS from CD/DVD–ROM or tape,

8-4, 8-5installing BOS from system backup, 14-16installing optional software, 12-1resizing /tmp, 17-20root volume group, backing up, 2-24, 14-4troubleshooting a mksysb installation, 17-2,

17-3troubleshooting full /usr file system, 17-11unlocking the root volume group, 17-19user volume group, backing up, 14-11verifying system backup, 14-13viewing readme files, iii

product identification, optional software, 12-2prompted installation, 14-19

help information, 14-19prompted mode, changing to (BOS), 17-10push permissions, changing to (BOS), disabling,

24-2

Rreadme files, viewing, iiireboot operation, 27-50recovery, 17-1, 30-1rejecting optional software

definition of, 12-9introduction, 12-1

remove operation, 27-51removing optional software

definition of, 12-9introduction, 12-1

reset operation, 27-51resolv_conf


resolv_conf resource, 27-25resource

boot, diskless/dataless, 27-6dump, diskless/dataless, 27-6home, diskless/dataless, 27-6resolv_conf, diskless/dataless, 27-7root, diskless/dataless, 27-6shared_home, diskless/dataless, 27-6SPOT, diskless/dataless, 27-6tmp, diskless/dataless, 27-7

resource groupallocate, 24-10define, 24-10

resource groupsallocating resources, 24-10defining, 27-57defining default, 24-10

resources, 27-15adapter_def, 27-15

defining, 27-15AIX Version 4.2 spots, network boot images,

27-29AIX Version 4.3 or later spots, 27-30boot, 27-16bosinst_data, 27-16

defining, 27-16clients and SPOT, customizing, 23-19distributed, 27-31dump, 27-17

defining, 27-17exclude_files, 27-17

defining, 27-18exporting, number of hosts, 26-2fb_script, 27-18

defining, 27-18fix_bundle, 27-19

defining, 27-19home, 27-19

defining, 27-20image_data, 27-20

defining, 27-20installp_bundle, 27-21

defining, 27-21lpp_source, 27-21

defining, 27-22mksysb, 27-23

defining, 27-23nim_script, 27-24operations, st ofst of, 27-15paging, 27-24

defining, 27-25resolv_conf, 27-25

defining, 27-25root, 27-26

defining, 27-26script, 27-26

defining, 27-27shared product object tree, 27-28shared_home, 27-27

defining, 27-27SPOT, 27-28

defining, 27-30st ofst of, 27-15tmp, 27-31

defining, 27-31resources, NIM, reducing space requirements,

26-3root directory, creating file resources, 26-11root resource, 27-26

defined, 27-26defining, 27-26

root volume group (rootvg), 2-24, 14-4definition of, 14-2unlocking, 17-19

router, booting over, 26-5


routes, 27-12creating a default, 25-9creating a static, 25-10

rte, source for BOS run–time image, 27-40rte install, performing, 23-10run–time image, 27-40

Ssample files, 28-1

bosinst.data, 11-11nimdef command, definition file, 28-2script resource, 28-1

savevg command, 14-11screens

Access a Root Volume Group (BOS), 17-10Change Disk(s) Where You Want to Install

(BOS), 7-4, 14-19Installing Base Operating System (BOS), 7-5,

8-6Maintenance (BOS), 17-10System Backup Installation and Settings, 14-19Volume Group Information (BOS), 17-10Welcome to Base Operating System

Installation and Maintenance (BOS), 17-10script, 27-26


script resource, sample file, 28-1select operation, 27-51service updates

committing, 12-8rejecting, 12-9removing, 12-9

shared product object tree, 27-28shared_home

defining, 27-27overview, 27-27

shared_home resource, 27-27defined, 27-27

showlog operation, 27-52showres operation, 27-53SMIT fast path

alt_clone, 15-7alt_mksysb, 15-7assist, 9-2cense_on_mediacense_on_media, 12-2cleanup_software, 12-14commit, 12-8compare_report, 12-12eznim, 22-1fixtolist_compare, 12-12install_all, 12-5install_latest, 12-5install_update, 9-3installed_license, 12-2instofix_compare, 12-12instolist_compare, 12-12maintain_software, 12-10reject, 12-9remove, 12-9rename_software, 12-13service_software, 12-11

update_all, 12-5update_by_fix, 12-5

SMIT interfacesCustom Install path

description of, 12-5prerequisites, 12-3procedural overview, 12-1

Installation Assistant, 9-1SMIT procedures, installing optional software, 12-1,

12-5software

sting for SPOTsting for SPOT, 24-12sting for standalone clientsting for standalone

client, 24-12software bundles, 12-2, 16-3

definition of, 12-2, 16-3examples of, 16-3

software filesets, definition of, 12-2software licenses, function of, 12-2software packages, definition of, 12-2software packaging

root part, 16-2share part, 16-2user part, 16-2

software products, 12-2applying, 12-8bundle, definition of, 12-2bundle, examples of, 16-3censed program, definition ofcensed program,

definition of, 12-2committing, 12-8fileset, definition of, 12-2identification of, 12-2package, definition of, 12-2packaging of, 12-2rejecting, 12-9removing, 12-9selection criteria for installation, 12-2

software service management, 12-11clean up software images, 12-13comparison reports, 12-12rename software images, 12-13

software updatessting for SPOTsting for SPOT, 24-13sting for standalone clientsting for standalone

client, 24-13software, optional, definition of, 12-1source system, 14-15SPOT

defined, 27-28defining, 27-30maintaining software, 24-14managing software, 24-12overview, 27-28resources, 25-7source for BOS run–time image, 27-40updating, 26-17

standalone client operations, 25-1standalone clients, 25-1, 27-5

adding, 23-6maintaining software, 24-12, 24-14, 27-5network booting, 27-5

standalone machines, determining control, 24-2

Index X-11

starting the system, 7-1, 8-5, 14-17static routes, creating, 25-10sting fixessting fixes

installed on a SPOT, 24-13installed on a standalone client, 24-13

sting informationsting informationsoftware in SPOT, 24-12software in standalone client, 24-12

sting software updatessting software updatesinstalled on a SPOT, 24-13installed on a standalone client, 24-13

suppressing, NIM output, 26-3sync_roots operation, 27-54system

booting (starting), 7-1, 8-5, 14-17configuring, 9-1

system backup, 14-2system backup to tape, 2-23system backup, BOS installation from, 14-15system bundles, 16-3system configuration, 9-1System Management Interface Tool, 9-1system messages, 17-13system settings

changing during BOS installation, 7-3creating bootable, troubleshooting, 17-21creating bootable,troubleshooting, 17-21

Ttapeblksz, 17-2

specifying for CD/DVD–ROM or tapeinstallation, 7-4

specifying for system backup installation, 14-19target system, 14-15

bos, installing, 21-1configuring NIM environment, 21-1installation, advanced, 24-1

terminals (ASCII), setting communications options,7-2, 14-17

tmp resource, 27-31defined, 27-31defining, 27-31overview, 27-31

troubleshooting, 17-13boot problems, 17-8

introduction, 17-8procedure, 17-8

cleaning up failed optional software installation,introduction, 2-26, 12-10

full /usr file system, 17-11installation from system backup (mksysb), 17-2

resolving reported problems, 17-3introduction, 17-1, 30-1network boot problem, 30-1

client and server, establishing networkcommunication, 30-1

obtaining the boot image from the server,30-1

running the boot image on the client, 30-3nonprompted mode, overriding, 17-10producing debug output, 30-4producing debug output from

a network boot image, 30-4BOS install program, 30-5

prompted mode, changing to, 17-10troubleshooting procedures, recovering /etc/niminfo

file, 25-12

Uunconfig operation, 27-54unconfiguring, master, 25-15update operation, 27-54update_all

install_all_updates command, 12-7SMIT fast path, 12-5

updates, service, explanation of, 12-1user volume group

backing up, 14-11definition of, 14-2

Vvolume groups

accessing, 17-8introduction, 17-8procedure, 2-24, 14-4, 14-11, 17-8

NIM, 29-1nonroot, 14-2root, 14-2, 17-19user, 14-2

WWeb–based System Manager, BOS installation,

14-16


Technical publication remarks form

Title : ESCALA AIX 5L Installation Guide and Reference

Reference Nº : 86 A2 07EG 01 Date: June 2003

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

86 A2 07EG 01REFERENCE

Utiliser les marques de découpe pour obtenir les étiquettes.

Use the cut marks to get the labels.

86 A2 07EG 01

AIX 5L InstallationGuide andReference

86 A2 07EG 01


86 A2 07EG 01


Documents

AIX 5L Installation - Bull On-line Support Portalsupport.bull.com/.../software/aix/aix5.2/g/86Y207EG01/86A207EG01.pdfAIX 5L Installation Guide and Reference ESCALA AIX REFERENCE