IBM Books

Installation and Migration Guide

|Adding an adapter to a node

| |

|This procedure can be used to logically add an adapter, also known as a |network interface card (NIC), to a previously installed SP node. This |includes Ethernet, token ring, and FDDI adapters. To configure adapters |such as ATM, ESCON, and PCA, you must configure the adapter manually on each |node.

|Step 1: Archive the SDR


|To save the current SDR attributes, run the command:


|This command saves SDR information for all system partitions.

|Step 2: Disable nodes from the switch

| |

|If any of the following conditions exit, you can skip this step: |

|If you want to bring the switch down for all nodes, issue the |Equiesce command for each system partition. If you use the |Equiesce command, you must later restart the switch by issuing the |Estart command. Issue the Estart command prior to Step 8: Verify installation settings.

|The Switch Admin Daemon will issue the Estart command under |certain circumstances, thus re-establishing switch recovery and primary node |takeover. To see if you are using the Switch Admin Daemon, issue the |following command:

|lssrc -a | grep swtadmd


|lssrc -a | grep swtadmd2

|where swtadmd is used for an SP Switch and swtadmd2 for |an SP Switch2.

|If the response returned shows that the subsystem is active, you may want |to turn off the Switch Admin Daemon before issuing the Equiesce |command. To turn off the daemon, issue the following command:

|stopsrc -s swtadmd


|stopsrc -s swtadmd2

|where swtadmd is used for an SP Switch and swtadmd2 for |an SP Switch2.

|If you are customizing a few nodes, you must disable these nodes from the |switch (if appropriate, first reassign the primary node or primary backup |node). To determine if one of the nodes you are migrating is a primary |or primary backup node, issue the Eprimary command. If you |need to reassign the primary or primary backup node, issue the |Eprimary command with appropriate options. Then issue the |Estart command to make your choices take effect. You must then |issue the Efence command to disable the nodes you are customizing |from the switch.

|Efence -G node_number node_number ... node_number

|Step 3: Shutdown the node


|The node must be powered off before the adapter can be installed. |Stop the applications, then use SP Perspectives or the cshutdown |command to shut down the node. For example, to shut down nodes 1 and |2:

|cshutdown -G -N 1 2

|Step 4: Install the new adapter

Your IBM Customer Engineer (CE) performs this step. |

|While the Customer Engineer installs the adapter, the system administrator |should proceed with the logical configuration of the adapter. DO |NOT REBOOT THE NODE until Step 11: Reboot the node, when both physical and logical changes are complete.

|Step 5: Define the adapter to the SDR


|This step creates adapter objects in the SDR for each new adapter being |added to a node. The data in the adapter objects is used during the |customization or installation steps to configure the adapters on the |nodes. You can configure the following adapters with this |procedure: |

|To configure additional adapters, for example Ethernet (en), token ring |(tr), or FDDI (fi), use smit node_data and select the Additional |Adapter Information or use the spadaptrs command. For |these adapters, you can select the Start Frame, Start Slot, Node Count, and |Node List fields, or issue the spadaptrs command.


  1. |When using the token ring (tr) adapter, you must select the Token Ring |Data Rate (4 MB, 16 MB, or autosense).

  2. |For best results with SMIT, exit and get back into the needed SMIT panel |for each different type of adapter. This clears any extraneous values |left behind in the panel.

  3. |Enter the correct value for Ethernet speed (10, 100, 1000, or auto), |Duplex (full, half, or auto), and Ethernet Adapter Type (bnc, dix, tp, fiber, |or NA), for each new Ethernet adapter on the target node. |

|The distribution of your IP addresses determines how many times you issue |the spadaptrs command. You may have to issue it more than once |if: |

|The following example adds SDR information for a tr0 (token ring adapter) |for node 1 with IP address and a netmask of |, and references the Node List |field:

|spadaptrs -l 1 -r 16 tr0

|The next example adds SDR information for a second Ethernet adapter on node |1 with a type of bnc, duplexing of half, a speed of 10MBS, an IP address of |, and a network mask of |

|spadaptrs -l 1 -t bnc -d half -f 10 en1

|To validate successful creation of adapter objects, issue the |command:

|splstdata -G -a

|and find the new objects.

|Step 6: Update DCE information for a node (required for DCE)


|You need to perform this step only if you have a new adapter on a node that |is running DCE (that is, the adapter was added after DCE was |configured). This step will create an ftp and a host |account in the DCE Registry database for each new adapter.


  1. |Login to the control workstation, and then DCE login as a DCE cell |administrator.
    This step can be performed from another host configured with a DCE client in |the same cell as the node's DCE client. |
  2. |Run the DCE command:
    |kerberos.dce -type admin -ip_name hostname_of_adapter
    This command does not require AIX root authority, but does require DCE cell |administrator authority. |

|To verify that the entries were created properly in the DCE Registry |database, issue the DCE account show command, as shown in the |following example:

|dcecp -c account show /.:/host/hostname_of_adapter -all
|dcecp -c account show /.:/ftp/hostname_of_adapter -all

|Step 7: Set node to customize


|Each node with a new adapter must be customized. Use the |spbootins commands to update the boot/install server's response |to the bootp request from the nodes. If you are customizing |nodes in more than one system partition, you must issue these commands in each |system partition. For a complete description of the flags associated |with these commands, refer to PSSP: Command and Technical |Reference.

|For example, to set the bootp response to customize for |nodes 1 and 2, issue the following command:

|spbootins -s no -r customize -l 1,2

|Step 8: Verify installation settings


|Make sure that the SDR has the appropriate installation values specified |for each of the nodes. Issue the following command to display the |values:

|splstdata -G -b

|The expected response is that nodes with new adapters should be set to |customize. All other attributes should contain the values last |used to install or customize your nodes.

|Step 9: Refresh RSCT subsystems


|The SDR has been updated to reflect the new adapters. You must now |refresh the RSCT subsystems on the control workstation and all nodes to pick |up these changes. Run syspar_ctrl on the control workstation |to refresh the subsystems on both the control workstation and on the |nodes:

|syspar_ctrl -r -G

|Step 10: Run setup_server to configure the changes


|The setup_server command must be run to properly set up NIM on the |control workstation. Use the following command:

|setup_server 2>&1 | tee /tmp/setup_server.out

|The output is saved in a log file called |/tmp/setup_server.out. If you have a node defined as a |boot/install server (BIS), you must also run setup_server on that |server node:

|dsh -w boot_install_node "/usr/lpp/ssp/bin/setup_server \
|    2>&1" | tee /tmp/setup_server.boot_install_node.out

|Step 11: Reboot the node


|Once the adapter has been physically installed in the node, the node can be |rebooted to complete the logical configuration. If you have any |boot/install servers in your system, you must customize them before |customizing their clients. Reboot the nodes to be customized by using |the cstartup command:

|cstartup -G -N 1 2

|The node has finished customization when the LEDs become blank, and its |host_responds value is yes.

|Verify that the bootp_response has been set to disk by |issuing the following command:

|splstdata -G -b

|Step 12: Complete the DCE configuration of the new adapter (required for DCE)

| |

|Complete the DCE configuration of the new adapter on the node. This |step can be done only after the customize has completed. Use the |following command:

|dsh -w node_name "kerberos.dce -type local"
In order for the DCE kerberos.dce command to complete |successfully, the command must be run as root on the target host, and DCE must |be running on that host. |

|To verify that the entries were created properly in the DCE self-host |(machine) key file on node_name, issue the DCE keytab show |command, as shown in the following example:

|dsh -w node_name "dcecp -c keytab show self"
This DCE command has the same requirements as the previous Note. |

|Using the hostname_of_adapter data from Step 6: Update DCE information for a node (required for DCE), scan the displayed output for ftp and |host fields that contain hostname_of_adapter.

|Step 13: Rejoin the nodes to the switch network

| |

|If you do not have a switch in your SP system, or if the node you are |adding the adapter to does not contain a switch, skip the remainder of this |step. In SP Switch2 systems, you can have some nodes on the switch and |some nodes off of the switch.

|If you disabled all nodes from the switch using the Equiesce |command, you must now issue the Estart command in each system |partition to rejoin the nodes to the switch network. If you disabled |only a few nodes using the Efence command, you must now issue the |Eunfence command to bring those nodes back to the current switch |network.

|If you stopped the Switch Admin Daemon in Step 2: Disable nodes from the switch, start it now by issuing the command:

|startsrc -s swtadmd


|startsrc -s swtadmd2

|where swtadmd is used for an SP Switch and swtadmd2 for |an SP Switch2.

|Step 14: Validate new adapter


|Verify that the new adapter is operational. Use ping or |other network commands.

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