pSeries 690 servers.
When you add a frame, SP-attached server, or a clustered enterprise server to your RS/6000 SP system, you should plan how it fits into your network configuration. Consider the number of new nodes and how many interfaces they will have when planning your network configuration. Record this information in your SP configuration worksheets, located in the RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment. Both the RS/6000 SP: Planning, Volume 1, Hardware and Physical Environment and the RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment offer information to help you with these decisions. For clustered enterprise servers, there are also planning issues that you must consider if you will be adding an SP frame |or switch sometime in the future.
IBM suggests that you add frames only to the end of your system, otherwise you may have to reconfigure the System Data Repository (SDR).
After you plan the configuration, follow these steps to add the frame and its nodes to your RS/6000 SP system, referring to your worksheets as necessary. Many steps include a reference to a previous chapter for more detailed information on the steps that you will be performing.
|Frames that will never contain nodes, such as SP expansion I/O units |or switch-only frames, can be added with frame numbers greater than |128.
See the section on using RS/6000 SP authentication services in the PSSP: Administration Guide for more information.
Before reconfiguring your system, you should back up the SDR by issuing:
SDRArchive
Note the location and the name of the file created after you issue this command.
If your existing system has multiple partitions defined and you want to add a frame that has a switch, you need to bring the system down to one partition before you can add the additional frame.
See the "Managing system partitions" chapter in the PSSP: Administration Guide for instructions on partitioning your SP system.
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.
|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 two serial ports. For example, if you have |two SP frames and one SP-attached server, configure four tty terminals. |Refer to Step 1.4: Verify the control workstation serial ports for valid tty port values.
|Enter a command similar to the following to define and configure an |RS-232 line for parent adapter sa0 on serial port 1:
mkdev -c tty -t tty -s rs232 -p sa0 -w 1
The following example configures a second port of a two-frame system:
mkdev -c tty -t tty -s rs232 -p sa1 -w 2
Use SMIT or the chdev command to configure each Ethernet adapter connecting |the nodes on your frames to the control workstation. For example, enter a command similar to the following to configure an |SP Ethernet administrative LAN adapter:
chdev -l en0 -a netaddr=129.33.41.1 -a netmask=255.255.255.0 -a state=up
For details on the correct use of chdev, see the 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. For example, enter a command similar to the following to define and configure 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 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.
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
|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: |
|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 8: 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.
Enter information about your frames using Perspectives, SMIT, or the spframe command. |You must be an authenticated administrative user to issue this |command.
Specify the spframe command with -r yes to reinitialize the SDR (when running the command for the 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
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.
|In PSSP 3.4, you can install multiple NSBs in an SP frame. A |multiple NSB frame can contain switches only 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.
|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 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 you entered SP or multiple NSB frame information in Step 7: 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.
|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.
|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/tty6
|Append the following to the /etc/switch.info |file:
|7,1 12 |7,2 13 |7,3 14 |7,4 15
|To define the third server to PSSP and reinitialize the SDR, |enter:
|spframe -r yes -p HSC -d huntley -i 129.33.32.121 7
All frames must be powered up and connected to the control workstation so that the nodes are automatically detected and added to the SDR.
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.
Proceed to the Adding nodes section to complete the installation of your system.