Anda di halaman 1dari 14

1. 1.

SUN CLUSTER INSTALLATION PROCEDURE Installation on both nodes

Installation on pr1r3db (Node 1) # cd /cdrom/cdrom0 # ls Copyright License.txt # cd Sun* # ls Sol_9 Sol_10 # cd Sol_10 # cd Tools # ./scinstall *** Main Menu *** Please select from one of the following (*) options: * 1) Establish a new cluster using this machine as the first node * 2) Add this machine as a node in an established cluster 3) Configure a cluster to be JumpStarted from this install server 4) Add support for new data services to this cluster node 5) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 1 *** Establishing a New Cluster *** This option is used to establish a new cluster using this machine as the first n ode in that cluster. Once the cluster framework software is installed, you will be asked for the name of the cluster. Then, sccheck(1M) is run to test this machine for basic Sun Clu ster pre-configuration requirements. After sccheck(1M) passes, you will be asked for the names of the other nodes whi ch will initially be joining that cluster. In addition, you will be asked to pro vide certain cluster transport configuration information. Press Ctrl-d at any time to return to the Main Menu. Do you want to continue (yes/no) [yes]? yes >>> Software Package Installation <<< Installation of the Sun Cluster framework software packages will take a few minu tes to complete. Is it okay to continue (yes/no) [yes]? yes ** Installing SunCluster 3.2 framework ** SUNWscr.....done SUNWscu.....done SUNWscnm....done SUNWscdev...done SUNWscgds...done

README

SunCluster_3.2 index.html

SUNWscman...done SUNWscsal...done SUNWscsam...done SUNWscvm....done SUNWmdm.....done SUNWscva....done SUNWscvr....done SUNWscvw....done SUNWfsc.....done SUNWfscvw...done SUNWjsc.....done SUNWjscman..done SUNWjscvw...done SUNWkscvw...done SUNWcsc.....done SUNWcscvw...done SUNWhscvw...done Hit ENTER to continue: >>> Cluster Name <<< Each cluster has a name assigned to it. The name can be made up of any character s other than whitespace. It may be up to 256 characters in length. And, you may want to assign a cluster name which will be the same as one of the failover logi cal host names in the cluster. Create each cluster name to be unique within the namespace of your enterpris e. What is the name of the cluster you want to establish? pr1r3db This step runs sccheck(1M) to verify that certain basic hardware and software pr e-configuration requirements have been met. If sccheck(1M) detects potential pro blems with configuring this machine as a cluster node, a list of warnings is pri nted. Hit ENTER to continue: Running sccheck ... done All sccheck tests passed. Hit ENTER to continue: >>> Cluster Nodes <<< This release of Sun Cluster supports a total of up to 16 nodes. Please list the names of the other nodes planned for the initial cluster configu ration. List one node name per line. When finished, type Control-D: Node name: pr1r3db Node name (Ctrl-D to finish): ^D This is the complete list of nodes: prdpsb1 prdpsci1 Is it correct (yes/no) [yes]? yes

>>> Authenticating Requests to Add Nodes <<< Once the first node establishes itself as a single node cluster, other nodes att empting to add themselves to the cluster configuration must be found on the list of nodes you just provided. The list can be modified once the cluster has been established using scconf(1M) or other tools. By default, nodes are not securely authenticated as they attempt to add themselv es to the cluster configuration. This is generally considered adequate, since no des which are not physically connected to the private cluster interconnect will never be able to actually join the cluster. However, DES authentication is a vailable. If DES authentication is selected, you must configure all necessary en cryption keys before any node will be allowed to join the cluster (see keyserv(1 M), publickey(4)). Do you need to use DES authentication (yes/no) [no]? no >>> Network Address for the Cluster Transport <<< The private cluster transport uses a default network address of 172.16.0.0. But, if this network address is already in use elsewhere within your enterprise, you may need to select another address from the range of recommended private addres ses. If you do select another network address, please bear in mind that the Sun Clust ering software requires that the rightmost two octets always be zero. The default netmask is 255.255.0.0; you may select another netmask, as long as i t minimally masks all bits given in the network address and does not contain any "holes". Is it okay to accept the default network address (yes/no) [yes]? yes Is it okay to accept the default netmask (yes/no) [yes]? yes >>> Point-to-Point Cables <<< The two nodes of a two-node cluster may use a directly-connected interconnect. T hat is, no cluster transport junctions are configured. However, when there are greater than two nodes, this interactive form of scinsta ll assumes that there will be exactly two cluster transport junctions. Does this two-node cluster use transport junctions (yes/no) [yes]? no >>> Cluster Transport Adapters and Cables <<< You must configure at least two transport adapters on each node which serve as c onnection points to the private cluster transport. More than two connection poin ts are allowed, but this interactive form of scinstall assumes exactly two. Note that interactive scinstall does not allow you to specify any special transp ort adapter properties settings. If your adapters have special properties which must be set, you may need to use non-interactive scinstall by specifying a compl ete set of command line options. For more information, please refer to the man p ages for your adapters in the scconf_transp_adap family of man pages (e.g.,sccon f_transp_adap_hme(1M)). Hit ENTER to continue:

Select the first cluster transport adapter to use: 1) 2) 3) 4) 5) nxge0 nxge1 nxge2 nxge3 Other

Option: 1 Adapter "nxge0" is an ethernet adapter. Searching for any unexpected network traffic on "nxge0" ... done Verification completed. No traffic was detected over a 10 second sample peri od. All transport adapters support the "dlpi" transport type. Ethernet adapters are supported only with the "dlpi" transport; however, other adapter types may suppo rt other types of transport. For more information on which transports are suppor ted with which adapters, please refer to the scconf_transp_adap family of man pa ges (scconf_transp_adap_ce(1M), ...). The "dlpi" transport type will be set for this cluster. Select the second cluster transport adapter to use: 1) 2) 3) 4) nxge 1 nxge 2 nxge 3 Other

Option: 2 Adapter " nxge 2" is an ethernet adapter. Searching for any unexpected network traffic on " nxge 2" ... done Verification completed. No traffic was detected over a 10 second sample period . >>> Global Devices File System <<< Each node in the cluster must have a local file system mounted on /global/.d evices/node@<nodeID> before it can successfully participate as a cluster member. Since the "nodeID" is not assigned until scinstall is run, scinstall will set t his up for you. However, in order to do this, you must supply the name of either an already-mounted file system or raw disk partition at this time. This file system or partition should be at least 512 MB in size. If an already-mounted file system is used, the file system must be empty. If a r aw disk partition is used, a new file system will be created for you. The default is to use /globaldevices. Is it okay to use this default (yes/no) [yes]? yes >>> Automatic Reboot <<<

Once scinstall has successfully installed and initialized the Sun Cluster softwa re for this machine, it will be necessary to reboot. After the reboot, this machine will be established as the first node in the new cluster. Do you want scinstall to reboot for you (yes/no) [yes]? no You will need to manually reboot this node in "cluster mode" after scinstall suc cessfully completes. Hit ENTER to continue: >>> Confirmation <<< Your responses indicate the following options to scinstall: scinstall -ik \ -C bwcluster \ -F \ -T node=pdbdrdb1,node=pdbdrci1,authtype=sys \ -A trtype=dlpi,name=nxge0 -A trtype=dlpi,name=nxge1 \ -B type=direct Are these the options you want to use (yes/no) [yes]? yes Do you want to continue with the install (yes/no) [yes]? yes Checking device to use for global devices file system ... done Initializing Initializing Initializing Initializing cluster name to "prdpsdbl" ... done authentication options ... done configuration for adapter "nxge0" ... done configuration for adapter "nxge1" ... done

Setting the node ID for "prdpsdbl" ... done (id=1) Setting the major number for the "did" driver ... done "did" driver major number set to 300 Checking for global devices global file system ... done Updating vfstab ... done Verifying that NTP is configured ... done Installing a default NTP configuration ... done Please complete the NTP configuration after scinstall has finished. Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done Adding the "cluster" switch to "hosts" in nsswitch.conf ... done Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done Verifying that power management is NOT configured ... done Unconfiguring power management ... done /etc/power.conf has been renamed to /etc/power.conf.072103025119 Power management is incompatible with the HA goals of the cluster. Please do not attempt to re-configure power management. Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

The "local-mac-address?" parameter setting has been changed to "true". Ensure network routing is disabled ... done Network routing has been disabled on this node by creating /etc/notrouter. Having a cluster node act as a router is not supported by Sun Cluster. Please do not re-enable network routing. Hit ENTER to continue: *** Main Menu *** Please select from one of the following (*) options: 1) Establish a new cluster using this machine as the first node 2) 3) 4) 5) ?) q) Add this machine as a node in an established cluster Configure a cluster to be JumpStarted from this install server Add support for new data services to this cluster node Print release information for this cluster node Help with menu options Quit

* * * *

Option: q Log file - /var/cluster/logs/install/scinstall.log.856 Apply the recommended Sun Cluster Reboot patches & reboot the system in cluster mode. I.e. init 6 Installation on pr1r3ci (Node 2) After the pr1r3db is started normally in cluster mode,start installation of clu ster pr1r3dci as follows : #. /scinstall *** Main Menu *** Please select from one of the following (*) options: * 1) Establish a new cluster using this machine as the first node * 2) Add this machine as a node in an established cluster 3) Configure a cluster to be JumpStarted from this install server 4) Add support for new data services to this cluster node 5) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 2 *** Adding a Node to an Established Cluster *** This option is used to add this machine as a node in an already established clus ter. If this is an initial cluster install, there may only be a single node whic h has established itself in the new cluster. Once the cluster framework software is installed, you will be asked to provide b oth the name of the cluster and the name of one of the nodes already in the clus ter. Then, sccheck(1M) is run to test this machine for basic Sun Cluster pre-con

figuration requirements. After sccheck(1M) passes, you may be asked to provide certain cluster transport configuration information. Press Ctrl-d at any time to return to the Main Menu. Do you want to continue (yes/no) [yes]? yes >>> Software Package Installation <<< Installation of the Sun Cluster framework software packages will take a few minu tes to complete. Is it okay to continue (yes/no) [yes]? yes ** Installing SunCluster 3.2 framework ** SUNWscr.....done SUNWscu.....done SUNWscnm....done SUNWscdev...done SUNWscgds...done SUNWscman...done SUNWscsal...done SUNWscsam...done SUNWscvm....done SUNWmdm.....done SUNWscva....done SUNWscvr....done SUNWscvw....done SUNWfsc.....done SUNWfscvw...done SUNWjsc.....done SUNWjscman..done SUNWjscvw...done SUNWkscvw...done SUNWcsc.....done SUNWcscvw...done SUNWhscvw...done Hit ENTER to continue: >>> Sponsoring Node <<< For any machine to join a cluster, it must identify a node in that cluster willi ng to "sponsor" its membership in the cluster. When configuring a new cluster, t his "sponsor" node is typically the first node used to build the new cluster. Ho wever, if the cluster is already established, the "sponsoring" node can be a ny node in that cluster. Already established clusters can keep a list of hosts which are able to configur e themselves as new cluster members. This machine should be in the join list of any cluster which it tries to join. If the list does not include this machine, y ou may need to add it using scconf(1M) or other tools. And, if the target cluster uses DES to authenticate new machines attempting to c onfigure themselves as new cluster members, the necessary encryption keys must b

e configured before any attempt to join. What is the name of the sponsoring node? pr1r3db >>> Cluster Name <<< Each cluster has a name assigned to it. When adding a node to the cluster, you m ust identify the name of the cluster you are attempting to join. A sanity check is performed to verify that the "sponsoring" node is a member of that cluster. What is the name of the cluster you want to join? hmel-prod-ecc Attempting to contact " hmel-prod-ecc" ... done Cluster name " hmel-prod-ecc " is correct. Hit ENTER to continue: >>> Check <<< This step runs sccheck(1M) to verify that certain basic hardware and software pr e-configuration requirements have been met. If sccheck(1M) detects potential pro blems with configuring this machine as a cluster node, a list of warnings is pri nted. Hit ENTER to continue: Running sccheck ... done All sccheck tests passed. Hit ENTER to continue: >>> Autodiscovery of Cluster Transport <<< If you are using ethernet adapters as your cluster transport adapters, autodisco very is the best method for configuring the cluster transport. Do you want to use autodiscovery (yes/no) [yes]? yes Probing......... The following connections were discovered: pr1r3db:nxge0 pr1r3db: nxge 0 pr1r3ci: nxge 1 - pr1r3ci nxge 2 Is it okay to add these connections to the configuration (yes/no) [yes]? Ye s

>>> Global Devices File System <<< Each node in the cluster must have a local file system mounted on /global/.dev ices/node@<nodeID> before it can successfully participate as a cluster member. S ince the "nodeID" is not assigned until scinstall is run, scinstall will set thi

s up for you. However, in order to do this, you must supply the name of either a n already-mounted file system or raw disk partition at this time. This file syst em or partition should be at least 512 MB in size. If an already-mounted file system is used, the file system must be empty. If a r aw disk partition is used, a new file system will be created for you. The default is to use /globaldevices02. Is it okay to use this default (yes/no) [yes]? yes >>> Automatic Reboot <<< Once scinstall has successfully installed and initialized the Sun Cluster softwa re for this machine, it will be necessary to reboot. The reboot will cause this machine to join the cluster for the first time. Do you want scinstall to reboot for you (yes/no) [yes]? no You will need to manually reboot this node in "cluster mode" after scinstall suc cessfully completes. Hit ENTER to continue: >>> Confirmation <<< Your responses indicate the following options to scinstall: scinstall -ik \ -C bwcluster\ -N pdbpsdb1\ -A trtype=dlpi,name=ce0 -A trtype=dlpi,name=ce1 \ -B type=direct \ -m endpoint=:nxge0,endpoint=pdbdrdb1:nxge0 -m endpoint=:nxge1,endpoint=pdbdrdb1:nxge1 Are these the options you want to use (yes/no) [yes]? yes Do you want to continue with the install (yes/no) [yes]? yes Checking device to use for global devices file system ... done Adding Adding Adding Adding Adding node "pdbdrci1" to the cluster configuration ... done adapter "ce0" to the cluster configuration ... done adapter "ce1" to the cluster configuration ... done cable to the cluster configuration ... done cable to the cluster configuration ... done

Copying the config from "prdpsdb1" ... done Setting the node ID for "prdpsci1" ... done (id=2) Setting the major number for the "did" driver ... Obtaining the major number for the "did" driver from "phys-iffknd01" ... done "did" driver major number set to 300 Checking for global devices global file system ... done Updating vfstab ... done Verifying that NTP is configured ... done

Installing a default NTP configuration ... done Please complete the NTP configuration after scinstall has finished. Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done Adding the "cluster" switch to "hosts" in nsswitch.conf ... done Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done Verifying that power management is NOT configured ... done Unconfiguring power management ... done /etc/power.conf has been renamed to /etc/power.conf.072103042755 Power management is incompatible with the HA goals of the cluster. Please do not attempt to re-configure power management. Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done The "local-mac-address?" parameter setting has been changed to "true". Ensure network routing is disabled ... done Network routing has been disabled on this node by creating /etc/notrouter. Having a cluster node act as a router is not supported by Sun Cluster. Please do not re-enable network routing. Hit ENTER to continue: *** Main Menu *** Please select from one of the following (*) options: 1) 2) 3) 4) 5) ?) q) Establish a new cluster using this machine as the first node Add this machine as a node in an established cluster Configure a cluster to be JumpStarted from this install server Add support for new data services to this cluster node Print release information for this cluster node Help with menu options Quit

* * * *

Option: q Log file - /var/cluster/logs/install/scinstall.log.856 Reboot the system in cluster mode. I.e. init 6 1.2 Adding Quorum Device

To complete this procedure, identify a disk drive by its device ID (DID), which is shared by the nodes. 1. Login as root on sc1host1 2. Run scsetup utility i. #scsetup ii. The main menu will be displayed 3. To work with quorum devices, type 1 (Quorum). The Quorum Menu is displayed. 4. To add a quorum device, type 1 (Add a quorum disk). Follow the instructions and type the name of the device to be used as the quorum device.

/dev/did/dsk/d1s6 5. Verify that the quorum device has been added. # scstat q Creation of diskset & partitions Diskset (metaset) has been created with the 4 different RAID sets r3oraset, r3ci set & r3archset r3 redo. This forms the device group for Sun Cluster installatio n. Use scdidadm L command to get a listing of all the did devices.

/ Installing Sun Cluster HA for Oracle Pre-requisite for installing SUN Cluster HA for Oracle On primary node i.e. pdbdrdb1 ensure biworaset diskset is available .Verify the same using scstat utility. Ensure that Oracle 9i is installed and configured with required volumes on biwor aset diskset . Ensure that Oracle user is created and has assigned appropriate rights to volume s that will be accessed by Oracle. Tnsnames.ora & listener.ora has valid HOST property as Logical Host. Installation and Configuration for SUN Cluster HA for Oracle & SAP. Install the data services package for Oracle & SAP from Sun Cluster 3.1 Agent CD on pdbdrdb1 & pdbdrci1 using pkgadd or scinstall menu. Register the resource types in the cluster a) Register HAStorage Plus resource type # scrgadm a t SUNW.HAStoragePlus b) Register Oracle Server resource type # scrgadm a t SUNW.oracle_server c) Register Oracle Listener resource type # scrgadm a t SUNW.oracle_listener d) Register SAP CI resource type # scrgadm -a -t SUNW.sap_ci_v2 e) Register SAP AS resource type # scrgadm -a -t SUNW.sap_as_v2 f) Register NFS resource type # scrgadm -a -t SUNW.nfs List the registerd resource type root@pdrdrci1 # scrgadm -p Res Type name: Res Type description: Res Type name: Res Type description: Res Type name: Res Type description: HA Storage SUNW.LogicalHostname:2 Logical Hostname Resource Type SUNW.SharedAddress:2 HA Shared Address Resource Type SUNW.HAStoragePlus:2 HA Storage Plus - A Resource Type which subsumes

Res Type name: Res Type description: Res Type name: Res Type description: Res Type name: Res Type description: Res Type name: Res Type description: Res Type name: Res Type description: Res Group name: Res Group RG_description: Res Group mode: Res name: Res R_description: Res resource type: Res type version: Res resource group name:

SUNW.oracle_server:4 Resource type for Oracle Server SUNW.oracle_listener:4 Resource type for Oracle Listener SUNW.sap_as_v2 SAP R/3 Application Server on Sun Cluster SUNW.sap_ci_v2 SAP R/3 Central Instance on Sun Cluster SUNW.nfs:3.1 HA-NFS for Sun Cluster r3ora-rg <NULL> Failover r3-ora-prv-lh SUNW.LogicalHostname:2 2 r3ora-rg

Res resource project name: default Res name: Res R_description: Res resource type: Res type version: Res resource group name: Res resource project name: Res name: Res R_description: Res resource type: Res type version: Res resource group name: Res resource project name: Res name: Res R_description: stener:4 Res resource type: Res type version: Res resource group name: Res resource project name: Res Group name: Res Group RG_description: Res Group mode: Res name: Res R_description: Res resource type: Res type version: Res resource group name: r3-ora-stor-res SUNW.HAStoragePlus:2 2 r3ora-rg default r3-ora-res SUNW.oracle_server:4 4 r3ora-rg default r3-ora-lsn-res Failover data service resource for SUNW.oracle_li SUNW.oracle_listener:4 4 r3ora-rg default r3ci-rg <NULL> Failover r3-ci-pub-lh SUNW.LogicalHostname:2 2 r3ci-rg

Res resource project name: default Res name: Res R_description: Res Res Res Res resource type: type version: resource group name: resource project name: r3-ci-prv-lh SUNW.LogicalHostname:2 2 r3ci-rg default r3-ci-stor-res SUNW.HAStoragePlus:2 2 r3ci-rg default nfs-res SUNW.nfs:3.1 3.1 r3ci-rg default r3-ci-res Failover data service resource for SUNW.sap_ci_v2 SUNW.sap_ci_v2 2.0 r3ci-rg default

Res name: Res R_description: Res resource type: Res type version: Res resource group name: Res resource project name: Res name: Res R_description: Res resource type: Res type version: Res resource group name: Res resource project name: Res name: Res R_description: Res resource type: Res type version: Res resource group name: Res resource project name: 1.3 Cluster Commands

Starting the Cluster Node For Cluster Mode o Give the command ok>boot o

to start the machine in cluster mode. to start the machine in non-cluster mode.

For Non-Cluster Mode Give the command ok>boot -x

Shutting down the machine To shutdown the cluster, give the following command on Primary node (prddrdb1) #scshutdown y g0 This command will bring down the secondary node first and then the primary node. Shutting down Single System in Cluster To shutdown any node of the cluster, give the following command #init 0 Switching the resources from Primary node (prdpsdb1) to Secondary node (prdpsci1 ) #scswitch z g r3ora-rg h p drdrci1 Stopping Oracle resources without shutting down the cluster services To shutdown Oracle Server resource, give the following command

#scswitch n

j r3-ora-res

To shutdown Oracle Listner resource, give the following command #scswitch n j r3-ora-lsn-res Starting Oracle resources in the cluster services To enable/start Oracle Server resource, give the following command #scswitch e j r3-ora-res To enable/start Oracle Listner resource, give the following command #scswitch e j r3-ora-lsn-res Stopping & starting Oracle resource group To stop Oracle resource group (r3ora-rg), give the following command #scswitch F g r3ora-rg

This will bring down the database before bringing resource group offline. To start Oracle resource group,give the following command #scswitch Z g r3ora-rg To view the overall cluster status #scstat g To view cluster information #scconf pvv

Anda mungkin juga menyukai