Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

download Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

of 3

Transcript of Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

  • 8/10/2019 Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

    1/3

    TM506LNX4ORCL10RWP TimeMachineConfiguration on OracleRACforRed HatLinux page1 of 3

    Thefollowing proceduredetailshowto setup acontrolprocessformultiplenodesin an OracleRACLinux clusterto run allTimeMachineoperationson each nodesimultaneously. Afterfollowing thesestepsauserwillbeableto enableordisabletheirvirtualclock on each machinewith onecommand.

    Step1:Enablershandthexinetddaemonandconfigureitto restartautomatically during eachsystemreboot.

    Ifxinetdisnotenabled on yoursystem, followtheappropriatemethod listed belowforyouroperating systemtype.

    Notethatwhen anodeisrebooted, thexinetdservicemustberestarted.

    Enabling xinetdandrshonRedHat4

    To enablexinetdon Red Hatversion 4, performthefollowing steps.

    1.

    Prepare the Linux host to provide rsh capability:a.

    Check that the rsh daemon is installed, using:

    chkconfig --list | grep rsh

    or

    rpm -qa | grep rsh-server

    b.

    If the rsh daemon does not exist, install the rsh server RPM package, (rsh-server-0.17-

    17.i386.rpm).

    c. Edit the following configuration files:

    /etc/xinetd.d/rexec with DISABLE = NO

    /etc/xinetd.d/rsh with DISABLE = NO

    /etc/xinetd.d/rlogin with DISABLE = NO

    2.

    If the /etc/securetty file exists, add the following lines to the end of the file.

    rsh

    rexec

    rlogin

    3.

    Update the following PAM-related files to allow remote logins from other systems:

    a. Edit the /etc/pam.d/rlogin file and comment out the following line by inserting a pound

    sign (#):

    # auth required /lib/security/pam_securetty.so

    b. Edit the /etc/pam.d/rsh file and change the following line:

    auth required /lib/security/pam_rhosts_auth.so

    to

    auth sufficient /lib/security/pam_rhosts_auth.so

    4. Restart the xinetd service using /etc/rc.d/init.d/xinetd restart.

  • 8/10/2019 Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

    2/3

    TM506LNX4ORCL10RWP TimeMachineConfiguration on OracleRACforRed HatLinux page2 of 3

    Step2:UserIDsonremotenodes

    On each remotenode, thesystemadministratormustsetup auserID, otherthan arootID, foreach useron each remotenodewho willbeexecuting serialorparallel. Both theusernameand userIDmustbethesameon allnodes. Also, theusermustbeamemberofthesamenamed group on thehomenodeand theremotenodes.

    Example:[oracle@spb10 ~]$ id

    uid=500(oracle)gid=501(dba)groups=501(dba)

    Step3:Userauthorization

    Each nodeneedsto besetup such thateach userid isauthorized to accessthatnodeorremotelink fromtheinitiating homenode. Edittheusers.rhostsfileon each nodeto specify thisusersauthorization to run commandsfromothernodesin thecluster.

    Exampleoffile/home/oracle/.rhosts(thisfilecanandshouldbethesameoneachnode. Inthisexampletherearetwo node, spb10 &spb15)

    spb10-intoraclespb15-intoraclespb10 oraclespb15 oracle

    Step4:Testthesetup

    Afterfollowing theabovestepson each nodein theclusterformthecommand lineon onenodetestthesetup using rsh to runacommand on theothernode:

    Example:(Thisexamplewasran frommachinespb10 calling outto machinespb15)[oracle@spb10 ~]$ rshspb15 -loraclelsconnectto address15.170.177.15:ConnectionrefusedTrying krb4 rsh...connectto address15.170.177.15:Connectionrefusedtrying normalrsh(/usr/bin/rsh)file1.txtfoo.barhello.world

    [oracle@spb10 ~]$

  • 8/10/2019 Enabling Xinetd and Rsh TM Linux Oracle RAC Cluster

    3/3

    TM506LNX4ORCL10RWP TimeMachineConfiguration on OracleRACforRed HatLinux page3 of 3

    Step5:Creating thecontrolscript

    Next create an editable script fi le that wi ll allow all the user s Time Machine commands tobeexecutedoneachnode.Thefollowing isanexampleofa scriptthatwilldeterminewhichmachineitisbeing calledfrom, executethepassed-incommandontheremotenodevia remote-shell(rsh)thenimmediately executethesamecommandonthelocalnode.

    # CLUSTERTM# ThisLinux shellscriptfiletakesin theentirecommand linestring "$@"and passesitto thedefined RSH# hostsand then executesthesame# command on thelocalhost. Thisfilemustbeexecuted fromthesamenetwork accounton thelocalhostason theremotehost/s.## Asthiswasdesigned forclustermanagementthisfileneedsto residein theusershomedirectory on allmachines## Exampleofuse: [oracle@spb15 ~]$ clusterm tmuser -a -u 500 -x 022812552010 -f## Used asabovetheremotemachineand localhostwillhaveavirtualclock foruseroraclesetto 12:55, Feb 28th 2010.

    case$HOSTNAMEinspb10.usa.hp.com)rshspb15.usa.hp.com-loracle$@;echo ------------Nowexecuting commandlocally------------------------$@;;

    spb15.usa.hp.com)rshspb10.usa.hp.com-loracle$@;echo ------------Nowexecuting commandlocally------------------------$@;;

    esac