>>> 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 addresses (see RFC 1597 for details).

If you do select another network address, please bear in mind that

the Sun Clustering 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 it minimally masks all bits given in the network address

and does not contain any holes.

Is it okay to accept the default network address [172.16.0.0] (y/n) y

8. Specify the netmask address of the private interconnect:

• To accept the default netmask address, press Y.
• To specify a different netmask address, press N, followed by the netmask address.

Is it okay to accept the default netmask [255.255.0.0] (y/n) y

Caution - You must press Y to accept the default netmask. Do not press Return. If you press Return, unpredictable behavior may occur.

9. Confirm the assigned names and addresses:

• If all are correct, press Y.
• If any of the values are not correct, press N, and the line number of the item to change, followed by the correct value.
• Press 99 to quit the update mode when all values are displayed correctly.

Management Server "MS-280R" (192.168.0.1) at 8:0:20:fd:ef:8 Option External Admin Network Setting ------- ------------------------------------------------------------- 1) Management Server's Default Router= 192.168.0.248 2) Terminal Server's Name= TC 3) Terminal Server's IP Address= 192.168.0.2 Option Cluster Environment and Public Network Settings ------ ------------------------------------------------------------- 4) Cluster Name= sc 5) Cluster Nodes Default Router= router_IP_address 6) Public Network Mask for the Cluster Nodes= 255.255.255.0 7) First Node's Name= node1 8) First Node's IP Address= node1_IP_address 9) First Node's Ethernet Address= 8:0:20:fb:29:8e 10) Second Node's Name= node2 11) Second Node's IP Address= node2_IP_addres 12) Second Node's Ethernet Address= 8:0:20:fb:1a:55 Option Internal Admin Network Settings Network Settings ------ ------------------------------------------------------------- 13) Internal Admin Network address= 10.0.0.0 14) Internal Admin Netmask= 255.255.255.0} 15) Admin IP Address for the Management Server= 10.0.0.1 16) Admin IP Address for the First Cluster Node= 10.0.0.2 17) Admin IP Address for the Second Cluster Node= 10.0.0.3 18) First T3's Host Name= T3-01 19) First T3's Admin Network IP Address= 10.0.0.4 20) First T3's Ethernet Address= 00:20:f2:00:3e:a6 21) Second T3's Host Name= T3-02 22) Second T3's Admin Network IP Address= 10.0.0.5 23) Second T3's Ethernet Address= 00:20:f2:00:04:d6 Option Cluster Private Interconnect Settings ------ ------------------------------------------------------------- 24) Private Interconnect Network Address= 172.16.0.0 25) Private Interconnect Netmask= 255.255.0.0 Option Finish Updates ------ ------------------------------------------------------------- 99) quit update mode....   Are all variables correctly set y/n? y

10. When prompted, choose one of the following volume manager products:

• For Solstice DiskSuite, press Y.
• For VERITAS Volume Manager, press N.

Storage Software Configuration <   The Cluster nodes can be configured with either *Solstice DiskSuite 4.2.1 or Veritas VM 3.1.1*   The default is Solstice DiskSuite 4.2.1. If the installer does not except the default, Veritas Volume Manager 3.1.1 will be installed. By choosing VXVM 3.1.1 you will be making a choose to encapsulate your boot disk.   A Veritas license is required for each node running VXVM 3.1.1. You will be prompted during the install of each cluster node to enter the license key.   Please have the license keys ready.   Do you want to install Solaris Volume Manager 4.2.1 (y/n) y

The configuration files for the management server are configured for root and swap mirroring.

================================================================ PLEASE WAIT: Setting up Management Server configuration files for jumpstart services Preparing Management Server for root and swap mirroring.   System will reboot after setup! ================================================================ Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard OpenBoot 4.0, 512 GB memory installed, Serial #16641800. Ethernet address 8:0:20:fd:ef:8, Host ID: 80fdef08.

The management server reboots.

To Boot Up the T3 Arrays

---

Caution - During a recovery, do not power cycle the Sun StorEdge T3 arrays as mentioned in Step 1. Instead, proceed to Step 2.

---

1. Power on the Sun StorEdge T3 disk arrays.

============================================================= Power on T3's at this point. If T3's are already powered up, Power cycle them and let them reboot.   This will take 3-4 minutes!!   Please Wait until T3's have completely rebooted.   Press the Return key when T3's are ready! =============================================================

The disk arrays boot.

2. Press Return when the Sun StorEdge T3 disk arrays are finished booting.

To Set Up the Sun Management Center Software

Refer to the Sun Management Center 3.0 Installation Guide for additional details.

1. Choose to set up, or not set up the Sun Management Center (Sun MC) software:

• Press Y to set up Sun Management Center software (server, agent, and console) on the management server, and continue with Step 2.
• Press N to set up the management server without configuring the Sun Management Center software, and proceed to To Install the Oracle Software. You can install the Sun Management Center software at another time by running the Sun Management Center setup script
  (/opt/SUNWsymon/sbin/es-setup).

- Do you want to setup Sun MC 3.0 (y/n) y

---

Note - If you receive an error that reports Missing Product License, you can do one of the following: Ignore the error, and run the Sun MC software as usual. The license is used for Sun MC advanced monitoring features. The standard features do not require a license. Obtain a Sun MC license. Visit: http://www.sun.com/solaris/sunmanagementcenter

---

2. Answer the Sun Management Center installation questions as shown in the following example:

----------------------------------- Sun Management Center Setup Program -----------------------------------   This program does setup of Sun Management Center components that are installed on your system.   Checking for Sun Management Center components installed on your system.   You have the following Sun Management Center components installed   Sun Management Center Server Sun Management Center Agent Sun Management Center Console   Sun Management Center successfully configured for java: "Solaris_JDK_1.2.2_08"   Configuring the system for setup, please wait.   This part of setup generates security keys used for communications between processes. A seed must be provided to initialize the keys. Please make sure you use the same seed for all the machines you install. You may like to keep record of this seed for future use.   Please enter the seed to generate keys:abc123 Please re-enter the seed to confirm:abc123   You should setup a user as a Sun Management Center administrator. This person will be added to the esadm and esdomadm groups. Please enter a user to be the Sun Management Center administrator:root   The Sun Management Center base URL is relative to the Sun Management Center Console. The Sun Management Center Console is able to request help documentation via the network.

If you have installed Sun Management Center help documentation in an http-accessible location within your network, you may specify this location. If Sun Management Center help is installed on the console host, simply accept the default value. Please enter base URL to Sun Management Center help [local]: <cr>   The base URL has been set to file:/opt/SUNWsymon/lib/locale ---------------------------------------------------------------- Starting Sun Management Center Service Availability Manager Setup ---------------------------------------------------------------- Setup for Service Availability Manager in progress, please wait. Setup of Service Availability Manager complete.

3. Specify whether you want to install the Sun Management Center Sun Fire 15K administration module.

• Press Y if you have Sun Fire 15K servers in your enterprise and you want to monitor them with Sun Management Center.
• Press N if you do not have Sun Fire 15K servers in your environment.

---------------------------------------------------------- Starting Sun Management Center Sun Fire 15000 Server Setup ----------------------------------------------------------   Would you like to setup this Sun Management Center package? [y|n|q] n

4. Specify whether you want to install the Sun Management Center Sun Fire 15K system controllers administration module.

• Press Y if you have Sun Fire 15K system controllers in your enterprise and you want to monitor them with Sun Management Center.
• Press N if you do not have Sun Fire 15K system controllers in your environment.

---------------------------------------------------- Starting Sun Management Center Sun Fire 15000 System Controller Server Setup ----------------------------------------------------   Would you like to setup this Sun Management Center package? [y|n|q] n

5. Specify whether you want to install the Sun Fire 6800/4810/4800/3800 administration module.

• Press Y if you have Sun Fire 6800/4810/4800/3800 servers in your enterprise and you want to monitor them. Answer the additional installation prompts.
• Press N if you do not have these Sun Fire servers in your environment.

For setting up Sun Fire (6800/4810/4800/3800) platform administration module you need to provide SC IP address, community strings, port numbers for domain agent etc.   Do you want to setup Sun Fire (6800/4810/4800/3800) platform administration module [y|n|q] n

6. Press Y to install the Sun Management Center Netra t administration module for monitoring the management server and Sun StorEdge T3 arrays.

---------------------------------------------------------- Starting Sun Management Center Netra t Setup ---------------------------------------------------------- ---> Platform Found: Netra T1 ---> Netra t add-on Agent package found! <--- Do you want to setup Netra t Config Reader for this platform? [y|n|q] y

7. Press Y to monitor the T3 arrays.

Do you want to setup T3 module [y|n|q] y

8. Press 3 to select the Add managed T3 routine.

Selecting 3 causes the script to prompt you with T3 setup questions.

---------------------------------- Sun Management Center StorEdge T3 Module Setup Program ----------------------------------   This program will configure the StorEdge T3, so that they can be managed by T3 Module   [1] List managed T3 [2] List available T3 [3] Add managed T3 [4] Remove managed T3 [5] Reconfigure managed T3 [6] Quit   Select the function you want to perform [1-6]: 3

9. Select 1 to display the list of available T3 arrays.

[1] add T3 from available T3 list. [2] add new T3 [3] return to the main menu Please press [1-3] 1

10. Press the line number of the first T3 array.

---

Note - Do not select any line numbers associated with the nodes.

---

Available T3: Name IP Address   1 node1 10.0.0.2 2 node2 10.0.0.3 3 T3-01 10.0.0.4 4 T3-02 10.0.0.5   Add available T3 [1-4] 3

11. Type the root password for the selected T3 array, and press Return.

---

Caution - During a recovery of the management server, the Sun StorEdge T3 arrays retain the passwords and IP addresses that you assigned during the initial installation. Resetting them during a recovery is not needed. If you are prompted for the array passwords and IP addresses, ignore the questions. The recovery process will continue after a time-out of a few seconds.

---

Input root password of T3-01:abc   Check SunMC token files... Check SunMC token files success. Check logging status... Check logging status success.   Press Enter to return: <CR>

12. Press 3 to configure Sun Management support for the second T3 array:

---------------------------------- Sun Management Center StorEdge T3 Module Setup Program ----------------------------------   This program will configure the StorEdge T3, so that they can be managed by T3 Module   [1] List managed T3 [2] List available T3 [3] Add managed T3 [4] Remove managed T3 [5] Reconfigure managed T3 [6] Quit   Select the function you want to perform [1-6]: 3

13. Press 1 to display the list of available arrays:

[1] add T3 from available T3 list. [2] add new T3 [3] return to the main menu Please press [1-3] 1

14. Press the line number of the second T3 array:

---

Note - Do not select any line numbers associated with the nodes.

---

Available T3: Name IP Address   1 node1 10.0.0.2 2 node2 10.0.0.3 3 T3-02 10.0.0.5   Add available T3 [1-3] 3

15. Type the root password for this T3 array, and press Return.

---

Caution - During a recovery of the management server, the Sun StorEdge T3 arrays retain the passwords and IP addresses that you assigned during the initial installation. Resetting them during a recovery is not needed. If you are prompted for the array passwords and IP addresses, ignore the questions. The recovery process will continue after a time-out of a few seconds.

---

Input root password of T3-02:abc   Check SunMC token files... Check SunMC token files success. Check logging status... Check logging status success.   Press ENTER to return: <CR>

16. Press 6 to exit the T3 module setup program.

The Sun Management Center software will install the module that supports monitoring of T3 arrays.

---------------------------------- Sun Management Center StorEdge T3 Module Setup Program ----------------------------------   This program will configure the StorEdge T3, so that they can be managed by T3 Module   [1] List managed T3 [2] List available T3 [3] Add managed T3 [4] Remove managed T3 [5] Reconfigure managed T3 [6] Quit   Select the function you want to perform [1-6]: 6

17. Specify whether you want to install the Sun Management Center CP2000 administration module.

• Press Y to use Sun Management Center to monitor any CP2000 systems (SPARCengine based systems with compact PCI) in your enterprise network and you want to monitor them with Sun Management Center.
• Press N if you do not have CP2000 systems in your environment.

---------------------------------------------------------- Starting Sun Management Center CP2000 Application Setup ---------------------------------------------------------- PLATFORM_FILE= /var/opt/SUNWsymon/platform/platform.prop /var/opt/SUNWsymon/platform ---> Visa application add-on Agent package found! <--- Do you want to setup the CP2000 applications for this platform? [y|n|q] n

18. If you receive the following question, specify whether you want to install the Sun Management Center CP2000/CP1500 server module.

• Press Y to use Sun Management Center to monitor any CP2000/CP1500 platforms in your enterprise and you want to monitor them with Sun Management Center.
• Press N if you do not have CP2000/CP1500 platforms in your environment.

----------------------------------------------------------- Starting Sun Management Center CP2000/CP1500 Server Setup ----------------------------------------------------------- PLATFORM_FILE= /var/opt/SUNWsymon/platform/platform.prop /var/opt/SUNWsymon/platform ---> Visa Server add-on package found! <--- Do you want to setup the Server Package for the CP2000/CP1500 platforms? [y|n|q] n

19. Press N to skip starting the Sun MC components.

---

Caution - You should press N to the following prompt. Pressing Y causes a list of exception errors that interfere with the script output. If you press Y, wait until the error messages complete, then press Return to be prompted to install the Oracle software, as in the next step. After the nodes have completed their configuration, you can manually start the Sun MC server and agent components on the management server. Alternatively, you can wait until the management server is rebooted, at which time the server and agent will be started automatically.

---

---------------------------------------------------------- Starting Sun Management Center WGS Setup ---------------------------------------------------------- Using /var/opt/SUNWsymon/cfg/console-tools.cfg /var/opt/SUNWsymon/cfg/tools-extension-j.x updated.   Sun Management Center setup complete. Please wait, Sun Management Center database setup in progress. It may take 15 to 20 minutes   Do you want to start Sun Management Center agent and server components now [y|n|q] n

To Install the Oracle Software

1. Press N to install the Oracle9i RAC software.

Do you want to install Oracle9i HA (y/n) n   Oracle9i RAC and Volume Manager 3.1.1 will be installed.

The Oracle software license will be printed.

2. When prompted, press Return to review the Oracle license terms.

3. Press Y to agree to the Oracle license terms.

The login prompt will appear.

To Install the Cluster Node Software

---

Note - When executing the ccp(1M) command remotely, you must ensure that the DISPLAY shell environment variable is set to the IP address of the local host.

---

1. Type the command /user/openwin/bin/xhost 192.168.0.1 (the administration IP address of the management server) to enable your windows manager to display screens from the management server.

2. Log in to the management server as the superuser (root).

3. Set and export the DISPLAY shell environment variable to the IP address of the local host:

# DISPLAY=local_host_IP_address:0.0; export DISPLAY

4. Launch the Cluster Control Panel:

# ccp $CLUSTER &

This command displays the Cluster Control Panel (FIGURE 3-3).

 

FIGURE 3-3 Cluster Control Panel

5. In the Cluster Control Panel window, double-click on the cconsole icon to display a Cluster Console window for each cluster node (FIGURE 3-4).

 FIGURE 3-4 Cluster and Node Console Windows

To type text into both node windows simultaneously, click the cursor in the Cluster Console window and type the text. The text does not display in the Cluster Console window. This ensures that both nodes execute the commands simultaneously.

---

Note - The console windows for both cluster nodes are grouped (the three windows move in unison). To ungroup the Cluster Console window from the node windows, select Options from the Hosts menu, and deselect the Group Term Windows checkbox.

---

6. In the Cluster Console window, type the following command into both nodes simultaneously:

boot net - install

---

boot net - You must use spaces before and after the hyphen (-) character in the "install" command.

---

The following software is automatically installed on both cluster nodes:

• Solaris 8 10/01 operating environment
• VERITAS Volume Manager 3.1.1
• Sun Cluster 3.0 7/01 and recommended patches
• Oracle9i Database RAC, version 9.0.1.2

All patches are applied and system files are configured to produce a basic cluster environment. In addition, the Oracle 9i Database RAC software is configured and a sample database is set up.

You may see the following error:

Boot device: /pci@8,700000/network@5,1: File and args: Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet . . .

If so, it is likely that you need to correct one of the following:

• Naming service conflict--A naming service was selected during the configuration of the management server.
• No network route--For network environments with a production and an administration network, the two network backbones must be routed so that the cluster nodes can jump start from the management server. If this is the case, you need to temporarily provide two Ethernet cables and connect the eri0 network interfaces on both cluster nodes to the supplied ethernet hub in the Clustered Platform. Once the installation and setup is complete, remove the temporary connections from the ethernet hub and the nodes, and reconnect the cables from the cluster nodes eri0 to the production network.

---

Note - Press Ctrl+] and send brk to stop the Timeout waiting for ARP/RARP packet errors.

---

After you execute the boot(1M) command, you should see output as the management server installs and configures the Oracle software. Refer to for an example of the output.

7. Take one of the following actions based on the volume manager product you chose:

• Solstice DiskSuite--continue with the next step.
• VERITAS Volume Manager--proceed to To Configure VERITAS Volume Manager.

8. Log into each cluster node as the superuser (password is abc), and change the default password to a secure password:

# passwd passwd: Changing password for root New password: secure-password-choice Re-enter new password: secure-password-choice

9. Install the Sun Management Center agent.

For instructions, refer to the Sun Management Center documentation.

10. Configure the Sun StorEdge T3 array shared disk storage.

Configure the T3 array volume configuration if you do not plan to use the default T3 configuration. Refer to the T3 documentation that shipped with your Clustered Platform.

Configure the storage using Solstice DiskSuite, then create disk sets, metadevices, and file systems that suit your needs. Refer to the Solstice DiskSuite documentation.

11. Proceed to Finishing Up.

To Configure VERITAS Volume Manager

---

Caution - The following instructions only apply to configurations that are using VERITAS Volume Manager instead of Solstice DiskSuite. Only follow this procedure if you selected to use VERITAS Volume Manager.

---

---

Note - You will not see these questions if you chose to install Solstice DiskSuite.

---

You must have two valid VERITAS license keys (one for each node) to complete this procedure.

1. In the Cluster Console window (cconsole) choose to encapsulate the root disk, and type the pathname of the Jumpstart program:

Do you want Volume Manager to encapsulate root [yes]? yes   Where is the Volume Manager cdrom? /net/ManagmentServer-ip-address/jumpstart/Packages/VM3.1.1

---

Note - Ignore references to "cdrom" in the computer output.

---

2. In each individual node window, enter the license key for that node (obtained from VERITAS) to register your version of VERITAS Volume Manager:

---

Note - You must enter your own valid VERITAS license keys for the script to complete successfully. A VERITAS license key is made up of 23 digits and is formatted as follows: 1234 5678 1234 5678 1234 567 (This is an example only. Do not use this number.)

---

---

Caution - You must enter valid license keys. If the script detects an error in the license key, the script will not complete successfully.

---

(For node 1) Volume Manager installation is complete. Oct 8 15:34:03 node1 vxdmp: NOTICE: vxvm:vxdmp: added disk array 60020f20000004d60000000000000000 Oct 8 15:34:03 node1 vxdmp: NOTICE: vxvm:vxdmp: added disk array 60020f2000003ea00000000000000000   Please enter a Volume Manager license key: node1_VERITAS_license_key

 

(For node 2) Volume Manager installation is complete. Oct 8 15:34:03 node2 vxdmp: NOTICE: vxvm:vxdmp: added disk array 60020f20000004d60000000000000000 Oct 8 15:34:03 node2 vxdmp: NOTICE: vxvm:vxdmp: added disk array 60020f2000003ea00000000000000000   Please enter a Volume Manager license key: node2_VERITAS_license_key

3. In the Cluster Console window, wait for the installer script to display the login prompt:

================================================================ Setting up root mirror. This will take approximately 45min's   Please wait .... ================================================================ The system is ready. node1 console login:

4. In each individual node window, log in to each cluster node as a superuser (password is abc) and change the default password to a secure password:

node1 console login: root Password: abc # passwd passwd: Changing password for root New password: secure-password-choice Re-enter new password: secure-password-choice

 

node2 console login: root Password: abc # passwd passwd: Changing password for root New password: secure-password-choice Re-enter new password: secure-password-choice

5. Install the Sun Management Center agent on the cluster nodes.

Installing the Sun Management Center agent enables Sun Management Center to monitor the nodes. For installation instructions, refer to the Sun Management Center 3.0 Installation Guide.

6. Configure the Sun StorEdge T3 array shared disk storage.

Configure the storage using VERITAS Volume Manager. Configure the volumes and file systems to suit your needs. Refer to the VERITAS Volume Manager documentation.

---

Note - The VERITAS Volume Manager VMSA packages are available on the management server in the /jumpstart/Packages/VM3.1.1 directory. If you want to use the VERITAS GUI, install the VMSA packages with the pkgadd command. Once installed, the Volume Manager man pages will be placed in the /opt/VRTS/man directory. Add this directory to your MANPATH variable to access these pages with the man command.

---

7. Proceed to Finishing Up.

---

Finishing Up

You need to perform additional steps depending on your environment. This section contains references to additional steps that may be needed.

To Finish the Installation

1. Install and configure your highly available application(s) for the cluster environment.

For additional details, refer to the manufacturers' documentation that accompanied your highly available application(s).

Refer to the following appendices for additional information about configuring the following software that came with your clustered platform:

• Appendix E, To Install Sun Component Manager 2.2
• Appendix F, To Access the Management Server from the Sun Ray

2. Establish network automatic failover (NAFO), resource groups, logical hosts, and data services to enable your application(s) under the Sun Cluster 3.0 infrastructure. Refer to the Sun Cluster 3.0 documentation. The path to the Sun Cluster data services is:

/net/sc3sconf1-ms/jumpstart/Packages/SC3.0u1/scdataservices_3_0_ul

NAFO configuration and activation information is in the Sun Cluster 3.0 U1 System Administration Guide (806-7073), Chapter 5, "Administering Cluster Interconnects and Public Networks," section "Administering the Public Network," starting on page 93.

---

Note - Before you use an editor in a Cluster Console window, verify that the TERM shell environment value is set and exported to a value that emulates the kind of input terminal your are using on the local system.

---

---

Note - You can stop the cluster nodes and access the OpenBoot PROM prompt by positioning the cursor in the Cluster Console window and pressing Ctrl+]. This control character sequence displays the telnet prompt. Typing send brk (equivalent to a Stop-A) at the telnet prompt forces access to the OpenBoot PROM prompt.

---

3. Optionally, enable the Oracle GUI configuration assistant to access the nodes.

Certain Oracle GUI configuration assistants such as dbca and netca require the ability to issue a remote shell (rsh) to the nodes. For this to take place, a .rhosts file must reside in the home directory of each node (for security reasons, the default configuration does not create a .rhosts file). The .rhosts file for each node is populated with the node name of each node, and private interconnect IP addresses (for the local node), followed by the oracle UNIX user name. For security, delete both .rhosts files when you are finished running dbca or netca.

Content for a .rhosts file:

cluster_node1_name oracle cluster_node2_name oracle node_private_interconnect_IP_1 oracle node_private_interconnect_IP_2 oracle

---

Note - You can run /usr/sbin/ifconfig -a on a node to determine the private interconnect IP addresses.

---

4. Place the Oracle database into archive log mode.

Choose a location where the Oracle redo log files are copied, and specify the location in the server parameter file. An area on the shared storage device can be used for this purpose. This location should be specified on a UFS file system, not on a raw partition. For more information on these topics, refer to the Oracle documentation.

5. Determine and set up your backup strategy and methods.

For backing-up the Oracle database, if you chose not to place the database into archive log mode, then only offline backups can be performed. In this case, you need to shutdown the instance during the backup, and recovery is only available back to the time of the last offline backup. For more information on these topics, refer to the Oracle documentation.

You are now done installing and configuring the Clustered Database Platform software.

---

After the Installation

This section contains information about what has been installed and configured on the cluster nodes and what you can do with the software.

Post-Installation Modification of the /etc/hosts File

After the management server finishes installing the software on the nodes, you must update the /etc/hosts file so that it corresponds to the cluster platform network configuration.

To Update the /etc/hosts File

1. On the management server, use a text editor to open the /etc/hosts file.

2. Delete the first two occurrences of the -admin text string (shown highlighted in the following example):

# Physical Hosts (Physical Addresses) 129.153.47.181 test #Management Server 129.153.47.71 TC #Terminal Concentrator 129.153.47.120 node1-admin #First Cluster Node 129.153.47.121 node2-admin #Second Cluster Node 10.0.0.1 test-admin #Admin Network 10.0.0.2 node1 #First Cluster Node admin network 10.0.0.3 node2 #Second Cluster Node admin network 10.0.0.4 T3-01 #First T3 Host Name 10.0.0.5 T3-02 #Second T3 Host Name

3. Append -admin to the two internal administration node names (shown highlighted in the following example):

# Physical Hosts (Physical Addresses) 129.153.47.181 test #Management Server 129.153.47.71 TC #Terminal Concentrator 129.153.47.120 node1 #First Cluster Node 129.153.47.121 node2 #Second Cluster Node 10.0.0.1 test-admin #Admin Network 10.0.0.2 node1-admin #First Cluster Node admin network 10.0.0.3 node2-admin #Second Cluster Node admin network 10.0.0.4 T3-01 #First T3 Host Name 10.0.0.5 T3-02 #Second T3 Host Name

4. Save your changes and quit the editing session.

Post-Installation Removal of the /.rhosts File

For security reasons, when the installation and setup of the cluster platform is complete, remove the root user /.rhosts file on each cluster node to prevent unauthorized access to the nodes. This file is not typically needed after the cluster installation is complete. However, some cluster agents may require the root user to have remote access to the cluster nodes. Refer to the agent documentation for more details.

Oracle9i Packages

The following packages are installed on the cluster nodes:

• SUNWraco--Oracle 9i RAC, version 9.0.1.2, with Intelligent Agent Patch 1918073
• SUNWraccf--Scripts to configure RAC database at node install time

Starter Database

The starter database is configured with the default Oracle passwords. For the sys user, the password is change_on_install. For the system user, the password is manager. You should change these passwords by using the alter user command in SQL*Plus.

Database Recovery

You should place each starter database provide with the Clustered Database Platform into archive log mode. You must choose a location to which the redo log files may be copied and to specify it in the server parameter file. For Oracle9i RAC, you must set it up on each instance.

Backup Method

You should choose a backup method to be performed on a regular basis, such as offline or online. You must provide the scripts. If you choose not to place the database into archive log mode, then only offline backups can be performed. An offline backup involves a shutdown of the instance, which means that the recovered data would only reflect the last offline backup. For more information on these topics or to read about Oracle Recovery Manager, refer to your Oracle software documentation.

Redo Log Groups

The RAC redo log files are not set up in redo log groups. You can, however, create the redo log groups and add the RAC redo log files so that each group acts as mirrors for redundancy. Use the ALTER DATABASE ADD LOGFILE MEMBER command to add the RAC redo log files to the groups.

If you add the RAC redo files and the database is placed into archive log mode, the Archiver background process can take advantage of the multiple copies to perform pre-fetching of redo log blocks from each group member in a round-robin fashion. For more information, refer to your Oracle software documentation, as well as Doc. ID 45042.1 on http://metalink.oracle.com. (You must be registered to use this site.)

Operation Instructions

You can access operation instructions in the Clustered Database Platform 280/3 system documentation and the Oracle documentation (see Clustered Database Platform Documentation).

Clustered Database Platform 280/3 With Oracle9i Database RAC Installation Guide

816-4075-10

Copyright © 2002, Sun Microsystems, Inc. All rights reserved.