You are on page 1of 18

Site: http://www.scribd.

com/doc/2673166/Confi guring-and-Managing-a-Red-HatCluster-for-Red-Hat-Enterprise-Linux-51 http://publib.boulder.ibm.com/infocenter /tssfsv21/index.jsp?topic=/com.ibm.sanfs. doc/fog0_t_configuring_rsa_adapter.html Configuring the RSA II adapter
This topic describes how to configure the RSA II adapter for the SAN File System. Context Use the documentation supplied with the RSA II adapter card for configuration information. You need to change the factory-supplied IP address so that it is unique for your network. In addition, the SAN File System uses certain configuration settings (you will need to supply the configuration setting when you run the setupsfs command). Note: You can use the setupsfs command to configure the RSA II adapter if it is not already configured. However, you must use this procedure to set the IP address, to set the user ID password to NULL, or to reset the user ID password. This procedure assumes that you have properly cabled the RSA II adapter. The RSA II adapters in the engines all come with the same default IP address. This address is: 192.168.70.125. Note: If you have multiple RSA II adapters on the network at the same time, all will have the same IP address. If you use the Web interface to configure the RSA II adapter, you will not be able to determine the RSA II adapter that you are updating. Instead, you can update the IP address through the BIOS, and then use the Web interface to complete the configuration. The recommended IP addresses for the RSA II adapters in the cluster are 192.168.70.1 through 192.168.70.n, where n is incremented by 1 for each additional RSA adapter. A

cluster of eight engines would contain RSA adapters numbered from 192.168.70.1 to 192.168.70.8. Number the engines and RSA adapters from 1 through n, starting with the top engine in the rack and ending with the bottom engine in the rack. Steps 1. 2. 3. 4. 5. Reboot the engine. Press F1 when prompted to enter the BIOS setup panel. Click Advanced Setup, and update the RSA II IP address and subnet mask. Exit setup, saving your configuration changes. After the system has finished booting, open a Web browser and point it to the IP address for the RSA II card. 6. Log on to the RSA II using the default user ID (USERID) and password (PASSW0RD - the 0 is a zero). 7. In the left frame, click Server --> ASM Control --> System Settings. 8. Fill in the following information. o Name. The unique name of the RSA II adapter. This name must match the name of the metadata server. You will enter this name during metadata server setup. o IP address. Update the IP address to a unique IP address. o Server timeouts. Set the following timeouts:  Post watchdog. Set to 10 minutes.  OS watchdog. Set to 4 minutes.  Loader watchdog. Set to 10 minutes. o Set the date, time, and timezone. o Click Save to save your settings. 9. In the left frame, click Server -->ASM Control -->Login Profiles 10. Click on a "not used" link in the Login ID column. 11. Create a user ID and password to be used for logging in to the RSA II card. This user ID must have read/write (Supervisor) authority. You will enter this information during metadata server setup, and it is the same for all metadata server engines in the cluster. Important: The password must contain only alphanumeric characters and it must be at least 5 characters long. 12. Click Restart ASM on the left frame. 13. You can verify the IP setting and new user ID by closing your browser, reopening it, and pointing to the new IP address.

Sample installation on an IBM eServer xSeries 346
This topic provides a sample installation of SLES9 and the SAN File System software on an IBM® eServer™ xSeries® 346 (xSeries 346). This section is intended to be only an example to illustrate the installation steps from start to finish for one specific combination of servers and storage. It should not be used as a step-by-step guide for installing the SAN File System metadata server. For specific installation details, see Installing the operating system and Metadata server software installation and configuration. These sections contain additional information that can apply to your configuration. For instance, the sample installation described in this topic does not include upgrading the kernel or configuring the RDAC multipath driver, as those tasks did not apply in this scenario. They might apply to your particular installation scenario. Table 1 and Table 2 provide overviews of the steps you need to complete to install SLES9 and the SAN File System software on an xSeries 346. The steps follow the tables.

Table 1. Installing SAN File System 2.2.2 on an IBM xSeries 346 - Server steps Completed Update flash BIOS Update the diagnostics firmware Update the Baseboard Management Controller (service processor firmware) Configure the RSA II Update the RSA II firmware Update the Broadcom adapter firmware Update the hard drive firmware Configure the HostRAID controllers Create a RAID device Start the SLES9 installation Configure the installation settings Perform post-installation configuration Set up NTP to keep the time in sync Set up Ethernet bonding Step

Table 1. Installing SAN File System 2.2.2 on an IBM xSeries 346 - Server steps Completed Update flash BIOS Update the diagnostics firmware Create local users and groups for authentication Verify IBMJava is not installed Install and start IBMsdd Table 2. Completing SAN File System 2.2.2 post-server installation steps Completed Set up ssh keys Verify all servers discover the same number of LUNs Verify that the LDAP server responds to queries Verify that the multi-path device driver restarts Install IBMJava2-142-ia32-JRE Verify the server meets hardware and software requirements Create a configuration file Install SAN File System Before you begin . . . You need to get the SLES9 installation instructions and download firmware and updates, as detailed here. Get the SLES9 installation instructions 1. Go to the Personal computing support Web site: www.ibm.com/pc/support 2. In the Learn section, click Operating system installation and fill in the fields as shown Table 3: Table 3. SLES9 installation choices Field Brand Family Type Model Servers xSeries 346 8840 21U Value Step Step

3. Click Continue.

4. Click Installing SUSE LINUX Enterprise Server 9 Products - IBM eServer xSeries 346 (Type 8840). Read the installation instructions completely before continuing. Download firmware and updates 1. Ensure that your browser cookies are enabled to maintain the selections on the Downloads and drivers Web page that you will see in several steps. 2. Go to the Personal Computing Support Web site: www.ibm.com/pc/support 3. In the Browse list, choose Servers. A new page is displayed. Select the choices displayed in Table 3. Leave the Operating system field set to All operating systems listed. If you choose any other value, you might not find all the links listed in Table 4. 4. Click Continue. Take note of the information in the Original description field. The SLES9 installation has specific instructions based on the type of SCSI controller. The type of SCSI controller that your model includes is listed in the Original description field. (In this example, the SCSI controller is the Adaptec AIC-7902 dual-channel 64-bit Ultra320 LVD SCSI PCI controller.) 5. Click Downloads and drivers. From this page, various firmware and drivers can be downloaded as shown in Table 4. Instructions for downloading are provided for each package. Additional instructions are noted in the table. Table 4. Downloads and drivers Web-page selections On the Downloads and drivers page, download the following packages: (Critical update) Baseboard Management Controller (BMC) Update Diskette - IBM eServer xSeries 346 Notes

The Installing SUSE LINUX Enterprise Server 9 Products - IBM eServer xSeries 346 (Type 8840) document refers to this update as "the service processor firmware".

Table 4. Downloads and drivers Web-page selections On the Downloads and drivers page, download the following packages: Flash BIOS Update (Windows® package) - IBM eServer xSeries 346 Diagnostics Flash Update (Windows update package) IBM eServer xSeries 346 Broadcom Firmware Update Utility - Servers and IntelliStation® IBM Hard Disk Drive Update Program (DOS update package) - IBM IntelliStation and Servers IBM ServeRAID-7e (Adaptec HostRAID) Support CD (Digitally Signed) - Servers Remote Supervisor Adapter II Firmware Update - IBM eServer xSeries 346 Select the link with the description IBM ServeRAID-7e (Adaptec HostRAID) Device Driver for SLES9 32-bit and 64bit, service pack 1. Select the link with the description Remote Supervisor Adapter II Firmware Update - IBM eServer xSeries 346. Notes

After downloading the packages, you have the following media:
• • • • • • •

Baseboard Management Controller Update diskette IBM eServer xSeries 346 Flash BIOS Update diskette Diagnostics Flash Update 3 diskette set Broadcom Firmware Update diskette IBM Hard Disk Drive Update CD a320raid-3.00.050-1.sles9sp1i586.i586 update diskette Remote Supervisor Adapter II Firmware Update files

The following steps are provided as an example of installing SLES 9 on an xSeries 346. These steps might not be the same for your model and type. However, they provide an outline for an installation. Note: During boot in the following steps, the following warning is displayed twice:
PCI device resource allocation failure

1. Update flash BIOS:

2.

3.

4.

5.

a. Insert the IBM eServer xSeries 346 Flash BIOS Update diskette and reboot the system. b. When the IBM Flash Update Utility panel opens, click update POST/BIOS , and then press Enter. c. Follow the prompts to install the update. Update the diagnostics firmware: a. Insert the disk 1 of the Diagnostics Flash Update 3-diskette set and reboot the system. b. When the IBM Flash Update Utility panel appears, click Update Diagnostics. c. When prompted for disk 1, insert the second disk that was created during the diskette creation process. d. When prompted for disk 2, insert the third disk that was created during the diskette creation process. Update the Baseboard Management Controller (service processor firmware): a. Insert the Baseboard Management Controller Update Diskette and reboot. b. The firmware is updated automatically. c. Reboot when prompted. Configure the RSA II: a. Reboot the system and press F1 to enter setup. b. Select Advanced Setup. c. Select RSA II Settings. d. Change DHCP Control to Use Static IP. e. Enter values for IP Address, Subnet Mask and Gateway. f. Set OS USB Selection to Linux® OS. g. Select Save Values and Reboot RSA II, and then press Enter. Update the RSA II firmware: Follow the instructions in the readme.txt file that was extracted from the “Remote Supervisor Adapter II Firmware Update” archive.

6. Update the Broadcom adapter firmware: a. Insert the Broadcom Firmware Update Diskette and reboot. b. After the system starts, run the UPDATE 8840 command at the prompt (8840 corresponds to the xSeries 346). c. After the update is complete, reboot the system. 7. Update the hard drive firmware: a. Insert the IBM Hard Disk Drive Update CD and reboot the system. b. Follow the prompts to update the hard driver firmware. 8. Configure the HostRAID controllers: a. Reboot the system b. Press Ctrl-A when prompted to enter the SCSISelect Utility. c. Highlight each controller and select SCSI Disk Utilities to determine which controller has devices attached. d. Select Configure/View SCSI Controller Settings for the controller that you plan to use.

e. Select HostRAID, and then set it to Enabled. f. Save and exit. 9. Create a RAID device: a. Use the SCSISelect Utility to configure the RAID 1. To start the SCSISelect Utility, reboot the machine, and then immediately press Ctrl+A when the following message appears:
Press <Ctrl><A> for SCSI Select(TM) Utility!

b. Select a channel from the device menu and press Enter. c. From the Option menu, perform the following steps: i. Select Configure/View SCSI Controller Settings and press Enter. A new menu appears. ii. Ensure that HostRAID is selected. If not, select it, and then press Enter. iii. Select Enabled. iv. Save the settings and return to the Option menu. d. From the Option menu, select Configure/View HostRAID Settings, and then press Enter. The main menu appears and displays the list of available hard disks. e. From the main menu, press C to create a RAID array. f. Select RAID-1 as the RAID type and press Enter. g. From the Select RAID Member menu, press the space bar to select the hard drives. An X appears next to the drive you select. You select two drives: The drive that needs to be mirrored. This is the source drive that contains all the data. In this example, the ID is m. The location of the mirrored source drive. In this example, the ID is n. The ID for each drive is shown in the first column. b. Press Enter to display the RAID-1 Build Option window. Available options are: Create new RAID-1 (default) Copy from (m) to (n) Copy from (n) to (m) Select Create new RAID-1 (default). c. If a partition exists on either of the selected drives, a message states that the partition will be deleted.

d. Assign a RAID name by entering up to 15 alphanumeric characters, then press Enter. e. The following message appears:
Do you want to make this array bootable?

Click Yes to make the array bootable. f. The following message appears:
Create Array?

Click Yes. g. The following message appears:
Are you sure?

Click Yes, and then press Enter to create a RAID 1 array. After the array is created, the progress bar shows the status of the process. This process takes 4 to 8 hours to complete depending on the size of the source drive. h. When the process completes, exit from the SCSI Select Utility by pressing ESC. i. Reboot your system to complete the configuration process. You are now ready to use RAID 1. Start the SLES9 installation: a. Insert the SLES9 Service Pack 1 CD and reboot the system. b. After the CD boots, you might see the message:
You are about to install 32-bit software on a 64-bit computer.

If this message is displayed, press Enter to continue. c. Select Installation from the menu, but do not press Enter yet. Do not press Enter until step h. d. In the boot options box, you must enter special values based on your SCSI controller. See the Installing SUSE LINUX Enterprise Server 9 Products document for your specific model for details. The following example shows typical boot options:
insmod=a320raid brokenmodules=aic7xxx insmod=aic79xx

e. Press F2, and then select 1024 x 768.

f. Press F6. Text appears prompting you to have the driver-update disk ready. g. Insert the 320raid-3.00.050-1.sles9sp1.i586 update diskette. h. Press Enter to start the installation. i. You are prompted to choose the driver update medium. If it is not selected, choose Floppy, and then press Enter. j. k. l. m. A confirmation message states that the driver was updated. Remove the diskette from the drive. Press Enter. You are prompted to choose the drive medium update. Choose Back and press Enter. n. When prompted to insert CD 1, remove the service pack 1 CD and insert the first CD from the SLES9 core CD set, and then press Enter. o. After reading the license, press Enter to accept the license agreement. p. Select a language. Configure the installation settings: The next panel, Installation settings, displays a summary of the installation settings. You might need to change some of the settings as follows: a. b. c. d. e. f. g. Click Change, and then select Partitioning. Select Create custom partition setup, and then click Next. Select Custom partitioning – for experts, and then click Next. Delete any existing partitions. Select the RAID 1 device, and then click Create. Select Primary partition when prompted. Create a 10 GB partition for / with a Reiser File System: i. In the Format field, select Format and Reiser. ii. In the Size field, the Start cylinder value should be 0. iii. Enter +10GB in the End field. iv. Select / for mount point. On the expert partitioner panel, select Create. Select Primary partition when prompted. Create a swap partition that is equal in size to the amount of physical memory installed in the server. In this example, the server has 4 GB of memory: i. In the Format field, select Format and Swap. ii. In the Size field, the Start cylinder value should be 10241. iii. Enter +4GB in the End field. On the expert partitioner window, select Create. Select Primary partition when prompted. Use the remainder of the disk for /var: i. In the Format field, select Format and Reiser.

b. c. d.

e. f. g.

h. i. j. k. l. m. n. o. p. q. r. s. t. u. v.

ii. In the Size field, the Start cylinder value should be 14338. iii. Leave the default entry in the End field to use the rest of the disk. iv. Select /var for mount point. Click Next to return to the Installation Settings panel. Click Change, and then select Software. Select Default system, and then click Detailed selection. In the left pane, add c/c++ Compiler and Tool to the selected software selections. In the left pane, highlight LSB Runtime Environment, then in the right pane select Expect. In the left pane, highlight KDE Desktop Environment, then in the right pane deselect IBMJava2-JRE. Click Accept to return to the Installation Settings panel. Click Change, and then select Time zone. Set the time zone, date and time appropriately, and then click Accept to return to the Installation Settings panel. Click Change, and then select Default Runlevel. From the menu, choose 3: Full multiuser with network. Click OK to return to the Installation Settings panel. When you are satisfied with the installation settings, click Accept to start the installation. Click Yes, install. When prompted, insert the following CDs:

SLES9 Service-Pack Version 1 CD 1 SUSE LINUX Enterprise Server 9 CDs 1, 2, and 3 b. The system will automatically reboot. Perform post-installation configuration: When prompted enter a root password. The Network Configuration panel displays a summary of the network settings. You can change the settings as follows: a. b. c. d. e. f. g. h. i. j. k. Click Change, and then select Network Interfaces. Select IBM Ethernet controller, and then click Change. Select the device to be modified, and then click Edit. Select Static address setup, and then enter an IP address and subnet mask. Click Host name and name server, and then enter appropriate information for your environment. Click OK to return to the Network address setup panel. Click Routing, and enter appropriate information for your environment. . Click OK to return to the Network address setup panel. Click Next to return to the Network cards configuration overview panel. Click Finish to return to the Network configuration panel. Click Next.

l. When prompted to test the internet connection, select No, Skip This Test, and then click Next. m. The Service Configuration panel displays a summary of the services. You can change the settings as follows. i. ii. iii. iv. v. vi. vii. viii. ix. Click Change, and then select OpenLDAP Server. Select Disable Server. Click Next to return to the Service Configuration panel. Click Next. In the User Authentication Method panel, select Local, and then click Next. At the Add a new local User panel, add a user. At the Release notes panel, click Next. The Hardware configuration panel does not need to be modified. Click Next. At the Installation Complete panel, click Finish.

10. Set up NTP to keep the time in sync: To keep the time among servers and clients in sync, complete the following steps: b. Enter chkconfig xntpd on. c. Enter chkconfig --list xntpd. Ensure that run levels 2, 3, and 5 are on. d. Edit the /etc/ntp.conf file and add server <IP address>, where <IP address> is an NTP server. You can add multiple NTP server lines to increase reliability. e. Enter /etc/init.d/xntpd start . f. Enter /sbin/hwclock --systohc. g. Enter /sbin/hwclock --show. 11. Set up Ethernet bonding: h. From the console, stop networking:
/etc/init.d/network stop

i. SLES9 stores the Ethernet configuration file in /etc/sysconfig/network and names each file with the MAC address included in the name (for example, ifcfg-eth-id-00:0d:60:55:70:74). Remove any Ethernet configuration files from the /etc/sysconfig/nework directory:
j. cd /etc/sysconfig/network rm ifcfg-eth-id-*

k. Recreate a basic Ethernet configuration file for each Ethernet device:

Run yast2 at the console prompt. Use the up and down arrow keys to select Network Devices in the left pane of the YaST Control Center panel, and then press Enter to change focus to the right panel. iii. Use the up and down arrow keys to select Network Card, and then press Enter. iv. When the network cards have been discovered, the Network cards configuration panel appears. Press the Tab key until the focus changes to the field, Network cards to configure: Available are:. v. Use the up and down arrow keys to select the first available IBM Ethernet controller and press Enter. vi. In the Network address setup panel, ensure that the default setting Automatic address setup (via DHCP) is selected. Click Next, and then press Enter to accept the default and return to the Network cards configuration window. vii. Press the Tab key until the focus changes to the field, Network cards to configure: Available are: viii. Select the second IBM Ethernet controller, and then press Enter. ix. In the Network address setup panel, ensure that the default setting Automatic address setup (via DHCP) is selected. Click Next, and then press Enter to accept the default and return to the Network cards configuration panel. x. Click Finish, and then press Enter to configure the Ethernet devices. xi. At the YaST Control Center panel, press the Tab key to select Quit, and then press Enter to exit YaST. l. Modify the Ethernet configuration files generated by yast2:
cd /etc/sysconfig/network

i. ii.

There are two Ethernet configuration files: these files begin with ifcfg-ethid and end with the MAC address associated with each card. Edit each file and change the values of BOOTPROTO and STARTMODE to the following:
BOOTPROTO=’none’ STARTMODE=’off’

Do not modify UNIQUE or _nm_name, but remove any other lines. m. Create an ifcfg-bond0 file with the following content (change IPADDR, NETMASK and NETWORK to match your environment):
n. o. p. q. r. s. STARTMODE="onboot" BOOTPROTO="static" IPADDR="CHANGE" NETMASK="CHANGE" NETWORK="CHANGE" REMOTE_IPADDR=""

t. BONDING_MASTER="yes" u. BONDING_MODULE_OPTS="mode=active-backup miimon=100" v. BONDING_SLAVE0="eth0" BONDING_SLAVE1="eth1"

w. Restart networking:
/etc/init.d/network restart

x. Verify that Ethernet bonding is working: i. Run the ifconfig command and verify that bond0 exists and has the same IP address as eth0 and eth1. ii. Use the ping command to verify that you can reach another system on the network. iii. While the ping command is running, remove an Ethernet cable for several seconds and then plug it back in to verify that the ping command continues to succeed. Do the same for the next cable. 12. Create local users and groups for authentication: Note: This step assumes you are using local authentication. If local users and groups will be used to authenticate SAN File System administrative console access, create the users and groups.
groupadd Administrator groupadd Operator groupadd Backup groupadd Monitor useradd -g Administrator sfsadmin –m passwd sfsadmin

Create additional users for the Operator, Backup and Monitor groups if needed. 13. Verify IBMJava is not installed:
rpm –qa | grep IBMJava2-JRE

If it is installed, remove it:
rpm –e IBMJava-JRE

14. Install and start IBMsdd: Note: This step assumes you are using SDD. Install and start IBMsdd to manage multiple fibre-channel paths to IBM storage LUNs (LUNs have already been created and mapped to this host).

y. Go to http://www1.ibm.com/servers/storage/support/software/sdd/downloading.html, and then click Subsystem Device Driver downloads. z. Click Subsystem Device Driver for Linux. aa. Download SDD for the storage subsystem and OS you are using. bb. Install the SDD driver:
rpm –U IBMsdd-1.6.0.1-4.i686.sles9.rpm

cc. Configure SDD to restart during boot:
chkconfig –a sdd

dd. Start SDD:
sdd start

ee. Verify that SDD devices were configured:
lsvpcfg

15. The following steps should be completed after you have installed all servers. 16. Set up ssh keys to allow unchallenged root login between all servers. For the steps to do this, see Set up ssh keys. 17. Verify all servers discover the same number of LUNs: ff. Cat /proc/partitions on all servers and verify that the same number of LUNs have been discovered on all servers. (You can also use /proc/scsi/scsi and /proc/scsi/qla2xxx/* to verify that the servers see the same number of LUNs). gg. If you are running SDD, the lsvpcfg command can be used to show all configured LUNS, the number of paths to each LUN, and the LUN serial numbers. (You can also use the SDD command, datapath query device, to show the same information). 18. If an LDAP server will be used to authenticate Administrative users, verify the LDAP server responds to queries:
ldapsearch -x -h <ldap_IP_addr> -b O=<your_org> '(objectclass=*)'

19. Verify that the multi-path device driver restarts after a reboot (example: SDD):
datapath query device

20. Install IBMJava2-142-ia32-JRE:

hh. Insert and mount the SAN File System CD. ii. Install IBMJava2:
rpm -U /media/dvd/common/IBMJava2-142-ia32-JRE-1.4.21.0.i386.rpm

21. Verify the server meets hardware and software requirements: This step uses the install_sfs-package script to verify that the server meets hardware and software requirements. You need to complete this step for each server in the cluster, but you can do it from the master metadata server. Before starting the following steps, gather this information: CD mount point Server IP address System Management IP (RSA II) Authorized RSA User Authorized RSA Users Password a. Enter the verify command:
/media/dvd/SLES9/install_sfs-package-<version>.i586.sh –verify

b. Read and accept the license agreement. c. Answer the questions when prompted. d. If the software or hardware fails to meet minimum SAN File System requirements, review /tmp/tmvt.report for details. Note that when you run the verify command from a master metadata server for a subordinate server, the tmvt.report file is put in /root. 22. Create a configuration file: Complete this step only on the master metadata server.
b. /media/dvd/SLES9/install_sfs-package-2.2.2101.i586.sh --genconfig > /tmp/sfs.conf

a. Generate the configuration file:

c. Edit /tmp/sfs.conf and modify each instance of CHANGE to match your environment. If your environment will not be using an LDAP server to authenticate Administration console users, there is no need to modify the settings that start with LDAP. 23. Install SAN File System: Complete this step only on the master metadata server.

a. Install the package and load the cluster:
b. /media/dvd/SLES9/install_sfs-package-2.2.2101.i586.sh --loadcluster --sfsargs "-noldap -f /tmp/sfs.conf"

Note that the -noldap option is only for local authentication. c. Read and accept the license agreement. d. Answer the questions when prompted (values entered in the /tmp/sfs.conf file will come up as defaults). The server will display that it is up and running.

Sample installation: post server-installation steps This topic provides the steps to complete the sample installation of SLES9 and the SAN File System software on an IBM eServer xSeries 346 (xSeries 346).

Parent topic: Installing the operating system Parent topic: Reference Library | Support | Terms of use | Feedback (C) Copyright IBM Corporation 2003, 2005. All Rights Reserved. IBM TotalStorage SAN File System version 2.2.2