Follow the steps in this section if you are upgrading your control workstation. |Supported starting points for the control workstation migration |include:
Depending on the current level of AIX and PSSP installed on the control workstation, you may first need to migrate to a new level of AIX.
If you have an HACWS configuration, proceed to HACWS migration strategy.
|To migrate to a new PSSP level without changing your AIX level, |perform Step 2: Quiesce your system and Step 13: Copy the PSSP images for PSSP 3.4 through Step 31: Validate the control workstation.
Keep in mind that you should always make a mksysb backup of your control workstation and a backup of the /spdata directory before proceeding with the migration process. For information on making a mksysb, refer to Step 10: Back up your control workstation.
| Restricted Root Access |
|---|
|
As of PSSP 3.2, you have the option of running your SP system with an enhanced level of security. With the restricted root access (RRA) option enabled, PSSP does not internally issue rsh and rcp commands as a root user from a node. Also, PSSP does not automatically grant authorization for a root user to issue rsh and rcp commands from a node. If you enable this option, some procedures might not work as documented. For example, to run HACMP, an administrator must grant the authorizations for a root user to issue rsh and rcp commands that PSSP otherwise grants automatically. See the "Planning for security" chapter in RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment for a description of this function and a complete list of limitations. |
Before beginning, refer to Preparing to migrate for information on preparing to migrate and verifying control workstation and system requirements.
|Be sure to quiesce your system as follows: |
You need to upgrade the control workstation to the target AIX level (AIX 4.3.3). Determine which of the following methods you want to follow based upon the information described at the beginning of this chapter:
Your control workstation may already be at AIX 4.3.3. You should issue the installp commands to install the new AIX 4.3.3 PTFs or file sets on top of the current AIX level to preserve the current files in the / (root), /var, /usr, and user-based file systems. To perform this operation, do Step 3a: Upgrade.
The control workstation is currently at an earlier version or release of your target AIX level. For example, your control workstation is at AIX 4.2.1 and your target AIX level is 4.3.3. Use this method to preserve the current files in the / (root), /var, /usr, and user-based file systems. To perform this operation, do Step 3b: Perform control workstation BOS migration install.
Applying PTFs for the control workstation allows the current rootvg file systems to be preserved. This activity provides installp updates and installs necessary AIX LPs to the control workstation. You must have all the necessary AIX file sets and PTFs listed in the READ THIS FIRST document available during this PTF upgrade. You will issue the installp command where the input source can be a CD-ROM or a directory (lppsource) that contains the PTFs or file sets. Using the directory requires you to use the bffcreate command to copy the AIX 4.3.3 PTFs or file sets into the lppsource directory. |Beware that the AIX update CD may contain PTFs for several levels of |AIX. You need only to copy the PTFs pertaining to the levels of AIX |installed on your system.
To create a list of LPs on the control workstation, issue:
lslpp -l -J >/tmp/FILE.43
To install and apply PTF service from a |CD-ROM and commit LPs, issue:
|installp -acNgd /dev/cd0 -f /tmp/FILE.43
Notes:
stopsrc -s supfilesrv
Once service is applied, issue the following command on the control workstation to restart the supper daemon:
startsrc -s supfilesrv
After completing this step, proceed to Step 4: Verify AIX levels.
| Attention |
|---|
|
You cannot migrate to AIX 5L 5.1 at this point. You must complete the migration to PSSP 3.4 before migrating to AIX 5L 5.1. |
This method preserves all file systems except /tmp, as well as the root volume group, logical volumes, and system configuration files. This activity provides installp updates and installs necessary AIX LPs to the control workstation. You must have all the necessary AIX file sets and PTFs listed in the READ THIS FIRST document available by CD-ROM or from the NIM master.
A migration install from CD-ROM is an interactive process. You will be prompted to verify settings, continue the installation, and verify the migration.
Refer to the AIX Installation Guide in chapters 1-3 for more information. The following list provides some hints:
After completing this step, proceed to Step 4: Verify AIX levels.
Verify that the control workstation was successfully migrated to your target AIX level (AIX 4.3.3), by issuing the the following command:
oslevel
For example, if your target AIX level is 4.3.3 and the output of this command does not indicate AIX 4.3.3, issue the following command to return a list of AIX files not migrated to AIX 4.3.3. You may need to install AIX PTFs to migrate those file sets to AIX 4.3.3.
oslevel -l 4.3.3.0
Before rebooting the control workstation, become familiar with "Tips for installing DCE on the SP" in Step 22: Configure DCE for the control workstation (required for DCE). If you plan to configure DCE after completing your migration, you may want to establish these environment variables now before rebooting.
If you just upgraded your control workstation (an AIX modification level change, for example, AIX 4.3.2 to 4.3.3,) you now need to reboot the control workstation so changes to the kernel will take effect.
|An authentication method must be set in order for remote commands to |work properly. If your SP system contains nodes at PSSP |3.1.1 or earlier, the Kerberos V4 value must be set. For |SP systems containing nodes at PSSP 3.2 or later, any value is valid |(Kerberos V5, Kerberos V4, or Standard AIX).
|Issue the lsauthent command to determine if an |authentication method is set. If the value is not set, use the |chauthent command to enable Kerberos V4 or Standard AIX. |Issue:
chauthent -k4 -std
Verify the configuration for each Ethernet adapter in the control workstation.
You can verify each Ethernet adapter by pinging its IP address and seeing if you get a response. For example:
ping -c 1 129.33.34.1
Reconfigure the adapter if you did not receive a response.
When you first install your system, the number of processes the root user can have is set to an AIX default. You cannot continue installing your system with this default value--you must increase the number to 256.
To check the current value, enter the following command:
lsattr -l sys0 -E | grep maxuproc
To change the value, enter the following command:
chdev -l sys0 -a maxuproc='256'
To validate the network tunables on the control workstation, use the no command to view and change the network values. To list the values, enter:
/usr/sbin/no -a
To change the value of tcp_mssdflt, enter:
/usr/sbin/no -o tcp_mssdflt=1448
The following list provides the PSSP defaults to use:
sb_max 163840 ipforwarding 1 tcp_sendspace 65536 tcp_recvspace 65536 udp_sendspace 32768 udp_recvspace 65536 tcp_mssdflt 1448 tcp_pmtu_discover 0 udp_pmtu_discover 0
You need to update the /etc/rc.net file so that these changes will take affect.
If your system is partitioned, first verify that the aliases for each of your system partitions are still defined in /etc/rc.net. Then, verify that the aliases are still defined by issuing the following command:
netstat -in
If the aliases are no longer defined due to the AIX migration, they must be redefined before continuing with your PSSP migration. To do this, edit the /etc/rc.net file looking for the template provided for changing the inet0 to an alias. Follow the instructions in the template and edit the file to define alias IP addresses and names. For example:
/usr/sbin/ifconfig tr0 alias 129.40.127.101 netmask 255.255.255.0 up \ >>$logfile 2>&1
After editing the /etc/rc.net file, make sure it has execute permission, then either execute the rc.net script or enter the following ifconfig command:
ifconfig tr0 alias 129.40.127.101 netmask 255.255.255.0 up
For complete details on how to create aliases for your system partitions, refer to the section on what you need to do before you define system partitions in the "Managing system partitions" chapter in the PSSP: Administration Guide.
Before creating a PSSP 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.
If any nonroot volume groups were exported in Step 10: Back up your control workstation, you will need to import these volume groups now. For example, to import the spdatavg volume group, issue the following command:
importvg -y spdatavg -V major # hdisk
The /spdata directory contains mksysb images and installp file sets. IBM suggests you create a separate volume group for the /spdata file system. These file sets are large and need much space (up to 2 GB per lppsource level supported). 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.
You need to create the proper PSSP directory structure for |PSSP 3.4.
You must create subdirectories on the /spdata file system for storing critical PSSP data. Make sure the directories have the permissions rwxr-sr-x. Issue the following commands to create the required directories:
mkdir -p /spdata/sys1/install/name/lppsource
This is the subdirectory for the required AIX 4.3.3 file sets. You can choose any name, but the name must not contain any dots (.). If you have multiple lppsources, you should pick more than one name. By default, this is set up as the string "default". You might want to pick a more meaningful name, such as aix433 for AIX 4.3.3 level code. If the control workstation will be the NIM server for different levels of AIX, you should create one subdirectory for each level of AIX.
|mkdir /spdata/sys1/install/pssplpp/PSSP-3.4
|This is the location of installp file sets for the code version |PSSP-3.4. If the control workstation will be a NIM server for |nodes at other PSSP levels, also create subdirectories under pssplpp with the |code versions for those levels (PSSP-2.4, PSSP-3.1.1, |PSSP-3.2).
If you have not done so already, you must now copy the AIX file sets into the /spdata/sys1/install/name/lppsource directory on your hard disk on the control workstation.
|You can download all of the AIX file sets (a very large number) or |only the minimal required AIX file sets (approximately 500 MB).
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.*
|Additional files you may want to add to your |lppsource:
Notes:
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. Note that important PTFs for perfagent.server are distributed on the AIX Update CD-ROM. The perfagent.tools file set is part of AIX 4.3.3.
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 perfagent.server or perfagent.tools file sets must also be copied to all of the lppsource directories on the control workstation. The level of PAIDE copied to each lppsource directory must match the level of AIX in that directory.
The required level of perfagent is dependent upon the level of AIX and PSSP
as shown in the following table:
|
| 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.x |
| AIX 5L 5.1 | PSSP 3.4 | perfagent.tools 5.1.0.* |
Refer to the READ THIS FIRST document for the latest information on PAIDE levels.
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 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...
The Performance Toolbox for AIX, Agent Component (PAIDE) is required. The correct level of AIX PAIDE (perfagent) needs to be installed on the control workstation and copied to all of the lppsource directories. The level of perfagent required is dependent upon the level of AIX. |For example, issue:
installp -aXd /spdata/sys1/install/name/lppsource perfagent.tools
The RS/6000 SP package consists of several file sets that must be copied into the |/spdata/sys1/install/pssplpp/PSSP-3.4 directory using the bffcreate command. After copying the file sets, rename the PSSP and RSCT file sets and create the .toc file:
|bffcreate -qvX -t /spdata/sys1/install/pssplpp/PSSP-3.4 -d /dev/cd0 all |cd /spdata/sys1/install/pssplpp/PSSP-3.4 |mv ssp.3.4.0.0.I pssp.installp |mv rsct.basic.1.2.1.0.I rsct.basic |mv rsct.clients.1.2.1.0.I rsct.clients |mv rsct.core.1.2.1.0.I rsct.core |inutoc .
|At this point, copy PSSP prerequisites to your AIX |4.3.3 lppsource. Issue:
|cp xlC.rte.* /spdata/sys1/install/name/lppsource |cp xlC.aix43.* /spdata/sys1/install/name/lppsource |cp ipfx.* /spdata/sys1/install/name/lppsource |cp vacpp.ioc.* /spdata/sys1/install/name/lppsource |cp vacpp.cmp.* /spdata/sys1/install/name/lppsource |cd /spdata/sys1/install/name/lppsource |inutoc .
Refer to Step 16: Copy the PSSP images for more information.
|PSSP 3.4 has prerequisites for |vacpp.ioc.aix43.rte 5.0.2.0 and |xlC.aix43.rte 5.0.2.0. These files |and their associated prerequisites were moved to your AIX 4.3.3 |lppsource /spdata/sys1/install/name/lppsource |during Step 13: Copy the PSSP images for PSSP 3.4.
|If your control workstation or nodes have parts of the xlC or vacpp |products installed other than the files moved in Step 13: Copy the PSSP images for PSSP 3.4, your AIX lppsource must contain the files you have |installed at the levels corresponding to the levels of the files shipped with |PSSP or the files must be migrated before the control workstation or nodes are |migrated. To determine the installed files do:
|lslpp -L | grep xlC |lslpp -L | grep vacpp
|If the output shows installed files different from the ones moved in |Step 13: Copy the PSSP images for PSSP 3.4, you must obtain the maintenance corresponding to the files |shipped with PSSP. Maintenance can be obtained from:
|http://techsupport.services.ibm.com/rs6k/fixdb.html
|The PSSP prerequisite files must be in your AIX lppsource. |However, it is suggested that you place the maintenance in a directory other |than your AIX lppsource and install the maintenance on both the control |workstation and the nodes before beginning a migration.
|To install only PSSP prerequisite runtime files, enter:
|installp -agXd /spdata/sys1/install/name/lppsource xlC.rte \ | xlC.aix43.rte vacpp.ioc.aix43.rte
|Alternatively, use SMIT or the installp command to install |the maintenance from your own directory.
The RS/6000 SP media provides a basic AIX minimal image for each level of AIX that |PSSP 3.4 is supported on. You need to properly load in the AIX mksysb image to the /spdata/sys1/install/images directory using the installp command. For example, to install the AIX 4.3.3 minimal images, issue the following command:
|installp -aXd /dev/cd0 spimg.433
Refer to Step 17: Copy a basic AIX (mksysb) image for more information.
Refer to the following table for the commands to issue to stop the daemons
from running on the control workstation. You must stop the daemons in
the order that they are presented in this table.
| To stop this daemon: | Issue this command: |
|---|---|
| RSCT daemons |
syspar_ctrl -G -k |
| sysctld daemon |
stopsrc -s sysctld |
| splogd daemon |
stopsrc -s splogd |
| hardmon daemon |
stopsrc -s hardmon |
| sdrd daemons |
stopsrc -g sdr |
Issue the lssrc -a command to verify that the daemons are no longer running on the control workstation. The SRC objects in the table should now have a status of inoperative with no active process ID (PID).
|If DCE or Kerberos V4 was enabled in Step 23: Set the authentication method for SP Trusted Services on the control workstation, you must obtain credentials using dce_login or |k4init. If DCE was selected, you should dce_login to |the SP administrative principal created in Step 22.3: Create SP administrative principals. If Kerberos V4 was selected, you should use the |appropriate administrative principal created in Step 21: Initialize RS/6000 SP Kerberos V4 (optional).
You now need to install the |PSSP 3.4 level code on the control workstation. The |PSSP 3.4 file sets are packaged to be installed on top of previously-supported releases. If in the original installation of PSSP on the control workstation, all of the file sets available in the |PSSP 3.4 package were installed, you should install all of them in this step also. For example, to install all of the file sets, enter:
|installp -aXd /spdata/sys1/install/pssplpp/PSSP-3.4 all
If in the original installation, optional file sets were omitted, you can omit them in this step. For more information, refer to Step 19: Install PSSP on the control workstation.
You can use installp to install multiple file sets. For example:
|installp -a -g -d /spdata/sys1/install/pssplpp/PSSP-3.4 -X ssp rsct
|If your starting PSSP level is earlier than PSSP 3.2, the |authentication method for SP Trusted Services may not have been set. To |determine if the authentication method was previously set, issue the |lsauthts command. If the response is a value of |compat or dce, you can skip this step. If the |authentication method for SP Trusted Services is not set to compat |and you are migrating from a version of PSSP earlier than PSSP 3.2, |issue the chauthts command. Issue:
chauthts compat
To properly set up the |PSSP 3.4 control workstation for the SDR, Hardmon, and other SP-related services, issue the following command:
install_cw
The install_cw command runs SDR_init which logs information in /var/adm/SPlogs/SDR/SDR_config.log.
For more information, see Step 25: Complete system support installation on the control workstation.
Use the splstdata command to verify the authentication values for auth_install, auth_root_rcmd, ts_auth_methods, and auth_methods.
splstdata -p
|Notes:
|auth_install k4 |auth_root_rcmd k4 |ts_auth_methods compat |auth_methods k4:std
Run verification tests that check for correct installation of the SDR, the System Monitor, and correct configuration of the System Monitor.
SDR_test (SDR verification) spmon_itest (SP mon verification)
You must ensure that the AIX level on the LP source (indicated by the cw_lppsource_name) matches the AIX level installed on your control workstation. To change any of the site environments, issue the spsitenv command:
spsitenv cw_lppsource_name=name
The system management environments on the control workstation are started by running services_config. Issue the following command:
/usr/lpp/ssp/install/bin/services_config
Check which supervisors need to be updated by issuing:
spsvrmgr -G -r status all
If action is required, update the microcode by issuing:
spsvrmgr -G -u frame_number:slot_number
You can update all of the microcode at once by issuing:
spsvrmgr -G -u all
For more information, see Step 34: Update the state of the supervisor microcode.
There are |RSCT subsystems that you need to add to the system. Even if you are not partitioning your system, you need to do this since you still have one default partition. Do the following:
syspar_ctrl -c -G
syspar_ctrl -A -G
|Issue /usr/sbin/rsct/bin/haemctrl -k on the control workstation |and on each of the nodes in the system partition. For PSSP 2.4 |or earlier, issue /usr/lpp/ssp/bin/haemctrl -k on the control |workstation and on each of the nodes in the system partition.
|You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in PSSP: Administration Guide.
|On the control workstation, issue the lssrc -s |haem.domain_name command. On the nodes, issue the |lssrc -s haem command.
|You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in the PSSP: Administration Guide.
|The status of each daemon should indicate that it is inactive.
|Issue /usr/sbin/rsct/bin/haemctrl -s on the control workstation |and on each of the nodes in the system partition. For PSSP 2.4 |or earlier, issue /usr/lpp/ssp/bin/haemctrl -s on the control |workstation and on each of the nodes in the system partition.
|You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in PSSP: Administration Guide. |
To verify that the system-partition sensitive subsystems have been properly started, refer to Step 56: Verify that RSCT subsystems have started.
|This step is only required when migrating the control workstation |from PSSP 2.4.
The pmand daemons out on the nodes need to be stopped and restarted in order to recognize changes that were made to the SDR in Step 20: Complete PSSP installation on the control workstation. You can accomplish this by running the following commands:
dsh -avG stopsrc -s pman dsh -avG startsrc -s pman
Any of the applications that you quiesced prior to migrating your control workstation should be started now if they have not already been automatically started. If you have an SP Switch, for each system partition issue the following command to restart your SP Switch:
Estart
You should validate that the |PSSP 3.4 software has been properly installed on the control workstation by issuing the following commands:
SYSMAN_test
spmon_ctest
CSS_test * run only if you have a switch
spverify_config * run only if your system is partitioned
st_verify * run only if Job Switch Resource Table Services
is installed
Verify that host_responds and switch_responds , if you have a switch, are set to yes by issuing the following command:
spmon -d -G
Using the spgetdesc command, you can obtain description information from the nodes and place it in the SDR for use by Perspectives and other applications. The spgetdesc command requires the nodes to be up in order to obtain the information from the node.
To obtain descriptions for all nodes and place it in the SDR, issue:
spgetdesc -au
If any nodes are not up when you run the spgetdesc command, you can reissue the command when those nodes are up by specifying a node list. For example:
spgetdesc -ul 1,3
See the spgetdesc command in the PSSP: Command and Technical Reference for more information.
If you are migrating from a level of PSSP 2.4 or earlier, the network adapters may have to be retuned. With PSSP 3.1, there are two new attributes that must be defined; otherwise, they will be assigned default values. The two new attributes are duplex and Ethernet speed.
To view the assigned values for these attributes, from the control workstation, issue:
splstdata -a
If the values in the enet_rate and duplex columns are correct, you do not have to do anything. To change adapter attributes, |use the spadaptrs command. For a complete |description of this command, refer to PSSP: Command and Technical Reference.
Your control workstation should now function at the |PSSP 3.4 level. All nodes should now be able to communicate to the control workstation, if the proper level of PTF service has been applied to the PSSP nodes.
There are occasions based on customer changes made to the SDR and Authentication services, that may require the PSSP nodes to be rebooted and possibly recustomized by the boot/install server (BIS) nodes.
You can now add other AIX, PSSP, and customer-owned LPs and files on to the control workstation. Be careful to make sure that older applications and LPs will work properly with the target AIX level and |PSSP 3.4.
|Software maintenance (PTFs) may now be applied to the PSSP file sets |installed on the control workstation. Refer to Installing program updates for planning considerations. Follow the instructions |in Preparing the control workstation to install the PTFs.