Install and select the SMC repository with the crepo, as follows:

sys-admin:~ # crepo --add sgimc-1.2-cd1-media-sles11-x86_64.iso
sys-admin:~ #  crepo --select SGI-Management-Center-1.2-sles11

Start configure-cluster (see “configure-cluster Command Cluster Configuration Tool”) and run Install SGI Management Center (optional, if available). Quit configure-cluster when finished.

---

Note: This example applies to a SLES11 SP1 installation, RHEL 6 will be similar.

---

SMC requires an LK license. Save the license to /etc/lk/keys.dat.

Restart /etc/init.d/mgr, as follows:

sys-admin:~ #  /etc/init.d/mgr restart

To run mgrclient, which will launch the SMC GUI, logout and log back in, to ensure that all environment variables are initialized appropriately.

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 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 you press 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 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 partitioned 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.

After the reboot completes, you will eventually see the YaST2 - firstboot@Linux Welcome screen, as shown in Figure 2-2. Select the Next button to continue.

Figure 2-2. 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-3, 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). Note that the hostname is saved to /etc/hosts in step 10, below. Click the Next button to continue.

Figure 2-3. Hostname and Domain Name Screen

---

Note: The mostly used keys are Tab and Shift + Tab to move forward and backward in modules, the arrow keys to move up and down or left and right in lists, the shortcuts (press Alt + highlighted letter) and Enter to execute the selected action or activate a menu item. You can use Ctrl L to refresh the YaST screen as necessary.

---

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

Figure 2-4. Network Configuration II Screen

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

Figure 2-5. 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-5.

---

The Network Card Setup screen appears, as shown in Figure 2-6. 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.

---

Note: You must use a fully qualified hostname (host + domain), such as, mysystem-admin.domainname .mycompany.com or the configure-cluster command will fail.

---

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-6. Network Card Setup Screen

At this point, you are back at the Network Settings screen as shown in Figure 2-7. At this time, select Hostname/DNS. In this screen, you should enter your house/public network hostname and fully qualified domain 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-7. Network Settings Screen

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

Figure 2-8. 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”.

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.

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 partitioned 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.

Proceed to the next section (“Initial Configuration of a RHEL 6 Admin Node”), to configure RHEL 6 on the admin node.

Add the IPADDR, NETMASK, and NETWORK values appropriate for the public (house) network interface to the /etc/sysconfig/network-scripts/ifcfg-eth0 file similar to the following example:

IPADDR=128.162.244.88
NETMASK=255.255.255.0
NETWORK=128.162.244.0

Create the /etc/sysconfig/network file similar to the following example:

[root@localhost ~]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=my-system-admin
GATEWAY=128.162.244.1

The House DNS servers must be set using configure-cluster (see “configure-cluster Command Cluster Configuration Tool”). Tempo overwrites anything added to /etc/resolv.conf. However, it is possible to temporarily add DNS server information to this file at this point of the install so that hostnames can be resolved on the admin node.

Add the IP address of the house network interface and the name(s) of the admin node to /etc/hosts file similar to the following example:

# echo "128.162.244.88 my-system-admin.domain-name.mycompany.com my-system-admin" >> /etc/hosts

Set the admin node hostname, as follows:

# hostname my-system-admin

Configure the /etc/resolv.conf file with your DNS server set up. Later in the cluster set up process, these name servers will be used as the defaults for the House DNS Resolvers you configure in a later configure-cluster command step. Setting this now allows you to register with RHN and allows you to access your house network to access any DVD images or other settings you need. You may choose to defer this step, but then you will need to also defer rhn_register. Here is an example resolv.conf:

search mydomain.mycompany.com
nameserver 192.168.0.1
nameserver 192.168.0.25

Force the invalidation of the host cache of nscd with the nscd(8) command on the hosts file, as follows:

# nscd -i hosts

Restart the following services (in this order), as follows:

# /etc/init.d/network restart
# /etc/init.d/rpcbind start
# /etc/init.d/nfslock start

Set the local timezone. The timezone is set with /etc/localtime, a timezone definition file. The timezone defined in /etc/localtime can be determined, as follows:

# strings /etc/localtime | tail -1
CST6CDT,M3.2.0,M11.1.0

Link the appropriate timezone file from directory /usr/share/zoneinfo to /etc/localtime. For example, set timezone to Pacific Time / Los Angeles, as follows:

# /bin/cp -l /usr/share/zoneinfo/PST8PDT /etc/localtime.$$
# /bin/mv /etc/localtime.$$ /etc/localtime

Confirm the timezone, as follows:

# strings /etc/localtime | tail -1
PST8PDT,M3.2.0,M11.1.0

Set network time configuration.

On a RHEL6 admin node, the default ntp configuration file is replaced when the configure-cluster task Configure Time Client/Server (NTP) is run. Insert local ntp server information after running configure-cluster (see “Set Network Time Configuration for RHEL6 Admin Node”).

Make sure you have registered with the Red Hat Network (RHN). If you have not yet registered, run the following command:

% /usr/bin/rhn_register

Run the configure-cluster command. See “configure-cluster Command Cluster Configuration Tool”.

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-10. This tool provides instructions on the steps you need to take to configure your cluster. Click OK to continue.

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

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

Figure 2-11. 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-12. Initial Cluster Setup Tasks Screen

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

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

To register additional media with SGI Tempo, click Yes.

Figure 2-15. 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-16. 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-17. 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-18.

Figure 2-18. 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-19.

Figure 2-19. Update Subnet Address Warning Screen

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

Figure 2-20. 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-21. Click OK to continue (this will be a subdomain to your house network, by default).

Figure 2-21. Update Cluster Domain Name Screen

The configure-cluster NTP configuration screens with for RHEL 6 are different from those for SLES. The next operation in the Initial Cluster Setup menu is NTP Time Server/Client Setup is for SLES. 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-22. NTP Time Server/Client Setup Screen

Configure NTP time service as shown in Figure 2-23. Click Next to continue.

Figure 2-23. Advanced NTP Configuration Screen

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

Figure 2-24. New Synchronization Screen

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

Figure 2-25. NTP Server Screen

The YaST tool completes. Click OK to continue.

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

On a RHEL 6 installation, from the menu screen in which "set ntp servers" is selected, selecting setting ntp servers just displays Figure 2-27 and then returns you to the previous menu.

Figure 2-27. Cluster Configuration Tool: NTP Time Server / Client Setup Screen (RHEL)

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-28. 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-29. Configure House DNS Resolvers Screen

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

Figure 2-30. Setting DNS Forwarding Screen

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

Figure 2-31. 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 service0 # 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.

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 those found in “Setting Up a SLES Service Node as a NIS Client”.

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.

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 mkpart primary ext2 0 249GB
Information: Don't forget to update /etc/fstab, if necessary.

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 

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.

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

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-sles11-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-sles11-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-sles11-clone/etc/yp.conf

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

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

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

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

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

admin:~ # cimage --push-rack compute-sles11-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-sles11 image (see “Power Management Commands” in Chapter 3).

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

admin:~ # cimage --push-rack compute-sles11 r\* 

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

admin:~ # cimage --update-db compute-sles11

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

admin:~ # cimage --list-images

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

admin:~ # cimage --set compute-sles11 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.