pSeries 690 servers.
This section describes the steps you take to enter the information defining the SP configuration. After you prepare the control workstation and install the PSSP software, you are ready to enter the data to define your SP configuration.
If you changed the lppsource name to something other than the default (you would have changed the name in Step 12: Create the required /spdata directories), you must perform this step.
If you do not want to change any of the default site environment variables, skip this step and continue with Step 32: Enter SP or multiple NSB frame information and reinitialize the SDR. |To check the default site environment variables settings, issue the |following command:
splstdata -e
Use Perspectives, SMIT, or the spsitenv command to enter information about your site environment. Use the worksheet in RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment to enter site environment values.
The site environment data is written to the SDR. Before you run any of the installation scripts, you must enter the following data on the control workstation. Refer to RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment for additional explanation.
Site environment data includes:
|Refer to the "user.admin collection" section in the |"Managing file collections" chapter of PSSP: Administration |Guide for more information. |
You must ensure that the AIX level of the LP source (indicated by the cw_lppsource_name) matches the AIX level installed on your control workstation.
|The SP model number and SP serial number are used in gathering vital |product data for the SP system. Entering these values is not |required. If not entered at this time, the data will need to be |provided the first time the get_vpd command is run to collect vital |product data for the SP system.
|Restricted root access must be enabled to use the secure remote command |method. Also, the secure remote command software should be installed |and running on the control workstation before enabling on the site environment |menu. Once set in the SDR, the PSSP installation and configuration |code, and CSS commands will automatically begin to use the secure remote |commands instead of the rsh and rcp commands. Refer |to RS/6000 SP: Planning, Volume 2, Control Workstation and Software |Environment for more information.
|Three environment variables are defined so that the user can override the |SDR settings for the Remote command method, the Remote command executable, and |the Remote copy executable on any given PSSP command or script |invocation. These are also used to drive the remote command method used |by user commands such as pcp and dsh which only use these |environment variables to determine the remote command method to use.
|The environment variables are: |
RCMD_PGM=secrshell or RCMD_PGM=rsh
DSH_REMOTE_CMD=remote_command_executable
REMOTE_COPY_CMD=remote_copy_command_executable |
|To set up your system to run with the secure remote command method:
|From SMIT: |
|The following options that appear on the Site Environment Information menu |for remote command access must be modified. The following are the |defaults. |
|The default depends on the setting of the remote command method. It |is not displayed when using SMIT.
|The default depends on the setting of the remote command method. It |is not displayed when using SMIT. |
|For the root remote command access restricted option, select |true. This enables the restricted root rcmd method on the |system which is required to enable a secure remote command method.
|For the remote command method, select secrshell which will enable |the PSSP code to use the secure remote command method. If the Remote |command executable and the Remote copy executable are left blank, the |executable will default to /bin/ssh and /bin/scp. If |this is not the location of your secure remote command program, enter the full |name (including path) of the location of your secure remote command and secure |remote copy program.
|The following command can be used in place of the SMIT panels to perform |the same function:
|spsitenv restrict_root_rcmd=true,rcmd_pgm=secrshell, \ | dsh_remote_cmd=/bin/ssh,remote_copy_cmd=/bin/scp
You can enter the site environment information using Perspectives, SMIT, or
the spsitenv command. Whichever method you chose, keep in mind
that you can easily change these options at any time after installation is
complete.
| If using: | Do this: |
|---|---|
| Perspectives |
From this point, you can follow the rest of the SMIT steps described in the
next row of this table.
|
| SMIT |
|
| spsitenv | This example configures NTP service as consensus and specifies that file
collection be installed.
spsitenv ntp_config=consensus filecoll_config=true This example specifies that the control workstation lppsource directory be /spdata/sys1/install/aix433/lppsource for you installation configuration. spsitenv cw_lppsource_name=aix433 |
|You must perform this step if your SP system or clustered enterprise server
|system will contain IBM pSeries 690 servers.
|The hardware control and monitor functions for the pSeries 690 server are |managed through a network connection from the control workstation to the |hardware management console (HMC) that is controlling the pSeries 690 |server. Install the HMC for your pSeries 690 server following the |instructions in pSeries 690 Installation Guide. The |following operations must be performed locally on the HMC before the pSeries |690 server is defined to PSSP. Refer to Hardware Management |Console for pSeries Operations Guide for details on performing these |operations. Review the READ THIS FIRST document that |accompanies the PSSP installation media for information on required HMC |product and PTF levels and the corresponding pSeries 690 hardware and software |product and PTF levels.
|Perform the following steps for each HMC and each pSeries 690 server: |
|If you need to change your partition settings at a later time, refer to Reconfiguring IBM e(logo)server pSeries 690 logical partitions (LPARs) for instructions on how to do this.
|The following operations must be performed on the control workstation |before entering non-SP frame information for your pSeries 690 servers. |
|ping hmc_hostname_or_ipaddr
where hmc_hostname_or_ipaddr is the host name or IP address of
|the HMC as configured on the HMC System Configuration interface in
|Step 1 of the previous section. If the command fails, review
|your network and name server configurations on both the control workstation
|and the HMC.
|/usr/lpp/ssp/bin/sphmcid hmc_hostname_or_ipaddr hmc_sysadmin_userid
where hmc_hostname_or_ipaddr is the host name or IP address of
|the HMC as configured on the HMC System Configuration interface in
|Step 1 of the previous section and hmc_sysadmin_userid is
|the system administrator user ID created on the HMC User Management
|interface in Step 2 of the previous section. You will be prompted to
|enter the password for the hmc_sysadmin_userid. You must run
|this command again anytime the password is changed for the
|hmc_sysadmin_userid.
|An example /etc/switch.info file might contain the |following entries for a pSeries 690 server that will be defined as frame 5, |with four LPARs, attached to switch 2 in the system:
|# Node_number Switch_node_number |65 16 |66 17 |67 18 |68 19If you are running your pSeries 690 server in SMP mode or will only be |defining one LPAR and it is assigned partition ID 1, you can skip this |operation and simply enter the switch node number when you enter the the other |non-SP frame information in Step 33: Enter non-SP frame information and reinitialize the SDR (optional). |
|You must perform this step at least once for each set of frames or |multiple node switch board (NSB) frames that you are adding to the |system. You do not need to reinitialize the SDR until you are entering |the last set of frames.
|SP frames containing nodes must be numbered between 1 and 128 |inclusive. This is to ensure that nodes will be numbered between 1 and |2047. Larger frame numbers, up to 250, can be used for frames that will |contain only switches or SP expansion I/O units.
This step creates frame objects in the SDR for each |SP frame in your system. At the end of this step, the SDR is reinitialized, resulting in the creation of node objects for each node attached to your frames.
You can enter information about your frames using Perspectives, SMIT, or the spframe command. You must be an authenticated administrative user to issue this command.
If frames are not contiguously numbered, repeat this step for each series
of contiguous frames. To save time, do not specify reinitialization of
the SDR until you are entering the final series of contiguous frames.
| If using: | Do this: |
|---|---|
| Perspectives |
From this point, you can follow the rest of the SMIT steps described in the
next row of this table.
|
| SMIT |
|
| spframe | Specify spframe command with -r yes to reinitialize
the SDR (when running the command for final series of frames), a starting
frame number, a frame count, and the starting frame's tty port.
The following example enters information for four frames (frame 1 to frame 4) and indicates that frame 1 is connected to /dev/tty0, frame 2 to /dev/tty1, and so on, and reinitializes the SDR. spframe -r yes 1 4 /dev/tty0 |
|In PSSP 3.4, you can install multiple NSBs in an SP frame. A |multiple NSB frame can only contain switches in slots 1 through 16. You |cannot install SP nodes in a multiple NSB frame.
|You can enter information for non-SP frames using Perspectives,
|SMIT, or the spframe command. If frames or tty ports are not
|all contiguously numbered, repeat this step for each series of contiguous
|information. To save time, do not specify the reinitialization of the
|SDR until you are entering the final series of contiguous frames.
|
| If using: | Do this: |
|---|---|
| Perspectives |
From this point, you can follow the rest of the SMIT steps described in the
next row of this table.
|
| SMIT |
|
| spframe | Specify spframe command with -r yes to reinitialize
the SDR (when running the command for final series of frames), a starting
frame number, a frame count, and the starting frame's tty port.
The following example enters information for two frames (frame 1 to frame 2) and indicates that frame 1 is connected to /dev/tty0, frame 2 to /dev/tty1, and reinitializes the SDR. spframe -r yes -m 1 2 /dev/tty0 |
|If you entered SP or multiple NSB frame information in Step 32: Enter SP or multiple NSB frame information and reinitialize the SDR, you must reinitialize the SDR before continuing |to enter frame information for non-SP frames. You must perform this |step at least once for each frame protocol of non-SP frames that you are |adding to the system.
|If you want to add an SP-attached server or clustered enterprise server
|(for example, the RS/6000 Enterprise Server Model M80 or |IBM pSeries 690) without reinstalling its software, install the rest of the new SP
|system. Once you have completed the steps, follow the steps in Chapter 6, Reconfiguring the RS/6000 SP system to integrate the new SP-attached server.
|SP-attached servers and clustered enterprise servers also require frame |objects in the SDR. These frames are referred to as non-SP frames and |one object is required for each server attached to your SP. These |objects have a non-SP hardware protocol associated with them which instructs |PSSP as to which method of hardware communications is to be used for |controlling and monitoring the node associated with this frame object. |Valid hardware protocol values of the nodes within the frame are: |
pSeries 690 servers
pSeries 660 servers (6H0, 6H1,
|6M1)
pSeries 680 servers
|The number of tty port values you must define depends on the hardware |protocol type you selected. |
|The servers that use the SAMI hardware protocol require two tty port values |to define the tty ports on the control workstation to which the serial cables |connected to the server are attached. The tty port value defines the |serial connection to the operator panel on these servers for hardware |controls. The s1 tty port value defines the connection to the serial |port on the servers for serial terminal (s1term) support.
|Switch port numbers are required on SP Switch or switchless systems for |each SP-attached server in your system. This information is available |from your Switch Configuration Worksheet. Although switch ports are not |required for |switchless or SP Switch2 clustered enterprise servers, you may want to specify a switch port |if you plan to add an SP frame sometime in the future. RS/6000 |SP: Planning, Volume 2, Control Workstation and Software |Environment explains how to fill out your worksheet and provides details |on assigning switch port numbers.
|For pSeries 690 servers in an SP Switch or switchless system, a |switch node number is required for each logical partition (LPAR). These |switch node numbers must be specified to PSSP through the |/etc/switch.info file. Manually edit the |/etc/switch.info file to include one entry for each LPAR in |the attached server. See the switch.info file in |PSSP: Command and Technical Reference for details on editing |this file.
|An example of the /etc/switch.info file might |contain the following entries for a pSeries 690 server that will be defined as |frame 5 with four LPARs attached to switch 2 in the system:
|# Node_number Switch_node_number |65 16 |66 17 |67 18 |68 19
|If you are running your pSeries 690 server in full system partition |(SMP) mode or will only be defining one LPAR and it is assigned partition ID |1, you can skip this operation. Instead just simply enter the switch |node number when you enter the other non-SP frame information later in this |step through the SMIT menu or the spframe command.
|You can enter information for non-SP frames using Perspectives, SMIT, or
|the spframe command. |If using SMIT, a different procedure is used for each hardware
|protocol. If frames, tty ports, or switch port values are not all
|contiguously numbered, repeat this step for each series of contiguous
|information. To save time, do not specify the reinitialization of the
|SDR until you are entering the final series of contiguous frames.
|
| If using: | Do this: |
|---|---|
| Perspectives |
|
| SMIT with HMC protocol |
|
| SMIT with CSP protocol |
|
| SMIT with SAMI protocol |
|
| spframe | Specify the spframe command with the -n option for each
series of contiguous non-SP frames. The -n option is not
required for switchless clustered enterprise servers or SP Switch2
systems. Specify the -r yes option when running the command
for the final series of frames. Include the starting frame number, the
number of frames, the starting tty port value, and the starting switch port
number for each invocation of the command.
The following example enters non-SP information for one S80 server (frame 5), one H80 server (frame 6), and one pSeries 690 server with four LPARs (frame 7). The first server has the following characteristics: Frame Number: 5 tty port for operator panel connection: /dev/tty4 tty port for serial terminal connection: /dev/tty5 switch port number: 10 The second server has the following characteristics: Frame Number: 6 tty port for operator panel connection: /dev/tty6 switch port number: 11 The third server has the following characteristics: Frame Number: 7 switch port number: 12, 13, 14, 15 To define the first two servers to PSSP, enter: spframe -r no -p SAMI -n 10 -s /dev/tty5 5 1 /dev/tty4 spframe -r no -p CSP -n 11 6 1 /dev/tty6Append the following to the /etc/switch.info file: 7,1 12 7,2 13 7,3 14 7,4 15To define the third server to PSSP and reinitialize the SDR, enter: spframe -r yes -p HSC -d huntley -i 129.33.32.121 7 |
|This step ensures that you have the latest level of microcode |required by the SP frames, nodes, and switches on your SP system.
| If using: | Do this: |
| Perspectives |
|
| SMIT |
Move the cursor to the RS/6000 SP Supervisor Manager heading and select the Help Key (F1). A list of hardware that supports supervisor microcode is displayed. To update all of the supervisors, SELECT Update "All" Supervisors That
Require Action. To update a subset of supervisors, SELECT Update
Selectable Supervisors That Require Action.
|
| spsvrmgr | The following command gives the status in report form of all of your
frames, nodes, and switches:
spsvrmgr -G -r status all The following command updates the microcode on the frame supervisor of frame 3: spsvrmgr -G -u 3:0 |
Perform this step to verify that the System Monitor and Perspectives have
been correctly installed.
| If using: | Do this: |
|---|---|
| Perspectives |
|
| SMIT |
|
| spmon | Enter:
spmon_ctest |
After the tests are run, the system creates a log in /var/adm/SPlogs/spmon called spmon_ctest.log.
See the section on "Diagnosing System Monitor problems" in PSSP: Diagnosis Guide if the verification test fails.
All frames must be powered up and connected to the control workstation so
that the nodes are automatically detected and added to the SDR.
| If using: | Do this: |
|---|---|
| Perspectives |
|
| spmon | Type:
spmon -d -G |
You should see the SP frames represented with thin, wide, or high nodes, depending on your configuration. If using Perspectives, SP-attached servers are shown as a unique SP-attached server icon. If using spmon -d, SP-attached servers are represented as a one node frame. |The pSeries 690 servers will be represented as one frame with one |node per LPAR within that frame. For multiple node switch board frames |and for intermediate switch board frames, you should see the SP frames |represented with switches listed in the appropriate slot |locations. If your frames are not correctly represented, you may have a hardware problem, such as a misplugged RS-232 cable. See the "Diagnosing hardware and software problems" chapter in PSSP: Diagnosis Guide for help in correcting the error. If an error occurred, the frame must be deleted, using the spdelfram command, prior to reissuing the spframe command. After updating the RS-232 connection to the frame, you should reissue the spframe command.
|If multiple IP interfaces do not map to the same host name on the starting |node and you decide to enter its host name, it must be identical to the |default host name returned by the host command for the starting node |SP Ethernet IP address. For example, if the SP Ethernet administrative |LAN adapter IP address of a node is 123.45.678.90 and |host 123.45.678.90 gives |v64n90.xen.kry.arg.com, then this host name must |be used.
This step adds IP address-related information to the node objects in the SDR. It also creates adapter objects in the SDR for the |SP Ethernet administrative LAN adapters on your nodes. This information is used during node customization and configuration.
|The default route on the node is the route it will use for its network |communications if there is no specific route to the destination. During |the boot process, this is set to the default route in the SDR. It can |be changed later on in the boot process or after the node is running, but |should not be changed permanently in the SDR. For FDDI, token ring, or |other Ethernet adapters, create the route in |firstboot.cust. The following example defines a route |for an Ethernet adapter. This example also saves the route into the |node's ODM.
|old_route_info=$($lsattr -E -l inet0 | $grep 'route *net,.*, |0, 0-9 . *' | $awk ' print $2; ' | $tail -n 1) #- |if -n "$old_route_info" ; then #- |$chdev -l inet0 -a delroute="$old_route_info" > /dev/null |2>&1 #- |fi #- |$chdev -l inet0 -a route="0,<route>"
|In order for the route to remain set after customization, also set the |route up in /etc/inittab after the line that runs |rc.sp. For the switch, set the route up in |/etc/inittab after the line that runs |rc.switch. |
Enter information about your nodes attached to each Ethernet adapter using
Perspectives, SMIT, or the |spadaptrs command.
| If using: | Do this: |
|---|---|
| Perspectives |
From this point, you can follow the rest of the SMIT steps described in the
next row of this table.
|
| SMIT |
If you have wide nodes or high nodes which each occupy multiple slots in your system, entering yes next to Skip IP Address for Unused Slots? can be useful in assigning IP addresses that correspond to the slots in the frame, with each wide node address incrementing by 2, each thin node address incrementing by 1, and each high node node incrementing by 4. You can avoid skipping IP addresses for the empty slots by entering no next to Skip IP Address for Unused Slots? In this way IP addresses are assigned consecutively for both thin and wide nodes. The distribution of your IP addresses determines how many times you perform this step. You may have to do it more than once if:
Enter the following information for each consecutive block of nodes:
If you specify nodes with a node list, you cannot specify yes for Skip IP Addresses for Unused Slots?
Starting Slot is always relative to the frame and not to the system. This means that the first slot in the second, third, and fourth frames is still slot 1 rather than slots 17, 33, and 49. For example, for the first frame you might enter: Start Frame 1 Start Slot 1 and for a second frame, you might enter: Start Frame 2 Start Slot 1 Node List is used to specify a group of node numbers separated by commas. Node numbers can be referenced for systems with more than one frame. (Node number 17 would be used for frame 2 slot 1.) For example: 1,5,7,9,15,17,19 You can also specify a file that contains a single line of data containing the node list, separated by commas. Enter the full-path name, unless the file is in your current directory. For example, if you have a list of nodes in /tmp/node_list, enter the following in the node_list field: /tmp/node_list |
| spadaptrs | This following example configures an SP Ethernet administrative LAN
adapter network of 16 nodes with IP addresses ranging from
129.33.32.1 to 129.33.32.16, a
netmask of 255.255.255.192, and a default route of
129.33.32.200 for a twisted-pair Ethernet using
auto-negotiate for the communication transfer and rate:
spadaptrs -e 129.33.32.200 -t tp -d auto -f auto 1 1 16 en0 \
129.33.32.1 255.255.255.192
The following example configures the adapter on the SP Ethernet administrative LAN adapter for the first logical partition of a pSeries 690 server. The adapter is a twisted-pair Ethernet adapter with communication transfer and rate set to auto-negotiate. The IP address is 129.33.32.65 with a netmask of 255.255.255.192. The pSeries 690 server is represented as frame 5, the node is assigned slot 1, and the adapter is located at physical location U1.9-P2-I2/E1. spadaptrs -P U1.9-P2-I2/E1 -t tp -d auto -f auto 5 1 1 en 129.33.32.65 \
255.255.255.192
|
If you are adding an extension node to your system, you may want to enter required node information now. For more information, refer to Chapter 10, Installing extension nodes.
This step gets hardware Ethernet addresses for |SP Ethernet administrative LAN adapters for your nodes, either from a file or from the nodes themselves, and puts them into the Node Objects in the SDR. That information is used to set up the /etc/bootptab files for your boot/install servers. |This step will also ping the default route set for this |node.
If you know the hardware Ethernet addresses, you can speed this process by putting the addresses in the /etc/bootptab.info file. |If you are performing this step for a pSeries 690 server, you may |already have the hardware Ethernet addresses available to you from Step 37: Enter the required node information. Create the /etc/bootptab.info file |as follows:
1 08005ABAB177 3 08005ABAAEAB 5 08005ABAB161 7 08005ABAB17A 9 02608CF53067 13 02608CF527F2 17 08005ABAB1A0 19 08005ABAB062 21 002035D34F7A 22 002035D34FE2 23 002035D34F3C 24 002035D34F70 25 002035D34E65 26 002035D34E5F 27 002035D34FE5 28 002035D34F68 29 02608CF55E6D
The /etc/bootptab.info file is not required. If you do not know your hardware Ethernet addresses, and the /etc/bootptab.info file does not exist, use sphrdwrad to access the SP node and retrieve the hardware Ethernet address for you. (This makes sphrdwrad take longer to run.)
| If using: | Do this: |
|---|---|
| Perspectives |
|
| SMIT |
|
| sphrdwrad | This example gets all hardware Ethernet addresses for an RS/6000 SP
system.
sphrdwrad 1 1 rest This example gets all hardware Ethernet addresses for the nodes specified in the node list (the -l flag): sphrdwrad -l 10,12,17 |