Turn on, reset, or reboot the system admin controller. The power on button is on the right of the system admin controller, as shown in Figure 2-1.

Figure 2-1. System Admin Controller Power On Button and DVD Drive

Prior to the SGI Tempo 1.2 release, the serial console was always used even if the admin node install itself went to the vga screen.

The new method configures the default serial console used by the system to match the console used for installation.

If the you type "serial" at the Admin dvd install prompt, the system is also configured for serial console operations after installation and the yast2-firstboot questions appear on the serial console.

If the you hit Enter at the prompt or type vga, the VGA screen is used for installation, as previously, but also, the system is configured to use VGA as the default console, thereafter.

If a you want to install to the VGA screen, but also want the serial console to be used for operations after initial installation, you should add a console= parameter to /boot/grub/menu.lst for each kernel line. This is done when the admin node boots for the first time after installation is completed. An example of this is, as follows:

kernel /boot/vmlinuz-2.6.16.46-0.12-smp root=/dev/disk/by-label/sgiroot  console=ttyS1,38400n8
splash=silent showopts

The appropriate entries were added to the inittab and /etc/security. The change, above, is the only one needed to switch the default console from VGA to serial. Likewise, to move from serial to VGA, simply remove the console= parameter, altogether.

Insert the SGI Admin Node Autoinstallation DVD in the DVD drive on the left of the system admin controller as shown in Figure 2-1.

An autoinstall message appears on your console, as follows:

SGI Admin Node Autoinstallation DVD

The first time you boot after installation, you will be prompted for
system setup questions early in the startup process.  These questions will
appear on the same console you use to install the system.

You may optionally append the "netinst" option with an nfs path to an ISO.

Cascading Dual-Boot Support:
install_slot=: install to a specific root slot, default 1
re_partition_with_slots=: re-partition with number of slot positions, up to 5.
default is 2. Reminder: applies to the whole cluster, not just admin node
destructive=1: allow slots with existing filesystems to be re-created
or signify ok to re-partition non-blank disks for re_partition_with_slots=

You may install from the vga screen or from the serial console.
The default system console will match the console you used for
installation. Type "vga" for the vga screen or "serial" for serial.
Append any additional parameters after "vga" or "serial".
EXAMPLE: vga re_partition_with_slots=3 netinst=server:/mntpoint/admin.iso

---

Note: If you want to use the serial console, enter serial at the boot: prompt, otherwise, output for the install procedure goes to VGA screen.

---

It is important to note that the command line arguments you supply to the boot prompt will have implications for your entire cluster including things such as how many root slots are available, and which root slot to install to. Please read “Cascading Dual-Boot” before you install the admin node so you are prepared for these crucial decisions.

You can hit the ENTER button at the boot prompt. The boot initrd.image executes, the hard drive is patitioned creating a swap area and a root file system, the Linux operating system and the cluster manager software is installed and a repository is set up for the rack leader controller, service node, and compute node software RPMs.

---

Note: When you boot the admin install DVD and choose to repartition an existing disk, all data is lost. If you are making use of cascading dual-boot (see “Cascading Dual-Boot”) and are reinstalling a given slot, the data in that slot will be deleted but the other slots will not be modified.

---

Once installation of software on the system admin controller is complete, remove the DVD from the DVD drive.

Once the system has been installed, enter the reboot command to reboot your system.

---

Note: The output will go to the VGA screen unless you used serial for the admin install DVD earlier.

---

You will see messages about the system admin controller booting the kernel. You can ignore any messages about a few services that may fail to start.

---

Note: If you used the serial console for installation ( serial is not the default), the console output and configuration questions from yast2 firstboot will go to the serial port. Pressing Ctrl -l will re-draw the yast2 firstboot screen when you are using the serial console.

---

After the reboot completes, the YaST first boot installation tool starts and a Welcome screen appears, as shown in Figure 2-2. Click on the Next button to proceed.

---

Note: The YaST Installation Tool has a main menu with sub-menus. You will be redirected back to the main menu, at various times, as you follow the steps in this procedure.

---

Figure 2-2. YaST Welcome Screen

You will be prompted by YaST firstboot installer to enter your system details including the root password, network configuration, time zone, and so on.

From the Hostname and Name Server Configuration screen, as shown in Figure 2-3, enter the hostname and domain name of your system in the appropriate fields. Make sure that Change Hostname via DHCP is unselected (no x should appear in the box). Click on the Next button to continue.

Figure 2-3.  -> Hostname and Domain Name Configuration Screen

---

Note: You can use Ctrl L to refresh the YaST screen as necessary.

---

The Network Configuration II screen appears. Select Change and a small window pops up that lets you choose Network Interfaces... or "Reset to Defaults" (as shown in Figure 2-4). Choose Network Interfaces. Click Next to continue.

Figure 2-4. Network Card Configuration Interfaces Screen

From the Network Card Configuration Overview screen, configure the first card under Name to establish the public network (sometimes called the house network) connection to your SGI Altix ICE 8200 system.

Figure 2-5. Network Card Configuration Overview Screen

---

Note: Do NOT configure the second interface at this time. A script will do this for you in a later step.

---

From the Network Address Setup screen, enter the IP address for the system admin controller. SGI recommends static IP configuration (as opposed to DHCP). This is your public/house network information. Click on the Next button to continue.

Figure 2-6. Network Address Setup Screen

From the Hostname and Name Server Configuration screen, enter the name and DNS domain name as shown in Figure 2-7. Note that the hostname was entered in step 7.

Figure 2-7. Hostname and Name Server Configuration Screen

From the Routing Configuration screen, enter the appropriate gateway address and netmask. Click on the OK button to continue.

From the Clock and Time Zone screen, select the appropriate region and time zone. Click on the Next button to continue.

From the Password for the System Administrator “root” screen, set the root password. Click on the Next button to continue.

From the User Authentication Method screen, select the authentication method to use for the users on your system. Click on the Accept button to continue.

Enter the user's full name, username, and user password in the New Local User screen. Click on the Next button to continue.

From the Hardware Configuration screen, select Use Following Configuration. Click on the Next button to continue.

An Installation Competed screen appears, as show in Figure 2-8. Click on the Finish button.

Figure 2-8. Installation Competed Screen

After you have completed the YaST first boot installation instructions, login into the system admin controller. You can use YaST to confirm or correct any configuration settings.

---

Note: It is important that you make sure that you network settings are correct before proceeding with cluster configuration.

---

You are now ready to run the configure-cluster command, proceed to the next section “configure-cluster Command Cluster Configuration Tool”.

Perform steps one through five in the SLES10 procedure described, above (see “Installing SLES10 on the Admin Node”). They are the same for SLES11.

After the reboot completes from the first five steps you followed in the SLES10 Admin Node Installation instructions, you will eventually see the YaST2 - firstboot@Linux Welcome screen, as shown in Figure 2-9. Click on the Next button to continue.

Figure 2-9. YaST2 - firstboot@Linux Welcome Screen

---

Note: The YaST Installation Tool has a main menu with sub-menus. You will be redirected back to the main menu, at various times, as you follow the steps in this procedure.

---

From the Hostname and Domain Name screen, as shown in Figure 2-10, enter the hostname and domain name of your system in the appropriate fields. Make sure that Change Hostname via DHCP is not selected (no x should appear in the box). Click the Next button to continue.

Figure 2-10. Hostname and Domain Name Screen

---

Note: You can use Ctrl L to refresh the YaST screen as necessary.

---

The Network Configuration II screen appears, as shown in Figure 2-11. Select Change and a small window pops up that lets you choose Network Interfaces... or Reset to Defaults. Choose Network Interfaces.

Figure 2-11. Network Configuration II Screen

From the Network Settings screen, as shown in Figure 2-12, configure the first card under Name to establish the public network (sometimes called the house network) connection to your SGI Altix ICE 8200 system. To do this, highlight the first card and select Edit.

Figure 2-12. Network Settings Screen

---

Note: In SLES11, this screen is also where we will come back to in order to set up things like the default route and DNS. You can see all of those menu choices just to the right of Overview in Figure 2-12.

---

The Network Card Setup screen appears, as shown in Figure 2-13. SGI suggests using static IP addresses and not DHCP for admin nodes. Select Statically assigned IP Address. Once selected, you can enter the IP Address, Subnet Mask, and Hostname. These are the settings for your admin node's house/public network interface. You will enter the default route, if needed, in a different step. Select Next to continue.

Figure 2-13. Network Card Setup Screen

At this point, you are back at the Network Settings screen as shown in Figure 2-14. At this time, select Hostname/DNS. In this screen, you should enter your house/public network hostname and fully qualified domian names. In addition, any name servers for your house/public network should be supplied. Please select (ensure an x is in the box) for Write hostname to /etc/hosts. Do not select OK yet.

Figure 2-14. Network Settings Screen

Select Routing shown in Figure 2-15 and enter your house/public network default router information there. Now you can select OK.

Figure 2-15. Network Settings Routing Screen

You are now back at the Network Configuration II screen, Click Next.

In the Clock and Time Zone screen, you can enter the appropriate details. Select Next to continue.

In the Password for the System Administrator "root"' screen, enter the password you wish to use. This password will be used throughout the cluster, not just the admin node. Select Next to continue.

In the User Authentication Method screen, most customers will want to stick with the default (Local). Select Next to continue.

In the New Local User screen, you can just select Next (and say Yes to the Empty User Login warning). Select Next to continue.

In Installation Completed, select Finish.

After you have completed the YaST first boot installation instructions, login into the system admin controller. You can use YaST to confirm or correct any configuration settings.

---

Note: It is important that you make sure that you network settings are correct before proceeding with cluster configuration

---

You are now ready to run the configure-cluster command.

The configure-cluster command does not always draw the screen properly from the serial console. Therefore, log in to your admin node as root using ssh prior to running the configure-cluster command. For more information on the configure-cluster command, see “configure-cluster Command Cluster Configuration Tool”.

Follow normal admin install DVD instructions.

When the system boots up, firstboot questions will start.

---

Note: The default root password is sgisgi.

---

RHEL firstboot has a timeout after which firstboot will quit. If you wish to restart the firstboot menu, enter the following:

# /etc/init.d/firstboot start

To force it to run, use the following commands:

# touch /etc/reconfigSys
# /etc/init.d/firstboot

Use Network configuration to configure eth0 for your house network.

Set Firewall configuration, appropriately.

Set up the time zone in Timezone configuration.

Currently, the following steps need to be performed before you start the configure-cluster command (see “configure-cluster Command Cluster Configuration Tool”).

If text based firstboot is already running, choose exit.

If needed, perform the following command:

# touch /etc/reconfigSys

If you are connecting from a workstation, you need networking configured on the admin node at least enough to be able to ssh to the node. To do this, run system-config-network from the console and configure eth0 with the proper networking values for your network.

After system-config-network exits, run the following commads:

# /etc/init.d/network restart
# /etc/init.d/portmap start

Use the following command, to connect to the admin node:

# ssh -X11 root@admin-node

Perform the following command:

# /etc/init.d/firstboot start

Currently, the following steps need to be performed before you start the configure-cluster command (see “configure-cluster Command Cluster Configuration Tool”).

Use the cat command to view the contents of the file and perform the following:

Start system-config-network in graphical mode.

Click New.

A window comes up prompting for Address:, Hostname:, and Aliases.

For entries missing from the hosts table that you noted above, perform the following:

---

Note: The system-config-network command will NOT display the localhost entries in the GUI but it will add them. The entry for your house network will show up in the GUI.

---

Choose File -> Save.

If your hostname were 'foo' and your fully qualified domain name were 'foo.bar.org', then your /etc/hosts would look something like this after the steps above are complete:

::1     localhost6.localdomain6      localhost6
127.0.0.1       localhost.localdomain       localhost
128.162.244.88  foo.bar.org     foo

---

Note: If localhost is missing from /etc/hosts, various commands will fail to start up properly. If your hostname is missing from /etc/hosts, configure-cluster will error out.

---

At this point, enter hostname -d to confirm it returns the domain name. If it does not, try nscd -i hosts to invalidate the nscd hosts cache and see if hostname returns what you expect then. If not, reboot the admin node.

Set the root password with the passwd command.

You may now start the configure-cluster command.

---

Note: SGI suggests that you run the configure-cluster command either from the VGA screen or from an ssh session to the admin node. Avoid running the configure-cluster command from a serial console.

---

To start cluster configuration, enter the following command:

% /opt/sgi/sbin/configure-cluster

The Cluster Configuration Tool: Initial Configuration Check screen appears, as shown in Figure 2-16. This tool provides instructions on the steps you need to take to configure your cluster. Click OK to continue.

Figure 2-16. Cluster Configuration Tool: Initial Configuration Check Screen

The Cluster Configuration Tool: Initial Cluster Setup screen appears, as shown in Figure 2-17. Read the notice and then click OK to continue.

Figure 2-17. Cluster Configuration Tool: Initial Cluster Setup Screen

---

Note: The Cluster Configuration Tool has a main menu with sub-menus. You will be redirected back to the main menu, at various times, as you follow the steps in this procedure.

---

From the Initial Cluster Setup screen, select Repo Manager: Set up Software Repos and click OK.

Figure 2-18. Initial Cluster Setup Tasks Screen

To add the SLES media and other media, such as, SGI ProPack, click OK.

Figure 2-20. Cluster Configuration Tool: Repo Manager Screen Two

To register additional media with SGI Tempo, click Yes.

Figure 2-21. Cluster Configuration Tool: Repo Manager Screen Three

Enter the full path to the mount point or the ISO file or a URL or NFS path that points to an ISO file. Click OK to continue.

Figure 2-22. Cluster Configuration Tool: Repo Manager Screen Four

From the Repo Manager: Add Media screen, click OK to continue and eject you DVD if you used physical media.

Figure 2-23. Cluster Configuration Tool: Repo Manager: Add Media Screen Four

---

Note: You will continue to be prompted to add additional media until you answer no. Once you answer no, you are directed back to the Inital Cluster Setup Tasks menu.

---

After choosing the Network Settings option, the Cluster Network Setup screen appears, as shown in Figure 2-24.

Figure 2-24. Cluster Network Setup Screen

The subnet addresses allows you to change the cluster internal network addresses. SGI recommends that you do NOT change these. Click OK to continue to adjust subnets. Otherwise, select Domain Name: Configure Cluster Domain Name and then skip to step 31. A warning screen appears, as shown in Figure 2-25.

Figure 2-25. Update Subnet Address Warning Screen

The Update Subnet Addresses screen appears, as shown in Figure 2-26.

Figure 2-26. Update Subnet Addresses Screen

The default IP address of the system admin controller which is the Head Network for the Altix ICE system is shown. SGI recommends that you do NOT change the IP address of the system admin controller (admin node) or rack leader controllers (leader nodes) if at all possible. You can adjust the IP addresses of the InfiniBand network (ib0 and ib1) to match the IP requirements of the house network. Click OK to continue.

Enter the domain name for your Altix ICE system, as shown in Figure 2-27. Click OK to continue (this will be a subdomain to your house network, by default).

Figure 2-27. Update Cluster Domain Name Screen

The next operation in the Initial Cluster Setup menu is NTP Time Server/Client Setup . This procedure changes your NTP configuration file. Click on OK to continue. This sets the system admin controller to serve time to the Altix ICE system and allows you to add time servers on your house networks, which you may optionally use.

Figure 2-28. NTP Time Server/Client Setup Screen

Configure NTP time service as shown in Figure 2-29. The example provided is for SLES10 SP2. SLES11 is simlar. For RHEL 5.3, you need to configure ntp by hand after the ntp.conf file is put into place. Click Next to continue.

Figure 2-29. Advance NTP Configuration Screen

From the New Synchronization screen, select a synchronization peer and click Next to continue.

Figure 2-30. New Synchronization Screen

From the NTP Server screen, set the address of the NTP server and click OK to continue.

Figure 2-31. NTP Server Screen

The YaST tool completes. Click OK to continue.

Figure 2-32. NTP Time Server/ Client Setup Screen Three

The next step in the Initial Cluster Setup menu directs you to select Perform Initial Admin Node Infrastructure Setup. This step runs a series of scripts that will configure the system admin controller of the Altix ICE system.

The script installs and configures your system and you should see an install-cluster completed line in the output.

Figure 2-33. Admin Infrastructure One Time Setup Screen One

The root images for the service, rack leader controller, and compute nodes are then created. The output of the mksiimage commands are stored in a log file at the following location:

/var/log/cinstallman

You can review the output if you so choose.

The final output of the script reads, as follows:

/opt/sgi/sbin/create-default-sgi-images Done!

---

Note: As it notes on the Admin Infrastructure One Time Setup screen, this step takes about 30 minutes.

---

Click OK to continue.

The next step in the Initial Cluster Setup menu is to configure the house DNS resolvers. It is OK to set these resolvers to the same name servers used on the system admin controller itself. Configuring these servers is what allows service nodes to resolve host names on your network. For a description of how to set up service nodes, see “Service Node Discovery, Installation and Configuration”. This menu has default values printed that match your current admin node resolver setup. If this is ok, just select OK to continue. Otherwise, make any changes you wish to the resolver listing and select OK. If you do not wish to have any house resolvers, select Disable House DNS.

After entering the IPs, click OK to enable, click Disable House DNS to stop using house DNS resolution, click Back to leave house DNS resolution as it was when you started (disabled at installation).

Figure 2-34. Configure House DNS Resolvers Screen

The setting DNS forwarding screen appears. Click Yes to continue.

Figure 2-35. Setting DNS Forwarding Screen

The Initial Cluster Setup complete message appears. Click OK to continue.

Figure 2-36. Cluster Configuration Tool: Admin Infrastructure One Time Setup Screen

Proceed to “Installing Software on the Rack Leader Controllers and Service Nodes”. It describes the discovery process for the rack leader controllers in your system and how to install software on the rack leader controllers.

---

Note: The main menu contains a reset the database function that allows you to start software installation over without having to reinstall the system admin controller.

---

Use the configuration tools provided on your service node to turn on IP forwarding and enable NAT/IP MASQUERADE.

Specific instructions should be available in the third-party documentation provided for your storage node system. Additional documentation is available at /opt/sgi/docs/setting-up-NAT/README. This document describes how to get NAT working for both IB interfaces.

---

Note: This file is only on the service node. You need to # ssh service0 and then from service 0 # cd /opt/sgi/docs/setting-up-NAT .

---

Update the all of the compute node images with default route configured for NAT.

SGI recommends a script on the system admin controller at /opt/sgi/share/per_host_customization/global/sgi-static-routes that can customize the routes based upon rack, IRU, and slot of the compute blade. Some examples are available in that script.

Use the cimage --push-rack command to propagate the changes to the proper location for compute nodes to boot. For more information on using the cimage command, see “cimage Command” in Chapter 3 and “Customizing Software On Your SGI Altix ICE System” in Chapter 3.

Use the cimage --set command to select the image.

Reboot/reset the compute nodes using that desired image.

Once the service node(s) has NAT enabled, is attached to an operational house network, and the compute nodes are booted from an image which sets their routing to point at the service node, test the NAT operation by using the ping(8) command to ping known IP addresses on the house network from an interactive session on the compute blade.

See the troubleshooting discussion that follows.

Edit the system admin controller's /opt/sgi/share/per_host_customization/global/sgi-fstab file or alternatively an image-specific script. An example of the sgi-fstab file is, as follows:

#!/bin/sh
#
# Copyright (c) 2007,2008 Silicon Graphics, Inc.
# All rights reserved.
#
#  This program is free software; you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  You should have received a copy of the GNU General Public License
#  along with this program; if not, write to the Free Software
#  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
#
# Set up the compute node's /etc/fstab file.
#
# Modify per your sites requirements.
#
# This script is excecuted once per-host as part of the install-image operation
# run on the leader nodes, which is called from cimage on the admin node.
# The full path to the per-host iru+slot directory is passed in as $1,
# e.g. /var/lib/sgi/per-host/<imagename>/i2n11.
#

# sanity checks
. /opt/sgi/share/per-host-customization/global/sanity.sh

iruslot=$1
os=( $(/opt/oscar/scripts/distro-query -i ${iruslot} | sed -n '/^compat /s/^compat.*: //p') )
compatdistro=${os[0]}${os[1]}

if [ ${compatdistro} = "sles10" -o ${compatdistro} = "sles11" ]; then

	#
	# SLES 10 compatible
	#
	cat <<EOF >${iruslot}/etc/fstab
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
tmpfs           /tmp            tmpfs   size=150m       0       0
EOF

elif [ ${compatdistro} = "rhel5"  ]; then

	#
	# RHEL 5 compatible
	#

	#
	# RHEL expects several subsys directories to be present under /var/run
	# and /var/lock, hence no tmpfs mounts for them
	#
	cat <<EOF >${iruslot}/etc/fstab
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
tmpfs           /tmp            tmpfs   size=150m       0       0
devpts          /dev/pts        devpts  gid=5,mode=620  0       0
EOF

else

	echo -e "\t$(basename ${0}): Unhandled OS.  Doing nothing"

fi

Add the mount point, push the image, and reset the node.

The server's export should get mounted. If it is not, use the technique for troubleshooting outlined in “Troubleshooting Service Node Configuration for NAT”.

In this case, you do not have to set up any additional NIS servers. Instead, each service node and compute node should be configured to bind to the existing house network servers. The nodes should already have the ypbind package installed. The following steps should work with most Linux distributions. You may need to vary them slightly to meet your specific needs.

For service nodes, the instructions are very similar to the following:

The only difference is that you should configure yp.conf to look at the IP address of your house network NIS server and not the leader node as is described in the sections listed, above.

Any service nodes that are NOT acting as an NIS slave server can be pointed at the existing house network NIS servers as described in Procedure 2-13. This is because they have house interfaces.

One (or more) service node(s) should be then be configured as NIS slave server(s) to the existing house network NIS Master server.

Since SGI can not anticipate what operating system or release the house network NIS Master server is running, no suggestions on any configuration you need to do to tell it that you are adding new NIS slave servers can be offered, however, some hints could be found in “Setting Up a RHEL Service Node as a NIS Master”.

Use the parted(8) utility, or some other partition tool, to create a partition on /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a . The following example makes one filesystem out of the disk. You can use the parted utility interactively or in a command-line driven manner.

Make a new msdos label, as follows:

# parted /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a mklabel msdos

Find the size of the disk, as follows:

# # parted /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a print
Disk geometry for /dev/sdb: 0kB - 249GB
Disk label type: msdos
Number  Start   End     Size    Type      File system  Flags
Information: Don't forget to update /etc/fstab, if necessary. 

Create a partition that spans the disk, as follows:

# # parted /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a mkpart
primary ext2 0 249GB
Information: Don't forget to update /etc/fstab, if necessary.  

Issue the following command to cause the /dev/disk/by-id partition device file is in place and available for use with the mkfs command that follows:

# udevtrigger

Create a filesystem on the disk. You can choose the filesystem type.

---

Note: The mkfs.ext3 command takes more than 10 minutes to create a single 500GB filesystem using default mkfs.ext3 options. If you do not need the number of inodes created by default, use the -N option to mkfs.ext3 or other options that reduce the number of inodes. The following example creates 20 million inodes. XFS filesystems can be created in much shorter time.

---

# mkfs.ext3 -N 20000000 /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a-part1

# mkfs.xfs /dev/disk/by-id/scsi-3600508e0000000008dced2cfc3c1930a-part1 

---

Note: RHEL based distros normally use the LABEL= syntax in /etc/fstab.

---

Add the newly created filesystem to the server's fstab file and mount it. Ensure that the new filesystem is exported and that the NFS service is running, as follows:

---

Note: Steps 8 and 9 are performed from the system admin controller (admin node).

---

The following steps describe how to mount the home filesystem on the compute nodes, as follows:

---

Note: SGI recommends that you always work on clones of the SGI-supplied compute image so that you always have a base to copy to fall back to if necessary. For information on cloning a compute node image, see “Customizing Software Images” in Chapter 3.

---

When you reboot the compute nodes, they will mount your new home filesystem.

Start up YaST, as follows:

# yast nis_server

Choose Create NIS Master Server and click on Next to continue.

Choose an NIS domain name and place it in the NIS Domain Name window. This example, uses ice.

Set up the NIS master server slaves.

---

Note: You are now in the NIS Master Server Slaves Setup. Just now, you can enter the already defined rack leader controllers (leader nodes) here. If you add more leader nodes or re-discover leader nodes, you will need to change this list. For more information, see “Tasks You Should Perform After Changing a Rack Leader Controller ”.

---

Select Add and enter r1lead in the Edit Slave window. Enter any other rack leader controllers you may have just like above. Click on Next to continue.

You are now in NIS Server Maps Setup . The default selected maps are okay. Avoid using the hosts map (not selected by default) because can interfere with Altix ICE system operations. Click on Next to continue.

You are now in NIS Server Query Hosts Setup. Use the default settings here. However, you may want to adjust settings for security purposes. Click on Finish to continue.

At this point, the NIS master is configured. Assuming you checked the This host is also a NIS client box, the service node will be configured as a NIS client to itself and start yp ypbind for you.

Log in to the service node as root and turn on these services:

# chkconfig ypserv on
# chkconfig yppasswdd on

Choose a NIS domain name and place it in the /etc/sysconfig/network file. For example:

# echo "NISDOMAIN=ice" >> /etc/sysconfig/network

The NIS domain will be set using this value when ypbind or ypserv is started for the first time.

Change NOPUSH=true to NOPUSH=false in /var/yp/Makefile. This will ensure that slave servers get map updates.

Start up the NIS server daemon, as follows:

# /etc/init.d/ypserv start

Configure the yp master server, as follows:

# /usr/lib64/yp/ypinit -m

It will prompt you for the hostnames that will act as NIS servers. It automatically includes the service node acting as the master in the list. At this time, enter the hostnames for the leader nodes starting with r1lead. Enter Ctrl-d when done as instructed by the tool.

Start up yppasswdd, as follows:

# /etc/init.d/yppasswdd start

NIS Master Servers are also NIS Clients. However, they are configured to look at themselves for NIS. Therefore, follow these steps to make the NIS Master Server an NIS client to itself:

Enable ypbind, perform the following:

# chkconfig ypbind on 

Set the default domain (already set on NIS master). Change ice (or whatever domain name you choose above) to be the NIS domain for your Altix ICE system, as follows:

# echo "ice" > /etc/defaultdomain

In order to ensure that no NIS traffic goes over the IB network, SGI does not recommend using NIS broadcast binding on service nodes. You can list a few leader nodes the in /etc/yp.conf file on non-NIS-master service nodes. The following is an example /etc/yp.conf file. Add or remove rack leader nodes as appropriate. Having more entries in the list allows for some redundancy. If r1lead is hit by excessive traffic or goes down, ypbind can use the next server in the list as its NIS server. SGI does not suggest listing other service nodes in yp.conf file because all resolvable names for service nodes on service nodes use IP addresses that go over the InfiniBand network. For performance reasons, it is better to keep NIS traffic off of the InfiniBand network.

ypserver r1lead
ypserver r2lead

Start the ypbind service, as follows:

# rcypbind start

The service node is now bound.

Add the NIS include statement to the end of the password and group files, as follows:

# echo "+:::" >> /etc/group
# echo "+::::::" >> /etc/passwd
# echo "+" >> /etc/shadow

Log in to the leader node(s) as root enable ypserv, as follows:

# chkconfig ypserv on

Choose a NIS domain name and place it in the /etc/sysconfig/network file. For example:

# echo "NISDOMAIN=ice" >> /etc/sysconfig/network

The NIS domain will be set using this value when ypbind or ypserv is started for the first time.

Start the yp server, as follows:

# /etc/init.d/ypserv start

For each leader node, log on using the ssh command and run this command replacing service0 with the hostname of the service node acting as the NIS master, as follows:

# /usr/lib64/yp/ypinit -s service0

Enable ypbind to make this a NIS client, as follows:

# chkconfig ypbind on

Configure the leader node to be a NIS client to itself, as follows:

# echo "ypserver localhost" >> /etc/yp.conf

Start up ypbind, as follows:

# /etc/init.d/ypbind start

Optionally, set up the password, shadow, and group files with NIS includes, as follows:

---

Note: SGI does not suggest that users log in to leader nodes, however, it is sometimes helpful for their accounts to show up there. Therefore, this is OPTIONAL.

---

# echo "+:::" >> /etc/group
# echo "+::::::" >> /etc/passwd
# echo "+" >> /etc/shadow

Optionally, if you elected to perform the above step, then you should ensure NIS is enabled in /etc/nsswitch.conf for passd, shadow, and group. The lines would look like this:

passwd:     files nis
shadow:     files nis
group:      files nis

Make it so ypbind starts at bootup, as follows:

# chkconfig ypbind on

Configure the NIS domain to the same NIS domain that the NIS master server is setup as, as follows:

# echo "NISDOMAIN=ice" >> /etc/sysconfig/network

In order to ensure that no NIS traffic goes over the IB network, SGI does not recommend using NIS broadcast binding on service nodes. You can list a few leader nodes the in the /etc/yp.conf file on non-NIS-master service nodes. The following is an example /etc/yp.conf file. Add or remove rack leader nodes as appropriate. Having more entries in the list allows for some redundancy. If r1lead is experiences excessive traffic or goes down, ypbind can use the next server in the list as its NIS server. SGI does not suggest listing other service nodes in yp.conf file because all resolvable names for service nodes on service nodes use IP addresses that go over the InfiniBand network. For performance reasons, it is better to keep NIS traffic off of the InfiniBand network.

ypserver r1lead
ypserver r2lead

Start ypbind up, as follows:

# /etc/init.d/ypbind start

Set up the password, shadow, and group files with NIS includes, as follows:

# echo "+:::" >> /etc/group
# echo "+::::::" >> /etc/passwd
# echo "+" >> /etc/shadow

Enable NIS lookups in the /etc/nsswitch.conf file. Ensure NIS is enabled in /etc/nsswitch.conf for passd, shadow, and group, as follows:

passwd:     files nis
shadow:     files nis
group:      files nis

SGI suggests that you operate on a cloned image, preserving the SGI default images as a reference. See “Customizing Software On Your SGI Altix ICE System” in Chapter 3.

In RHEL, the NIS domain is set up in /etc/sysconfig/network . However, this is a file that Tempo normally creates on its own in per-host-customization. Therefore, to modify this file, we have to create a customization script of our own that appends the value. This script can be simple. The script filename should sort alphabetically after "sgi-hostname" to ensure it executes after the sgi-hostname customization script. For example, create the following file on the admin node assuming the NIS domain is 'ice' and the compute node image is compute-rhel52-clone, as follows:

# vi /opt/sgi/share/per-host-customization/global/yp-setup

Put in the following two lines in the file, then save it, as follows:

iruslot=$1
echo "NISDOMAIN=ice" >> ${iruslot}/etc/sysconfig/network

Change permissions on the file to be executable and readable, as follows:

# chmod a+rx /opt/sgi/share/per-host-customization/global/yp-setup

Set up compute nodes to get their NIS service from their rack leader controller (fix the domain name as appropriate), as follows:

# echo "ypserver lead-eth" > /var/lib/systemimager/images/compute-rhel52-clone/etc/yp.con

Enable the ypbind service, using the chroot command, as follows:

# chroot /var/lib/systemimager/images/compute-rhel52-clone chkconfig ypbind on

Set up the password, shadow, and group files with NIS includes, as follows:

# echo "+:::" >> /var/lib/systemimager/images/compute-rhel52-clone/etc/group
# echo "+::::::" >> /var/lib/systemimager/images/compute-rhel52-clone/etc/passwd
# echo "+" >> /var/lib/systemimager/images/compute-rhel52-clone/etc/shadow

Enable NIS lookups in nsswitch.conf . On a compute node, do this by ensuring the nsswitch.conf file in the image you wish to modify has the lines as they are shown below. The filename would be, assuming image name compute-rhel52-clone, /var/lib/systemimager/images/compute-rhel52-clone/etc/nsswitch.conf :

passwd:     files nis
shadow:     files nis
group:      files nis

Push out the updates using the cimage command, as follows:

# cimage --push-rack compute-rhel52-clone "r*" 

Create a compute node image clone. SGI recommends that you always work with a clone of the compute node images. For information on how to clone the compute node image, see “Customizing Software Images” in Chapter 3.

Change the compute nodes to use the cloned image/kernel pair, as follows:

admin:~ # cimage --set compute-sles10sp2-clone 2.6.16.46-0.12-smp "r*i*n*"

Set up the NIS domain, as follows ( ice in this example):

admin:~ # echo "ice" > /var/lib/systemimager/images/compute-sles10sp2-clone/etc/defaultdomain

Set up compute nodes to get their NIS service from their rack leader controller (fix the domain name as appropriate), as follows:

admin:~ # echo "ypserver lead-eth" > /var/lib/systemimager/images/compute-sles10sp2-clone/etc/yp.conf

Enable the ypbind service, using the chroot command, as follows:

admin:~# chroot /var/lib/systemimager/images/compute-sles10sp2-clone chkconfig ypbind on

Set up the password, shadow, and group files with NIS includes, as follows:

admin:~# echo "+:::" >> /var/lib/systemimager/images/compute-sles10sp2-clone/etc/group
admin:~# echo "+::::::" >> /var/lib/systemimager/images/compute-sles10sp2-clone/etc/passwd
admin:~# echo "+" >> /var/lib/systemimager/images/compute-sles10sp2-clone/etc/shadow

Push out the updates using the cimage command, as follows:

admin:~ # cimage --push-rack compute-sles10sp2-clone "r*"

Log in to the NIS Master service node as root.

Issue a useradd command similar to the following:

# useradd -c "Joe User" -m -d /home/juser juser

Provide the user a password, as follows:

# passwd juser

Push the new account to the NIS servers, as follows:

# cd /var/yp && make

Shut down any compute nodes that are running the compute-sles10sp2 image (see “Power Management Commands” in Chapter 3).

Push out the changes with the cimage --push-rack command, as follows:

# cimage --push-rack compute-sles10sp2 r\* 

Update the database to reflect the new kernel in the compute-sles10sp2, as follows:

# cimage --update-db compute-sles10sp2

Verify the available kernel versions and select one to associate with the compute-sles10sp2 image, as follows:

# cimage --list-images

Associate the compute nodes with the new kernel/image pairing, as follows:

# cimage --set compute-sles10sp2 2.6.16.46-0.12-smp "r*i*n*"

---

Note: Replace 2.6.16.46-0.12-smp with the actual kernel version.

---

Reboot the compute nodes with the new kernel/image.