×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Troubleshooting

Here is how to add a pSeries Regatta LPAR to an existing SP by bjverzal
Posted: 17 Jan 03

This document will indicate the steps for adding a server into an existing SP environment.  These steps assume the following:

1.    The person doing these steps has some understanding of how an SP works
2.    The LPAR has already been loaded with AIX
3.    The information in Appendix A has been filled out.
4.    The person doing these steps has some understanding of how a Regatta Series server works
5.    The LPAR has a configured management Ethernet interface on the ôreliable Ethernetö network, usually  ôen0.ö  Consult Appendix B to perform this step.
6.    The LPAR has at bos.net.nfs.client loaded (lslpp ûl bos.net.nfs.client)
7.    The LPAR has been added into the SDR via ôsmitty enter_dataö.  If this step has not been done, proceed to Appendix C, then continue below with ôBeginö.

Begin:

A.  Determine what the IP Address and subnet mask will be on the ôreliable Ethernetö segment of this
server.  See Appendix A for this information.
B.    telnet to the node
C.    ftp the file ô/etc/SDR_dest_infoö from the control workstation to the node.  Verify the permissions of this file are the same on the server as the control workstation.
D.    Verify that perfagent.tools is installed (lslpp ûl perfagent.tools).  If it is not installed, you must install it at this time.
E.    mkdir /mnt
F.    mkdir /mnt2
G.    Add the IP address and hostname for the control workstation to /etc/hosts on the node(s).
H.    Mount via NFS, the directory ô/spdata/sys1/install/pssplppö to ô/mntö from the control workstation.
I.    Mount via NFS, the directory ô/spdata/sys1/install/aix510/lppsourceö to ô/mnt2ö from the control workstation
J.    cd /mnt2/installp/ppc
K.    Install the following filesets:

vacpp.ioc.aix50.rte (IBM Open Class Library AIX 5.0 Application Runtime)
vacpp.ioc.aix50.lib (IBM Open Class Library AIX 5.0 Static Libraries)
vacpp.ioc.rte (IBM Open Class Library Application Runtime)

L.    cd /mnt/version-number (cd /mnt/PSSP-3.4, for example)
M.    Install the following fileset(s):
ssp.basic (SP System Support Package).  It is contained in the ôpssp.installpö ôbffö.
N.    Unmount /mnt and /mnt2
O.    On the node, run the script ô/usr/lpp/ssp/install/bin/pssp_scriptö.  This step will configure the SP environment on the node and also configure the control workstation properly for this node.  This step may take a few minutes.  If the prompt returns right away, there is a configuration error of some sort.  The pssp_script will display a log file name.  Look in that log file for the error specifics.  If the error log is not there, there are no errors and everything should have worked.  If the prompt does not return right away, the pssp_script is working and configuring the SP environment on the node.
P.    Reboot the node via ôshutdown ûFrö
Q.    When the node comes back up, the control workstation should show a ôhost respondsö of ôyesö for this node:

spcws02:/spdata/sys1/install/aix510/lppsource/installp/ppc >spmon -d
1.  Checking server process
   Process 19888 has accumulated 0 minutes and 56 seconds.
   Check successful

2.  Opening connection to server
   Connection opened
   Check successful

3.  Querying frame(s)
   1 frame
   Check successful

4.  Checking frames

   This step was skipped because the -G flag was omitted.

5.  Checking nodes
----------------------------------- Frame 1 ----------------------------------
                      Host     Switch   Key     Env   Front Panel      LCD/LED
Slot Node Type  Power Responds Responds Switch  Error LCD/LED          Flashes
---- ---- ----- ----- -------- -------- ------- ----- ---------------- -------
 1     1  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A
 2     2  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A
 3     3  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A
 4     4  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A
 5     5  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A
 6     6  thin   on     yes    noconn    N/A    N/A  LCDs are blank     N/A

    A ôHost Respondsö of ôyesö indicates that the ôhardmonö daemons are communicating from the node to the control workstation.  If this is not the case, follow standard SP troubleshooting procedures for an SP problem.

Once all steps are done and the system is rebooted, add the new node(s) to $WCOLL, then on the Control Workstation, run the following command:

    # /usr/lpp/ssp/bin/updauthfiles

This command will update authorization across the SP Complex and allow for trusted rcmd execution and rsh.  You are now done.
 
Appendix A.

Fill in the following fields:

I.    Starting Node IP Address: _____._____._____._____
II.    Node Subnet Mask: _____._____._____._____
III.    Default Route: _____._____._____._____
    IV.    Node Name(s):  __________________________________________________________
    V.    Start Frame: _________
    VI.    Start Slot/Node Number (LPAR # of first LPAR you are working on): ________
    VII.    Number of Nodes/LPARs you are working on (Node Count): ________
 
Appendix B.

For a Regatta LPAR:

B1.    Log into the HMC and open up a serial console for the LPAR.
B2.    Configure the ôreliable Ethernetö IP information as defined in step Appendix A above into Ethernet interface ôen0ö.
B3.    Close the serial console.
B4.    Add the IP address and hostname for the node(s) to /etc/hosts on the control workstation, if not already present

 
Appendix C.

Italic Text is typed
Bold Text are selected options
    
Entering the LPAR into the SDR.

A.    Log into the Control workstation
B.    # smitty enter_data
C.    Select Node Database Information
D.    Be sure the serial console is closed, or the next several commands will fail.
E.    Select Get Adapter Physical Location Information (pSeries 670/690 Only)
Note: This will power off the node
Note 2: This step will run for a while
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
When the screen returns, continue.
F.    Select SP Ethernet Information
Follow the on-screen instruction as to which fields to fill.
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
Generally, fill in item ôDö on the screen with ôen0ö
Fill in the final fields as shown below, but replace the IP address and default route with the real information:

* Starting Node's IP Address or Hostname             [10.129.33.11] (Step I of Appendix A)
* Netmask                                            [255.255.255.0] (Step II of Appendix A)
* Default Route Hostname or IP Address               [10.129.33.254] (Step III of Appendix A)
 Ethernet Adapter Type                               tp
 Duplex                                              
 Ethernet Speed                                      auto
 Skip IP Addresses for Unused Slots?                 No

G.    Select Get Hardware Ethernet Addresses
Note: This will power off the node
Note 2: This step will run for a while
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
H.    Select Hostname Information
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
Fill in step ôDö on the screen.  Enter ôen0ö unless otherwise specified.
I.    Select Change Volume Group Information
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
Enter ôrootvgö for Volume Group Name
Enter ôhdisk0ö for Physical Volume List
Enter ôbos.obj.ssp.51ö for Network Install Image Name
Enter ôaix510ö for LPP Source Name
Press ENTER to submit the screen.
J.    Select Boot/Install Server Information
Put the SP frame number in the Start Frame entry box (Appendix A, step V)
Put the Node Number for the node(s) you are working on in the Start Slot entry box (Appendix A, step VI)
Put the number of nodes you are working on in the Node Count entry box. (Appendix A, step VII)
Change Response from Server to bootp Request to ôcustomizeö
Select ôrootvgö as Volume Group Name
Change Run setup_server? to ônoö if there are more servers to change, or leave it at yes if this is the last server you are configuring.
K.    If setup_server exits with ô(rc=0)ö, you are done.  If not, you must find out what is wrong and correct it, then re-run setup_server.
L.    Now, power on the node(s) with the following command:
spmon ûp on node# (where # is the number of the node(s), one at a time.)
Wait for the node to respond to a ôpingö before continuing.
M.    Return to Begin.

Back to IBM: AIX FAQ Index
Back to IBM: AIX Forum

My Archive

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close