Skip to main content

RDAC Multipath Failover Driver for Linux OS

Installing the RDAC Driver


The following procedure describes how to install the RDAC driver for Red Hat RHEL 5, Red Hat Advanced Server 4, and Red Hat SuSE.



•Red Hat RHEL 5 package: rdac-LINUX-09.03.0B05.0042-source.tar.gz



•Red Hat Advanced Server 4 package: rdac-LINUX-09.03.0C02.0042-source.tar.gz



1. Unpack the source code using the tar command:



# tar -zxvf rdac-LINUX-xx.xx.xxxx.xxxx-source.tar.gz

where xx.xx.xxxx.xxxx is the RDAC version you downloaded.



The files are copied to the linuxrdac-xx.xx.xx.xx directory.



2. Change to the directory containing the unpacked files. For example,



# cd linuxrdac-09.03.C2.13

3. Remove any earlier version drivers that are in this directory by running the make clean command:





# make clean -r

make V=0 -C/lib/modules/2.6.18-8.el5xen/build M=/PTS/linuxrdac-09.03.C2.13 MODVERDIR=/lib/modules/2.6.18-8.el5xen/build/.tmp_versions SUBDIRS=/PTS/linuxrdac-09.03.C2.13 clean

make[1]: Entering directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

make[1]: Leaving directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

rm -f ./mpp_linux_sys_headers/mppLnx26p_spinlock.h mppLnx_Spinlock_Size

rm -f Module.symvers

rm -f mppUtil

rm -f genuniqueid

#







4. Compile all driver modules and utilities by running the make command:





# make

make V=0 -C/lib/modules/2.6.18-8.el5xen/build M=/PTS/linuxrdac-09.03.C2.13 MODVERDIR=/lib/modules/2.6.18-8.el5xen/build/.tmp_versions SUBDIRS=/PTS/linuxrdac-09.03.C2.13 modules

make[1]: Entering directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

CC [M] /PTS/linuxrdac-09.03.C2.13/MPP_hba.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_upper.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_sysdep.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppCmn_s2tos3.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppCmn_SysInterface.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhbamisc.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhbatask.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhba.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhbaproc.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhbalib.o

CC [M] /PTS/linuxrdac-09.03.C2.13/mppLnx26p_vhbaio.o

LD [M] /PTS/linuxrdac-09.03.C2.13/mppUpper.o

LD [M] /PTS/linuxrdac-09.03.C2.13/mppVhba.o

Building modules, stage 2.

MODPOST

CC /PTS/linuxrdac-09.03.C2.13/mppUpper.mod.o

LD [M] /PTS/linuxrdac-09.03.C2.13/mppUpper.ko

CC /PTS/linuxrdac-09.03.C2.13/mppVhba.mod.o

LD [M] /PTS/linuxrdac-09.03.C2.13/mppVhba.ko

make[1]: Leaving directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

make V=0 -C/lib/modules/2.6.18-8.el5xen/build M=/PTS/linuxrdac-09.03.C2.13 MODVERDIR=/lib/modules/2.6.18-8.el5xen/build/.tmp_versions SUBDIRS=/PTS/linuxrdac-09.03.C2.13 modules

make[1]: Entering directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

Building modules, stage 2.

MODPOST

make[1]: Leaving directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

gcc -D__KERNEL__ -I/lib/modules/2.6.18-8.el5xen/build/include mppLnx26p_spinlock_size.c -o mppLnx_Spinlock_Size







Sample output continued from previous page



gcc -I/PTS/linuxrdac-09.03.C2.13 -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_headers/ -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_sys_headers/ -c ./utility/mppUtil.c -o mppUtil.o

/bin/bash ./genfileattributes bld

gcc -I/PTS/linuxrdac-09.03.C2.13 -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_headers/ -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_sys_headers/ -c ./utility/mppUtil26p_sysdep.c -o mppUtilSysdep.o

gcc mppUtil.o mppUtilSysdep.o -o mppUtil

gcc -o genuniqueid genuniqueid.c







5. Uninstall any existing RDAC drivers using the make uninstall command:



# make uninstall

MPP driver is currently not installed on the system

[root@va64-x4100d-sca11 linuxrdac-09.03.C2.13]

6. Install the new RDAC driver using the make install command. This command:



■Copies the driver modules to the kernel module tree.



■Builds the new RAMdisk image (mpp-‘uname -r‘.img) which includes the RDAC driver modules and all driver modules that are needed at boot time.





# make install

make V=0 -C/lib/modules/2.6.18-8.el5xen/build M=/PTS/linuxrdac-09.03.C2.13 MODVERDIR=/lib/modules/2.6.18-8.el5xen/build/.tmp_versions SUBDIRS=/PTS/linuxrdac-09.03.C2.13 modules

make[1]: Entering directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

Building modules, stage 2.

MODPOST

make[1]: Leaving directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

make V=0 -C/lib/modules/2.6.18-8.el5xen/build M=/PTS/linuxrdac-09.03.C2.13 MODVERDIR=/lib/modules/2.6.18-8.el5xen/build/.tmp_versions SUBDIRS=/PTS/linuxrdac-09.03.C2.13 modules

make[1]: Entering directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

Building modules, stage 2.

MODPOST

make[1]: Leaving directory ‘/usr/src/kernels/2.6.18-8.el5-xen-x86_64’

/bin/bash ./genfileattributes bld

gcc -I/PTS/linuxrdac-09.03.C2.13 -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_headers/ -I/PTS/linuxrdac-09.03.C2.13/mpp_linux_sys_headers/ -c ./utility/mppUtil26p_sysdep.c -o mppUtilSysdep.o

gcc mppUtil.o mppUtilSysdep.o -o mppUtil

Checking Host Adapter Configuration...

Unsupported Host Adapter Model: Product ID fc10(rev01)

Unsupported Host Adapter Model: Product ID fc10(rev01)

Detected 2 Emulex Host Adapter Port(s) on the system

Detected 1 LSI Host Adapter Port(s) on the system

Detected 2 QLogic Host Adapter Port(s) on the system

Host Adapters from different supported vendors co-exists on your system.

Unsupported model from Vendor Emulex exists.

Please make sure that only one supported model of HBA is connected to Storage Array.







7. Type yes when you are prompted to continue:





Do you want to continue (yes or no) ? yes

Please wait while we modify the system configuration files.

Your kernel version is 2.6.18-8.el5xen

Preparing to install MPP driver against this kernel version...

Generating module dependencies...

Warning: Duplicate module options detected.

Option in /etc/modprobe.conf ( max_luns=256 ) takes precedence over MPP default setting ( max_luns=512 ).

Creating new MPP initrd image...

You must now edit your boot loader configuration file, /boot/grub/menu.lst, to

add a new boot menu, which uses mpp-2.6.18-8.el5xen.img as the initrd image.

Now Reboot the system for MPP to take effect.

The new boot menu entry should look something like this (note that it may

vary with different system configuration):



...



title Red Hat Linux (2.6.18-8.el5xen) with MPP support

root (hd0,5)

kernel /vmlinuz-2.6.18-8.el5xen ro root=LABEL=RH9

initrd /mpp-2.6.18-8.el5xen.img

...

MPP driver package has been successfully installed on your system.







8. Follow the on-screen instructions to modify the grub.conf file. Change the module and initrd names as follows:





Original Name

Revised Name



module /initrd-2.6.18-8.el5xen.img

module /mpp-2.6.18-8.el5xen.img



initrd /initrd-2.6.18-8.el5.img

initrd /mpp-2.6.18-8.el5xen.img







The content of the grub.conf file looks similar to the following. (The revised module and initrd names are shown in bold text.)





# boot=/dev/sda

default=0

timeout=5

title Red Hat Enterprise Linux Server (2.6.18-8.el5xen)

root (hd0,0)

kernel /xen.gz-2.6.18-8.el5 com1=9600n8

module /vmlinuz-2.6.18-8.el5xen ro root=LABEL=/ console=ttyS0,9600n8 rhgb quiet

module /mpp-2.6.18-8.el5xen.img

title Red Hat Enterprise Linux Server-base (2.6.18-8.el5)

root (hd0,0)

kernel /vmlinuz-2.6.18-8.el5 ro root=LABEL=/ console=ttyS0,9600n8 rhgb quiet

initrd /mpp-2.6.18-8.el5xen.img







9. Reboot the Linux server.



# reboot

Comments

  1. AnurajaJune 26, 2012 at 11:39 AM

    i want to install rdac driver. after compile source, by using "make". we have to install "make install" or what have to do.

    ■Copies the driver modules to the kernel module tree.

    ■Builds the new RAMdisk image (mpp-‘uname -r‘.img) which includes the RDAC driver modules and all driver modules that are needed at boot time. this is unable to understand explain clearly. we have to ramdisk ? my mail id is jvaurajecil@gmil.com
    jvanuraja_2007@yahoo.co.in

    ReplyDelete

Post a Comment

Popular posts from this blog

Six Linux softphone's list

VoIP has improved a lot since its first days, today a lot of multinational business are using it as a reliable way to keep stay in touch. With more and more telecommuters, and business man working, and with cell phone roaming costs still high, VoIP is a real option for both big and small corporations. And when you talk to a CFO about investing to save costs, you usually will see the checkered flag for your project. Most of these projects will involve IP phones or ATAs, but you may use softphones too, which are very convenient for the traveler guy, here we will review some of the soft phones available for Linux. Linphone Linphone is a mature piece of software, it uses SIP, for voice and video over IP, it can work as a stand alone application, and you can call other sip enabled devices just entering its ips on the dial window of Linphone, or you can configure it to use an Asterisk PBX. There are binary packages for the most common distros, so try to install it using you pa...
4 comments
Read more

How to configure multipath Debian CentOS for IBM Storage

This detailed how to guides to achieve high availability and performance on Debian and CentOS for accessing storage space at IBM DS8300 Data Storage Systems. Tested on Debian GNU/Linux 5.x Lenny 64 bits and CentOS 5.3 64 bits running on 8 cores blades, with Host Bus Adapters Qlogic and Emulex Light Pulse Fiber Channel in deployed systems at SERPRO . Observations showed that Debian Lenny has the best performance, for our app load profile and hardware. Also, there are listed a number of previously not clearly documented critical pitfalls to avoid. STUDY whole articles, hints, implications, and cited resources before planning your deployment. Every detail matters . Before start, you must have LUNs at IBM DS8300 storage configured for high availability and performance as explained at the article How to configure maximum performance storage space for Debian GNU/Linux on IBM DS 8300 Data Storage Systems . Multipath and storage basic concepts In order t...
Post a Comment
Read more

Configuring the virtual path devices

We recommend that you start with a "fresh" disk configuration, so it is a good idea to delete all previously configured FC adapters and their child (disk) devices. On node1, we checked which disks are still defined: {node1:root}/-> lspvhdisk0 0022be2ab1cd11ac rootvg activehdisk1 0022be2a3d02ead0 Nonehdisk2 0022be2a4cbbafd8 Nonehdisk3 none NoneThese are the internal SCSI disk drives {node1:root}/-> lscfg grep disk+ hdisk3 U1.9-P2/Z2-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk2 U1.9-P2/Z1-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk1 U1.9-P1/Z2-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk0 U1.9-P1/Z1-A8 16 Bit LVD SCSI Disk Drive (36400 MB)In order to include the ESS disks, run the configuration manager on each node: {node1:root}/-> cfgmgr -vSince ESS was configured with two host paths for each node (node1a and node1b), this results in two hdisks on the nodes. Actually, those two logical hdisks represent the same physical disk, accessed via the two ...
Post a Comment
Read more