Installation and Migration Guide

Task A. Prepare the control workstation

This section describes the steps you take to prepare the control workstation. Note that it is a prerequisite for the control workstation to already have the correct level of AIX installed.

Step 1: Verify the control workstation requirements

Ensure that the following requirements are met:

Step 1.1: Verify the inst_root directories

If your control workstation has had the inst_root directories removed, the system cannot be used as a SPOT server. To determine if the inst_root directories have been removed, issue:

/usr/lib/instl/inurid -q; echo $?

If the result is 1, you will need to reinstall.

In addition to running the inurid -r command manually, the inst_root directories may have been removed on your system:

If the control workstation was installed by a non-mksysb NIM installation using a bosinst resource that had the RM_INST_ROOT variable set to yes.
If the control workstation was installed from a mksysb that had the inst_root directories removed before it was created.

Step 1.2: Review the READ THIS FIRST document

Refer to the READ THIS FIRST document that accompanies the PSSP installation media for the latest information for supported AIX release and |software update (PTF) levels.

Step 1.3: Verify the control workstation required software

The RS/6000 |machine you use as the control workstation must have |AIX Version 4.3.3, AIX 5L 5.1, or later Base |Operating System software installed.

Step 1.4: Verify the control workstation serial ports

The control workstation requires one serial port available per SP frame for the RS-232 cable that supports hardware monitoring and control.

|The following tables lists the number of tty ports you must allocate |for the specific servers.
|

SP model numbers tty port values
IBM pSeries 690 Does not require a tty port value, but the Hardware Management Console (HMC) must be connected by the SP Ethernet administrative LAN
RS/6000 H80, M80, and IBM pSeries 660 (6H0, 6H1, 6M1) 1
RS/6000 S70, S7A, and S80 or IBM pSeries 680 2

SP model numbers	tty port values
IBM pSeries 690	Does not require a tty port value, but the Hardware Management Console (HMC) must be connected by the SP Ethernet administrative LAN
RS/6000 H80, M80, and IBM pSeries 660 (6H0, 6H1, 6M1)	1
RS/6000 S70, S7A, and S80 or IBM pSeries 680	2

|Refer to Step 33: Enter non-SP frame information and reinitialize the SDR (optional) for more information.

Step 1.5: Verify the control workstation disk space

The control workstation must have ample disk space for the boot/install server files. See RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment for detailed information about space requirements.

Step 1.6: Install the Distributed Computing Environment (DCE) on the control workstation (optional)

If you plan to have PSSP use DCE, you must install DCE either as a client or server on the control workstation.

Note:: If using DCE, you should use a separate file system for the DCE configuration files. DCE-related file systems should be created under /var. Refer to IBM Distributed Computing Environment for AIX: Administration Guide--Introduction for more information.

Step 1.7: Verify the AIX error log size

You must verify that the AIX Error Log is at least 4096000 bytes. For example, issue:

/usr/lib/errdemon -l

To change the size of the AIX Error Log, issue:

/usr/lib/errdemon -s 4096000

Step 1.8: Update the root user path

You must run all installation tasks from root on the control workstation. All of the SP commands in this chapter are located in the following directories:

/usr/lpp/ssp/bin
/usr/lib/instl
/usr/sbin
/usr/bin
/usr/lpp/ssp/kerberos/bin

Note:: Refer to the "Naming conflict if using both Kerberos Version 4 and DCE" section in the "Security features on the SP system" chapter of PSSP: Administration Guide for additional information on using the k4destroy, k4init, and k4list commands.

To avoid entering the complete path name each time you want to invoke a command, you should add the directories in the previous list to the root user's path. For example, if using the Korn shell, add the directories to the path statement in root's .profile file. The following is an example of the root's user path statement:

PATH=$PATH:/usr/lpp/ssp/bin:/usr/lib/instl:/usr/sbin: \
/usr/lpp/ssp/kerberos/bin

If you would like to use the man pages during your install, you must set the MANPATH as follows:

|MANPATH=$MANPATH:/usr/lpp/ssp/man

In order for this path statement to take effect, you first have to execute .profile. For example, issue:

. /.profile

To verify that this step completed successfully, issue:

echo $PATH

Step 1.9: Verify name resolution on the control workstation

All names and addresses of all IP interfaces on SP nodes must be resolvable on the control workstation before you install and configure the SP.

Ensure that the control workstation host name is set. After you have set the host names and IP addresses on the control workstation, you should not change them for the duration of the installation.

|Step 1.10: Install the secure remote command software

| |

|PSSP 3.4 provides the ability to remove the dependency PSSP has on |the rsh and rcp commands issued as root by enabling the use |of a secure remote command method. It is the administrator's |responsibility to choose the secure remote command software and install it on |the control workstation. When installing the software, you should use a |separate file system for the secure remote shell configuration files and keys |to ensure that they are not picked up in the mksysb to be installed on the |nodes.

|All nodes must be at PSSP 3.2 or later before the secure remote |command method can be enabled.

|The secure remote command software will be installed on the nodes by |editing the script.cust file to install the secure remote |command software after the PSSP code is installed.

|There is usually a requirement that root be the owner of it's home |directory to run secure remote commands. By default, this is not true |in a general AIX installation |(earlier than AIX 5.1) with the root home directory defaulting to (/) owned by |bin. Either / must be changed to be owned by root, or the |administrator must create a new home directory for root. In this |environment, it is also beneficial to create root's home directory in a |separate file system to make sure that any keys generated by the root user are |not contained in the mksysb and become installed on the nodes.

|Public keys must be generated and known_hosts file set up such that the |PSSP code can run |the secure remote commands as root without being prompted for |passwords or passphrases. |The known_hosts files must contain both long and short names for the |nodes. Applications that have changed to support the secure remote command |environment such as dsh will appear to hang if the secure remote |command code issues a prompt when the command is run. |See SSH The Secure Shell The Definitive Guide for |additional information. See PSSP: Diagnosis Guide for diagnosing secure |remote setup problems.

|After the secure remote command software is installed and the daemon is |started on the control workstation, the administrator should ensure that the |root ID can issue a secure remote command and secure remote copy command from |the control workstation to the control workstation without being prompted for |input (for example, passwords, passphrases). This ability to run secure |remote commands and copies is required to run the PSSP code using the secure |remote command method.

|Some of the secure remote copy products default the location of the secure |remote |command to /usr/local/bin/ssh. If your product does this, |be sure that the secure remote command executable is located in this directory |or linked to this directory.

|When the PSSP code issues secure remote commands and copies, it uses no |options on the call to the secure remote product. In this way, we |have built no dependency on a particular implementation of a secure remote |command product.

Step 2: Verify the network requirements

Using your node worksheets, check all |SP Ethernet administrative LAN and additional adapter information to ensure that you have assembled the correct host name, IP address, and netmask data for installation.

Step 3: Connect frames to your control workstation

Connect RS-232 and Ethernet cables from the SP system frames and from the SP-attached servers |or clustered enterprise servers to the control workstation according to your SP Control Workstation Network Worksheet. Your IBM Customer Engineer (CE) performs this step. |The CE will need access to the control workstation to run |diagnostics. See RS/6000 SP: Installation and Relocation for instructions.

Step 4: Configure RS-232 control lines

|You must allocate the appropriate number of tty ports in this |step. Each SP frame in your system requires a serial port on the |control workstation configured to accommodate the RS-232 line. |SP-attached servers require different numbers of tty ports depending on the |server type. For example, an S80 requires two tty ports, so if you have |two SP frames and one S80 SP-attached server, configure four tty |terminals. Refer to Step 1.4: Verify the control workstation serial ports for valid tty port values.

If using: Do this:
SMIT

TYPE
smit tty

The TTY menu appears

SELECT
Add a TTY
SELECT
tty rs232 Asynchronous Terminal
SELECT
An appropriate serial port (parent adapter) connection. For example, sa0.

A data entry window appears

PRESS
List to show the available port numbers. Select a port number. For example, 0, 1, 2, 3.
PRESS
Ok to configure the line.

mkdev Enter a command similar to this example, which defines and configures an RS-232 line for parent adapter sa0 on port serial port 1:
mkdev -c tty -t tty -s rs232 -p sa0 -w 1

This example configures a second port of a two-frame system:
mkdev -c tty -t tty -s rs232 -p sa1 -w 2

You can accept the default Baud rate of 9600. The internal system daemon called hardmon changes the rate to 19200.

If using:	Do this:
SMIT	TYPE smit tty The TTY menu appears SELECT Add a TTY SELECT tty rs232 Asynchronous Terminal SELECT An appropriate serial port (parent adapter) connection. For example, sa0. A data entry window appears PRESS List to show the available port numbers. Select a port number. For example, 0, 1, 2, 3. PRESS Ok to configure the line.
mkdev	Enter a command similar to this example, which defines and configures an RS-232 line for parent adapter sa0 on port serial port 1: mkdev -c tty -t tty -s rs232 -p sa0 -w 1 This example configures a second port of a two-frame system: mkdev -c tty -t tty -s rs232 -p sa1 -w 2
You can accept the default Baud rate of 9600. The internal system daemon called hardmon changes the rate to 19200.

Step 5: Tune all control workstation network adapters

Various models of network adapters can have different values for transmit and receive queue sizes. The queue setting for Micro Channel adapters is 512. For PCI adapters, the queue setting is 256 or greater.

You can set these values using SMIT or the chdev command. If the adapter you are changing is also the adapter for the network you are logged in through, you will have to make the changes to the database only. Then reboot the control workstation for the changes to become effective.

If using: Do this:
SMIT

TYPE
smit devices
* The Devices menu appears
SELECT
Communication
* The Communication menu appears
SELECT
The adapter you want to reset (for example, Ethernet Adapter)
* The Ethernet Adapter menu appears
SELECT
Adapter
* The Adapter menu appears
SELECT
Change / Show Characteristics of an Ethernet Adapter
* An Ethernet Adapter window appears
SELECT
An adapter from the list shown
* The Change / Show Characteristics of an Ethernet Adapter window appears
CHANGE
The HARDWARE TRANSMIT queue size. (See note 2 below.)
CHANGE
Apply change to DATABASE only to yes. (Press List and select yes.)
PRESS
Ok to apply the changes to the database.

chdev Enter
chdev -P -l ent0 -a xmt_que_size=512

You must reboot the control workstation in order for the changes to take effect.
To determine the name of the TRANSMIT queue size, issue:
lsattr -l adapter_name -E

In response, a list of all of the values for the different variables, what they are, and the name of the variable will be displayed.
In the previous example, an MCA adapter with AIX 4.2.1 or later was used.

If using:	Do this:
SMIT	TYPE smit devices * The Devices menu appears SELECT Communication * The Communication menu appears SELECT The adapter you want to reset (for example, `Ethernet Adapter`) * The Ethernet Adapter menu appears SELECT Adapter * The Adapter menu appears SELECT Change / Show Characteristics of an Ethernet Adapter * An Ethernet Adapter window appears SELECT An adapter from the list shown * The Change / Show Characteristics of an Ethernet Adapter window appears CHANGE The HARDWARE TRANSMIT queue size. (See note 2 below.) CHANGE `Apply change to DATABASE only` to yes. (Press List and select yes.) PRESS Ok to apply the changes to the database.
chdev	Enter chdev -P -l ent0 -a xmt_que_size=512
You must reboot the control workstation in order for the changes to take effect. To determine the name of the TRANSMIT queue size, issue: lsattr -l adapter_name -E In response, a list of all of the values for the different variables, what they are, and the name of the variable will be displayed. In the previous example, an MCA adapter with AIX 4.2.1 or later was used.

Step 6: Configure the control workstation Ethernet adapters

Use SMIT or the chdev command to configure each Ethernet adapter connecting |the nodes on your frames to the control workstation. For details on the correct use of chdev, see IBM AIX Commands Reference, the man pages, or the online information database.

Refer to your SP Control Workstation Network Worksheet in RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment.

If the adapter is not yet defined or configured, use smit mkinet or the mkdev command instead of smit chinet or chdev to specify a new IP host name and netmask values. If you are adding an extension node to your system, you may want to configure the adapters now. For more information, refer to Chapter 10, Installing extension nodes.

If using: Do this:
SMIT

TYPE
smit chinet

The Available Network Interfaces menu appears

SELECT
The Ethernet interface to be configured
ENTER
IP interface and netmask information from worksheet.
SELECT
up as the Current STATE option
PRESS
Ok to complete operation

chdev Enter a command similar to this example, which configures an SP Ethernet administrative LAN adapter.
chdev -l en0 -a netaddr=129.33.41.1 -a netmask=255.255.255.0 -a state=up

mkdev Enter a command similar to this example, which defines and configures an SP Ethernet administrative LAN adapter.
mkdev -c if -s EN -t en -a netaddr=129.33.34.1 \ -a netmask=255.255.255.0 -a state=up -q -w en0

If using:	Do this:
SMIT	TYPE smit chinet The Available Network Interfaces menu appears SELECT The Ethernet interface to be configured ENTER IP interface and netmask information from worksheet. SELECT up as the `Current STATE` option PRESS Ok to complete operation
chdev	Enter a command similar to this example, which configures an SP Ethernet administrative LAN adapter. chdev -l en0 -a netaddr=129.33.41.1 -a netmask=255.255.255.0 -a state=up
mkdev	Enter a command similar to this example, which defines and configures an SP Ethernet administrative LAN adapter. mkdev -c if -s EN -t en -a netaddr=129.33.34.1 \ -a netmask=255.255.255.0 -a state=up -q -w en0

Step 7: Verify the control workstation interfaces

Verify the configuration for each Ethernet adapter in the control workstation. You can verify that the adapter is installed even if it is not cabled to the SP system yet.

Verify each Ethernet adapter by pinging its IP address and seeing if you get a proper response. If you do not receive a response, debug the network problem, and reconfigure the adapter.

For example:

ping -c 1 129.33.34.1

Step 8: Ensure that the necessary daemons are running on the control workstation

Check to see if the System Resource Controller (SRC) is running by issuing the following:
```
lssrc -a
```
If you get an error message similar to the following, then SRC is not running:
```
The System Resource Controller daemon is not active
```
To start SRC, uncomment or add the srcmstr entry in the /etc/inittab file and reboot the control workstation using the shutdown -Fr command.
In /etc/inittab, the srcmstr entry should look like:
```
srcmstr:2:respawn:/usr/sbin/srcmstr # System Resource Controller
```
Check to see if the bootps and tftp entries are uncommented in the /etc/inetd.conf file. If they are commented (a leading pound sign designates a comment), uncomment the two entries in the file and issue the following:
```
refresh -s inetd
```

Step 9: Change the control workstation maximum default processes

When you first install your system, the number of processes is set to an AIX default. You will not be able to continue installing your system with this default value--you must increase the number. IBM suggests changing the maximum number to 256.

If using: Do this:
SMIT

TYPE
smit system

The System Environments menu appears

SELECT
Change / Show Characteristics of Operating System
ENTER
256 for the maximum number of processes allowed per user.
PRESS
Ok

chdev Enter:

chdev -l sys0 -a maxuproc='256'

If using:	Do this:
SMIT	TYPE smit system The System Environments menu appears SELECT Change / Show Characteristics of Operating System ENTER 256 for the maximum number of processes allowed per user. PRESS Ok
chdev	Enter: chdev -l sys0 -a maxuproc='256'

Step 10: Change the control workstation tunables and tunable values

When you first install your system, the network tunable values are set to AIX defaults. (A tunable is a performance parameter you can set to a value that makes your system run its workload most efficiently.) Your system may not run efficiently with the default values. Use the no command to display these values. This command and all its parameters are described in IBM AIX Commands Reference.

When you install PSSP on your control workstation, change the network tunables on the control workstation to the suggested values in the following table.

Table 1. Control Workstation Tunables

Tunable Recommended Initial Value Description
thewall 16384 The upper bound on the amount of real memory that can be used by the communications subsystem. The units are in 1 KB increments.
Note:
As of AIX 4.3.3, the recommended initial value should not be set because it is automatically sized by the system at boot.

sb_max 163840 Upper limit on the size of the TCP and UDP buffers in mbufs of allocated space to a connection.
ipforwarding 1 Specifies whether the kernel should forward packets. A value of 1 forwards packets when they are not for the local system; a value of 0 prevents forwarding.
tcp_sendspace 65536 The default size of the TCP send window.
tcp_recvspace 65536 The default size of the TCP receive window.
udp_sendspace 32768 The default size of the UDP send buffer. The effective maximum is 65536 (64K).
udp_recvspace 65536 The default size of the UDP receive buffer.
tcp_mssdflt 1448 Maximum package size for remote network.
tcp_pmtu_discover 0 TCP MTU path discovery (AIX 4.3.1 or later).
udp_pmtu_discover 0 UDP MTU path discovery (AIX 4.3.1 or later).

Tunable	Recommended Initial Value	Description
thewall	16384	The upper bound on the amount of real memory that can be used by the communications subsystem. The units are in 1 KB increments. Note: As of AIX 4.3.3, the recommended initial value should not be set because it is automatically sized by the system at boot.
sb_max	163840	Upper limit on the size of the TCP and UDP buffers in mbufs of allocated space to a connection.
ipforwarding	1	Specifies whether the kernel should forward packets. A value of 1 forwards packets when they are not for the local system; a value of 0 prevents forwarding.
tcp_sendspace	65536	The default size of the TCP send window.
tcp_recvspace	65536	The default size of the TCP receive window.
udp_sendspace	32768	The default size of the UDP send buffer. The effective maximum is 65536 (64K).
udp_recvspace	65536	The default size of the UDP receive buffer.
tcp_mssdflt	1448	Maximum package size for remote network.
tcp_pmtu_discover	0	TCP MTU path discovery (AIX 4.3.1 or later).
udp_pmtu_discover	0	UDP MTU path discovery (AIX 4.3.1 or later).

Using the no Command

To display network tunable values, enter:

no -a

To change the value of tcp_mssdflt, enter:

no -o tcp_mssdflt=1448

When you change the network tunables, they take effect immediately. However, they are not preserved across a boot. To make the changes to the tunables effective across boots, add the no -o commands you used to change the network tunables to the last section of the /etc/rc.net file. Using the same syntax, place the commands under the line:

/usr/sbin/no -o extendednetstats=0 >>/dev/null 2>&1

For example:

/usr/sbin/no -o tcp_mssdflt=1448 >>/dev/null 2>&1

Step 11: Define space for the /spdata directory

The /spdata directory contains, among other items, mksysb, and installp file sets. IBM suggests you create a separate volume group for the /spdata file system. These file sets require a minimum of 2 GB of disk space. You will require additional disk space if you need to support multiple AIX and PSSP release levels, and multiple mksysb images. If you have not done so already, use RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment to help you estimate how much space you need to define.

To define space for the /spdata directory, refer to the following table to determine which steps to follow. Do either Procedure A or B. Do not perform more than one procedure.

Procedure To: Follow these steps:.
A Define a new volume group

Do Step 11.1: Define a volume group
Do Step 11.2: Create the logical volume for /spdata
Do Step 11.3: Create the file system for /spdata
Do Step 11.4: Mount the /spdata file system
Do Step 12: Create the required /spdata directories

B Use an existing volume group (such as rootvg) and define a new file system.

Do Step 11.2: Create the logical volume for /spdata
Do Step 11.3: Create the file system for /spdata
Do Step 11.4: Mount the /spdata file system
Do Step 12: Create the required /spdata directories

Procedure	To:	Follow these steps:.
A	Define a new volume group	Do Step 11.1: Define a volume group Do Step 11.2: Create the logical volume for /spdata Do Step 11.3: Create the file system for /spdata Do Step 11.4: Mount the /spdata file system Do Step 12: Create the required /spdata directories
B	Use an existing volume group (such as rootvg) and define a new file system.	Do Step 11.2: Create the logical volume for /spdata Do Step 11.3: Create the file system for /spdata Do Step 11.4: Mount the /spdata file system Do Step 12: Create the required /spdata directories

Step 11.1: Define a volume group

The logical volume manager (LVM) configuration you define can also include placing the /spdata file system in its own volume group rather than using the default volume group rootvg.

You cannot create a separate volume group if all control workstation disks are in use or the control workstation has only one physical volume. When working with larger disks that are greater than 4 GB, you must specify the physical partition size to be 8 MB or more for the spdata volume group.

If using: Do this:
SMIT

TYPE
smit vg

The Volume Groups menu appears

SELECT
Add a Volume Group

The Add a Volume Group window appears

TYPE
The volume group name (for example, spdatavg).
TYPE
The physical volume name (press F4 and select a volume).
PRESS
Ok to create the volume group.

SMIT automatically varies on the volume group.
mkvg The following command will create a new logical volume named spdatavg, using hdisk1 as the physical volume.
mkvg -f -y spdatavg hdisk1

After you create the new volume group spdatavg, vary on the volume group on your control workstation using the varyonvg command.
varyonvg spdatavg

If using:	Do this:
SMIT	TYPE smit vg The Volume Groups menu appears SELECT Add a Volume Group The Add a Volume Group window appears TYPE The volume group name (for example, spdatavg). TYPE The physical volume name (press F4 and select a volume). PRESS Ok to create the volume group. SMIT automatically varies on the volume group.
mkvg	The following command will create a new logical volume named spdatavg, using hdisk1 as the physical volume. mkvg -f -y spdatavg hdisk1 After you create the new volume group spdatavg, vary on the volume group on your control workstation using the varyonvg command. varyonvg spdatavg

Step 11.2: Create the logical volume for /spdata

You now need to create the logical volume called spdata_lv with 2 GB, assuming a 4 MB physical partition size.

If using: Do this:
SMIT

TYPE
smit mklv

The Add a Logical Volume menu appears

TYPE
The volume group name (for example, spdatavg or press F4 and select a volume).
TYPE
The logical volume name (for example, spdata_lv).
TYPE
The number of logical partitions (for example, 500).
TYPE
The maximum number of logical partitions (for example, 512).
PRESS
Ok to create the logical volume.

mklv To create a logical volume spdata_lv, use the mklv command:
mklv -y spdata_lv -x 512 spdatavg 500

If using:	Do this:
SMIT	TYPE smit mklv The Add a Logical Volume menu appears TYPE The volume group name (for example, spdatavg or press F4 and select a volume). TYPE The logical volume name (for example, spdata_lv). TYPE The number of logical partitions (for example, 500). TYPE The maximum number of logical partitions (for example, 512). PRESS Ok to create the logical volume.
mklv	To create a logical volume spdata_lv, use the mklv command: mklv -y spdata_lv -x 512 spdatavg 500

Step 11.3: Create the file system for /spdata

You now need to create the /spdata file system on the control workstation. The file system must be mounted as /spdata.

If using: Do this:
SMIT

TYPE
smit crfs
SELECT
Add a Journaled File System (AIX 5L 5.1 systems only)
SELECT
Add a Journaled File System on a Previously Defined Logical Volume
SELECT
Add a Standard Journaled File System
SELECT
Your logical volume (press F4 and select a volume).
SPECIFY
/spdata as mount point
SELECT
yes for Mount AUTOMATICALLY at system restart?
PRESS
Ok to create the file system.

crfs To create a file system /spdata within the newly-created logical volume spdata_lv, use the crfs command. The following example creates the /spdata file system, using logical volume spdata_lv and mount point /spdata. It also adds the /spdata into the /etc/filesystems to be automatically mounted at system restart.
crfs -v jfs -d spdata_lv -m /spdata -A yes -p rw -t no -a bf=true

If using:	Do this:
SMIT	TYPE smit crfs SELECT Add a Journaled File System (AIX 5L 5.1 systems only) SELECT Add a Journaled File System on a Previously Defined Logical Volume SELECT Add a Standard Journaled File System SELECT Your logical volume (press F4 and select a volume). SPECIFY /spdata as mount point SELECT yes for `Mount AUTOMATICALLY at system restart?` PRESS Ok to create the file system.
crfs	To create a file system /spdata within the newly-created logical volume spdata_lv, use the crfs command. The following example creates the /spdata file system, using logical volume spdata_lv and mount point /spdata. It also adds the /spdata into the /etc/filesystems to be automatically mounted at system restart. crfs -v jfs -d spdata_lv -m /spdata -A yes -p rw -t no -a bf=true

Step 11.4: Mount the /spdata file system

After you create the new /spdata file system, you need to mount it on the control workstation. Use the AIX command mount.

The following example mounts the /spdata file system:

mount /spdata

Step 12: Create the required /spdata directories

Make sure you mount the new /spdata file system before you create the /spdata directories. The SP requires that you create subdirectories on the /spdata file system for storing critical PSSP data. Make sure the directories have the permissions rwxr-sr-x. Table 2 lists the required directories.

Table 2. Required /spdata Directories

Directory Description mkdir Command
/spdata/sys1/install/name/lppsource Location of required AIX file sets mkdir -p /spdata/sys1/install/name/lppsource
/spdata/sys1/install/images Location of all required AIX mksysb images mkdir /spdata/sys1/install/images
/spdata/sys1/install/pssplpp/code_version Location of all SP installp file sets mkdir -p \ /spdata/sys1/install/pssplpp/code_version
/spdata/sys1/install/pssp Location of NIM configuration data files mkdir /spdata/sys1/install/pssp

name is the new lpp_source name for the nodes (such as aix433 if that is what you called the subdirectory with the AIX 4.3.3 lppsource). Keep in mind that the setup_server program looks for this name later on during the installation process. By default, it is set to the string "default," so that if you use that as your subdirectory name, you do not have to change the name here.
code_version is the version of code of the form PSSP-x.y. (such as, PSSP-3.4).

Directory	Description	mkdir Command
/spdata/sys1/install/`name`/lppsource	Location of required AIX file sets	mkdir -p /spdata/sys1/install/`name`/lppsource
/spdata/sys1/install/images	Location of all required AIX mksysb images	mkdir /spdata/sys1/install/images
/spdata/sys1/install/pssplpp/`code_version`	Location of all SP installp file sets	mkdir -p \ /spdata/sys1/install/pssplpp/`code_version`
/spdata/sys1/install/pssp	Location of NIM configuration data files	mkdir /spdata/sys1/install/pssp
`name` is the new lpp_source name for the nodes (such as aix433 if that is what you called the subdirectory with the AIX 4.3.3 lppsource). Keep in mind that the setup_server program looks for this name later on during the installation process. By default, it is set to the string "default," so that if you use that as your subdirectory name, you do not have to change the name here. `code_version` is the version of code of the form PSSP-x.y. (such as, PSSP-3.4).

Step 13: Define space for the NIM boot images

Before creating an AIX boot/install server, ensure that there is sufficient space in the root (/) file system or create a separate file system for /tftpboot to manage the space required for the boot images (approximately 25 MB per lppsource level supported) created by NIM. For example, to increase the size of the root file system by 25 MB, issue:

chfs -a size=+51200 /

If you want to create a logical volume and file system in either the rootvg or /spdatavg volume group, follow the instructions in Step 11: Define space for the /spdata directory.

Step 14: Copy the AIX LP images and other required AIX LPs and PTFs

|You must copy the AIX file sets into an lppsource directory on the |hard drive of your control workstation. For AIX 4.3.3, |the files go into |/spdata/sys1/install/name/lppsource.

|In AIX 5L 5.1, changes were made to allow installation with |installers other than installp to allow new installation media |formats. With AIX 5L 5.1, two new commands (geninstall |and gencopy) were introduced, which call installp |or bffcreate, or other commands as appropriate. |Additional subdirectories have also been added into the NIM LPP_SOURCE with |AIX 5L 5.1. For NIM, instead of just putting everything in the |LPP_SOURCE directory, appropriate subdirectories are created by the |gencopy and bffcreate commands and the images are copied to |those subdirectories |based on the format of the install package.

|You must copy the AIX file sets |under the /spdata/sys1/install/name/lppsource |directory on your hard disk on the control workstation. The |bffcreate command places the files into the appropriate |subdirectory:

|AIX 4.3.3: |/spdata/sys1/install/name/lppsource |
|AIX 5L 5.1: |/spdata/sys1/install/name/lppsource/installp/ppc |/spdata/sys1/install/name/lppsource/rpm/ppc

|You can download all of the AIX file sets (a very large number) or |only the minimal required AIX file sets |(approximately 500 MB for AIX 4.3.3 and approximately |1 GB for AIX 5L 5.1). Download the AIX file sets and the required AIX LPs into |/spdata/sys1/install/name/lppsource. The AIX |file sets and required AIX LPs must exist in this directory. Links to |file sets in other directories are not allowed. If you change the path |name in any way, the installation fails.

The following is the minimal list of AIX file sets required to perform mksysb installations. The prefix.* syntax in the list refers to everything that starts with the prefix. For example, devices.* refers to all of the file sets starting with devices.

|Minimal list of AIX 4.3.3 file |sets:

|Java.rte.*                   bos.diag.*
|X11.apps.*                   bos.html.en_US.topnav.*
|X11.base.*                   bos.mp.*
|X11.compat.*                 bos.net.*
|X11.Dt.*                     bos.powermgt.*
|X11.fnt.*                    bos.rte.*
|X11.loc.*                    bos.sysmgt.*
|X11.motif.*                  bos.terminfo.*
|X11.vsm.*                    bos.up.*
|X11.msg.*                    devices.*
|bos                          perfagent
|bos.64bit.*                  perl.*
|bos.adt.*

|Minimal list of AIX 5L 5.1 file sets:

|IMNSearch.bld.*              bos.net.*
|IMMSearch.rte.*              bos.perf.*
|Java130.rte.*                bos.powermgt.*
|Tivoli_Management_Agent.*    bos.rte.*
|X11.Dt.*                     bos.svprint.*
|X11.adt.*                    bos.sysmgt.*
|X11.apps.*                   bos.terminfo.*
|X11.base.*                   bos.txt.*
|X11.compat.*                 bos.up.*
|X11.fnt.*                    devices.*
|X11.loc.*                    ifor_ls.base.*
|X11.motif.*                  invscout.ldb.*
|X11.msg.*                    invscout.rte.*
|X11.vsm.*                    perl.*
|bos                          perfagent.tools.*
|bos.64bit.*                  printers.rte.*
|bos.adt.*                    rpm.rte.*
|bos.diag.*                   rsct.*
|bos.doc*                     sysmgmt.help.msg.en_US.*
|bos.help.msg.en_US.*         sysmgmt.msg.en_US.websm.*
|bos.html.en_US.topnav.*      sysmgmt.sguide.*
|bos.iconv.*                  sysmgmt.websm.*
|bos.loc.iso.*                xlC.aix50.*
|bos.man.en_US.*              xlC.cpp.*
|bos.mp.*                     xlC.msg.en_US.cpp.*
|bos.mp64.*                   xlC.rte.*
|box.msg.en_US.*

|Additional files you may want to add to your |lppsource:

|bos.acct.*: |Required if you plan to use PSSP accounting |
|bos.cpr.*: |Required to install LoadLeveler 3.1 or Parallel Environment |3.2
|dce.*: |The DCE file sets are required only if DCE will be configured by PSSP |anywhere on the system. You will need the client portion of the DCE |file sets because the installation code installs the DCE client code. |
|Java130.xml4j: |Required for pSeries 690 servers |
|CIMOM: |Copy from the AIX toolbox for Linux applications CD. It is labeled |in the Contents as openCIMOM, with the file name of |Rpms/noarch/openCIMOM-0.61-1.aix5.1.noarch.rpm

Notes:

Refer to your disk usage planning in the "Combining the space requirements" section of RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment to determine if you have allocated enough space to accomplish this task.
Allow at least 1-3 hours for moving all the file sets from media to disk.

|To copy the AIX LP images, login to the control workstation as root |and run bffcreate using SMIT or the command line. The |following example shows the product media on cd0 and the selection of |all LPs. Using all may load unnecessary file sets into the |directory.

bffcreate -qvX -t/spdata/sys1/install/name/lppsource -d /dev/cd0 all

The following warning message is issued--ignore it:

bffcreate:
Warning: important size information is missing from
the table of contents file.  Consequently, there may not
be enough free file system space to successfully create
the bff image(s).  Continuing anyway...

If you choose not to use bffcreate, you need to run the inutoc script as follows:

cd /spdata/sys1/install/name/lppsource
 
inutoc .

|Step 15: Copy the Correct level of PAIDE

| |

|The perfagent.server file set is part of the Performance Aide for |AIX (PAIDE) feature of the Performance Toolbox for AIX (PTX), a separate |product. This product provides the capability to monitor your SP |system's performance, collects and displays statistical data for SP |hardware and software, and simplifies runtime performance monitoring of a |large number of nodes.

|The Performance Toolbox for AIX, Agent Component (PAIDE) is |required. The correct level of AIX PAIDE (perfagent.tools) needs |to be installed on the control workstation and copied to all of the lppsource |directories. The perfagent.tools file set is part of AIX |4.3.3 and AIX 5L 5.1.

|The required level of perfagent is dependent upon the level of AIX and PSSP |as shown in the following table:
|

|Table 3. perfagent File Sets

AIX Level PSSP Level Required File Sets
AIX 4.2.1 PSSP 2.4 perfagent.server 2.2.1.x, where x is greater than or equal to 2
AIX 4.3.3 PSSP 2.4 perfagent.server 2.2.33.*
AIX 4.3.3 PSSP 3.1.1 perfagent.tools 2.2.33.*
AIX 4.3.3 PSSP 3.2 perfagent.tools 2.2.33.*
AIX 4.3.3 PSSP 3.4 perfagent.tools 2.2.33.*
AIX 5L 5.1 PSSP 3.4 perfagent.tools 5.1.0.*

AIX Level	PSSP Level	Required File Sets
AIX 4.2.1	PSSP 2.4	perfagent.server 2.2.1.x, where `x` is greater than or equal to 2
AIX 4.3.3	PSSP 2.4	perfagent.server 2.2.33.*
AIX 4.3.3	PSSP 3.1.1	perfagent.tools 2.2.33.*
AIX 4.3.3	PSSP 3.2	perfagent.tools 2.2.33.*
AIX 4.3.3	PSSP 3.4	perfagent.tools 2.2.33.*
AIX 5L 5.1	PSSP 3.4	perfagent.tools 5.1.0.*

|Verify that your lppsource contains the correct level of PAIDE.

|Refer to the READ THIS FIRST document for the latest information |on PAIDE levels.

|Note that important PTFs for perfagent.server are distributed on the |AIX Update CD-ROM. The level of PAIDE copied to each lppsource |directory must match the level of AIX in that directory.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]