xSeries 346 installation upgrade procedure

This topic presents details on installing the xSeries® 346.

Context

The xSeries 346 is functionally equivalent to the xSeries 345, but there are differences in physical layout and operating-system installation, as described in this topic.

RSA II connectivity
The connectivity of the xSeries 346 differs from the xSeries 345 in the following ways, and as shown in Figure 1:
  • The xSeries 346 uses an RSA II Slimline adapter that is not on the PCI bus, but is instead attached to an internal system connector. As such, there is no card edge for the RSA II, as there is in the xSeries 345. Instead, the RSA II Ethernet and ASM connections are positioned on the back panel of the xSeries 346.
  • The external USB connection is not required for the xSeries 346, as that connection is made internally.
  • There is no VGA connector specific to the RSA II, as there is on the xSeries 345. Use the regular video port on the left side of the back panel.
  • The ASM ports are located in the center of the back panel of the xSeries 346 (stacked vertically). You can use these two ASM ports like the ports on the breakout cable (dongle) of the xSeries 345 RSA II. To do this, daisy chain the ports together with other metadata servers as described in Figure 1.
  • The RSA II Ethernet is located directly to the right of the regular system Ethernet ports.
  • All other functions and configuration steps of the RSA II Slimline are the same as those for the regular RSA II.
Figure 1. Back plane of the xSeries 346This figure shows the back plane of the xSeries 346.
Onboard Ethernet adapters are Broadcom and require changes to SLES 8 installation
The onboard network adapters for the xSeries 346 are Broadcom NetXtreme Gigabit, instead of the Intel™ E1000 in the xSeries 345. These adapters require some new Linux™ drivers that are not a part of the default SLES 8 Service Pack 3 installation. When installing the xSeries 346, take note of the following changes to the xSeries 345 installation steps presented in Installing the operating system:
  1. Because networking is not available immediately after SLES 8 installation, you need to put the required drivers and rpms onto a CD. Before starting the metadata server installation procedure, obtain the following files and burn them onto a CD. In this procedure, this CD is referred to as the Driver/Kernel CD:
    • From SUSE:
      kernel-source-2.4.21-231.i586.rpm
      k_smp-2.4.21-231.i586.rpm
    • From Broadcom:
      bcm5700-7.3.5-1.src.rpm
      The Broadcom Web site is located at:
      http://www.broadcom.com/drivers/driver-sla.php?driver=570x-Linux
      Note that the download file is a zip file. You must open that zip file and extract the rpm contained in Server/Linux/Driver/bcm5700-7.3.5-1.src.rpm.
  2. Disconnect all SAN (Fibre Channel) cables from the metadata server.
    Attention: Failure to perform this step can result in loss of SAN File System metadata.
  3. Insert the SUSE Linux Enterprise Server SP3 CD 1 into the CD-ROM drive and reboot the engine.
  4. When the install program displays Make sure CD 1 is in the drive!, eject the SUSE Linux Enterprise Server SP3 CD 1 and insert the standard SLES 8 CD 1.
  5. At this point, continue with step 3 in Installing the operating system and continue through Apply United Linux Service Pack 3 (SP3) updates.
  6. After applying the SP3 updates in Apply United Linux Service Pack 3 (SP3) updates, upgrade the SAN File System 2.2 required kernel by completing these steps:
    1. Insert the Driver/Kernel CD that was prepared earlier into the CD drive and enter the following commands (ignore any error messages about an inability to delete a directory):
      mount /media/cdrom  
      cd /media/cdrom 	
      cp kernel-source-2.4.21-231.i586.rpm /tmp
      cp k_smp-2.4.21-231.i586.rpm /tmp 
      cp bcm5700-7.3.5-1.src.rpm /tmp
      cd
      umount /media/cdrom 
      rpm -e kernel-source-2.4.21-138
      rpm -ivh /tmp/kernel-source-2.4.21-231.i586.rpm
      rpm -Uvh /tmp/k_smp-2.4.21-231.i586.rpm
      depmod -a    		
    2. Remove the CD from the CD drive.
    3. Reboot.
  7. You can now install the Broadcom driver by entering the following commands:
    cd /usr/src/linux 
    make mrproper 
    cp /boot/config-2.4.21-231-smp .config 
    make oldconfig 
    make dep
    rpm -ivh /tmp/bcm5700-7.3.5-1.src.rpm 
    cd /usr/src/packages
    rpm -bb SPECS/bcm5700.spec 
    rpm -ivh --force RPMS/i386/bcm5700-7.3.5-1.i386.rpm
  8. Edit the /etc/modules.conf file and change these lines (near the beginning of the file)
    alias eth0 off
    alias eth1 off
    to
    alias eth0 bcm5700
    alias eth1 bcm5700
  9. Set up the dependency descriptions for the loadable kernel modules by creating the makefile and updating the kernel:
    depmod -a
  10. After you have completed the installation of the driver, reboot.
After the reboot, the networking is operational. At this point, continue with the remaining SAN File System setup steps starting with Installing prerequisite software on the metadata server engine.
Note: Repeat these steps for all xSeries 346 metadata servers.

Postrequisites

Parent topic: Metadata server engine setup

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2