5.1 Installation Rules

When you install Solaris 2.4 on Solstice HA servers, you must follow these general rules:

• Set up each of the Solstice HA systems as standalone machines.
• Install the same Solaris software cluster on both servers. For example, if the entire distribution is installed on one server, it must be installed on the other Solstice HA server.
• Use identical partitioning on the local disks of each of the Solstice HA servers where Solaris 2.4 is installed.

5.2 Selecting the Size of the Root Slice

The root slice on your local disk must be large enough to hold the following:

• The Solaris 2.4 system components
• Any components from Solstice DiskSuite, Solstice HA, and other third party software packages
• Data space for symbolic links in /dev for the SPARCstorage Arrays and Solstice Disksuite metadevices

The root slice must also have enough inodes for the various files and directories as well as the device inodes in /devices and symbolic links in /dev. By default one inode is allocated per two Kbytes of file system capacity when newfs(1M) is run on the file system during Solaris installation.

The Solaris install process automatically determines the file system size required for the operating system components placed on the root slice. For Solaris 2.4 this is approximately 14 Mbytes (assuming separate files systems for /opt, /var, and /usr).

While the install process does not determine the number of inodes required, the number of Solaris inodes is approximately 3,000. These do not include SPARCstorage Array and Solstice DiskSuite inodes. The default ratio of inodes to storage (one inode per two Kbytes of UFS capacity) is sufficient for the Solaris root slice in configurations that do not have SPARCstorage Arrays or Solstice DiskSuite. The demand for inodes by the SPARCStorage Arrays and Solstice DiskSuite may exceed the number available. The worksheet in Table 5-1 will help you plan your root slice size. Table 5-4 tells you the required root file system sizes for various configurations.

Each disk partition requires two inodes in /devices (one inode for each raw and block device). Each partition also requires two symbolic links in /dev that point to the device inodes in /devices. Each symbolic link requires one inode and one fragsize block of disk storage (typically this is one Kbyte). Since each disk drive has eight slices you will need 32 inodes and 16 Kbytes on the root file system for each disk.

You should allocate resources for the maximum number of SPARCstorage Array chassis you will configure into your system (for the SPARCserver 2000 systems 20 SPARCstorage Arrays are supported, while the SPARCcenter 1000s

support eight SPARCstorage Arrays). While you may initially only partially populate your SSA chassis you should allocate enough inodes and space for a full complement of disks to allow for future growth and reconfiguration.

The SPARCstorage Array 100 chassis accommodates 30 drives, and so 960 inodes and 480 Kbytes should be allocated on the root file system for each chassis.

Each Solstice DiskSuite metadevice consumes two inodes (raw and block) in /devices and two inodes as well as two Kbytes in /dev (symbolic links to /devices). The default Solstice DiskSuite configuration has md_nsets=4 and nmd=128 (refer to the Solstice DiskSuite 4.0 Administration Guide) for a total of 512 metadevices.

---

Note - The Solstice DiskSuite documentation refers to hot spare pools as metadevices, but they do not consume inodes in /dev or /devices, so they do not enter the computation.

---

Under Solstice HA, a maximum Solstice DiskSuite configuration would have md_nsets=3 and nmd=1024 for a total of 3,072 metadevices. Thus a maximum Solstice DiskSuite configuration would require 12,288 inodes and 6,144 Kbytes of disk storage on the root file system.

The worksheet and examples in Table 5-1, and Table 5-2 show the computation. The number of Solstice DiskSuite metadevices is the product of the values for nmd and md_nsets that are found in the /kernel/drv/md.conf file.

Table 5-1

Components	Inode Calculations	Kbyte Calculations
SPARCstorage Array 100 with 30 disks number of SPARCstorage Arrays (SSA)	SSAs * 960 = ____ inodes	SSAs * 480 Kbytes = _____ Kbytes
Solstice DiskSuite metadevices (md_nsets times nmd)	nmd * md_nsets * 4 = ____ inodes	nmd * md_nsets * 2 = _____ Kbytes
Solaris 2.4	3,000 inodes	= 15,000 Kbytes
Totals	total inodes total inodes times 2 Kbytes = minimum UFS size _____ Kbytes	_____ Kbytes

You should take the larger of Inode Calculations and Kbyte Calculations from the last line of Table 5-1 to use as your required root file system size. You also need to allow for additional free space.

The example in Table 5-2 shows how the template could be used in a typical configuration that has six SPARCstorage Arrays and 512 metadevices. In this example the entries are made in bold font.

Table 5-2

Components	Inode Calculations	Kbyte Calculations
SPARCstorage Array 100 with 30 disks	6 * 960 = 5,760 inodes	6 * 480 Kbytes =	2,880 Kbytes
Solstice DiskSuite metadevices (md_nsets times nmd)	4 * 128 * 4 = 2,048 inodes	4 * 128 * 2 Kbytes = 1,024 Kbytes
Solaris 2.4	3,000 inodes	=	15,000 Kbytes
Totals	10,808 inodes 10,808 inodes times 2 Kbytes = minimum UFS size 21,616 Kbytes		18,904 Kbytes

Table 5-3 shows a maximum Solstice HA configuration that has two SPARCserver 2000s and 20 SPARCstorage Arrays and uses the maximum number of Solstice DiskSuite metadevices.

Table 5-3

Components	Inode Calculations	Kbyte Calculations
SPARCstorage Array 100 with 30 disks	20 * 960 = 19,200 inodes	20 * 480 Kbytes =	9,600 Kbytes
Solstice DiskSuite metadevices (md_nsets times nmd)	3 * 1024 * 4 = 12,288 inodes	3 * 1024 * 2 Kbytes = 6,144 Kbytes
Solaris 2.4	= 3,000 inodes	=	15,000 Kbytes
Totals	34,488 inodes 34,488 inodes times 2 Kbytes = minimum UFS size 68,976 Kbytes		30,744 Kbytes

In the example shown in Table 5-2 the inode and symbolic link requirements for the SPARCstorage Arrays and Solstice DiskSuite devices require a file system more than double the size of that needed for the data alone.

You may want to allocate additional capacity to the root slice to accommodate future growth and package installation. This is especially true in small configurations where the size dictated by inodes is roughly equal to that dictated by data storage requirements and so comparatively little free data space is available.

Table 5-4 shows the required root file system size. The table should be used with the maximum number of drives you ultimately expect to have in the configuration, not the number you have during initial configuration. Similarly the metadevice parameters (md_nsets and nmd) should reflect your ultimate needs. The table entries are of the form size (free space), where size is the amount of space required in megabytes for the root file system and the amount of free space after Solaris 2.4, Solstice HA, and other required software have been installed. The values in the table are based on the calculations outlined earlier in this section.

---

Caution - Remember that you cannot enlarge the size of the root file system without reinstalling the Solaris operating environment. So you should calculate your disk needs based on future growth of the Solstice HA configuration.

---

Table 5-4 md.conf

Change md.conf File Values to:	md_nsets=4 nmd=128	md_nsets=3 nmd=256	md_nsets=3 nmd=512	md_nsets=3 nmd=1024
Number of Drives	root (free) in Mbytes	root (free) in Mbytes	root (free) in Mbytes	root (free) in Mbytes
30	17 (0)	17 (0)	20 (1.6)	32 (11)
60	17 (0)	18 (0)	22 (3)	34 (12)
90	18 (0)	18 (0)	24 (4.4)	36 (13)
120	18 (0)	20 (1.3)	26 (5.8)	38 (15)
150	20 (1.2)	22 (2.7)	28 (7.2)	40 (16)
180	22 (2.6)	24 (4.1)	30 (8.6)	42 (18)
210	23 (4.1)	25 (5.6)	31 (10)	43 (19)
240	25 (5.5)	27 (7)	33 (11)	45 (20)
270	27 (6.9)	29 (8.4)	35 (13)	47 (22)
300	29 (8.3)	31 (9.8)	37 (14)	49 (23)

Table 5-4 md.conf

Change md.conf File Values to:	md_nsets=4 nmd=128	md_nsets=3 nmd=256	md_nsets=3 nmd=512	md_nsets=3 nmd=1024
Number of Drives	root (free) in Mbytes	root (free) in Mbytes	root (free) in Mbytes	root (free) in Mbytes
330	29 (9.7)	33 (11)	39 (16)	51 (25)
360	33 (11)	35 (13)	41 (17)	53 (26)
390	35 (12)	37 (14)	43 (18)	55 (27)
420	37 (14)	39 (15)	45 (20)	57 (29)
450	38 (15)	40 (17)	46 (21)	58 (30)
480	40 (17)	42 (18)	48 (23)	60 (32)
510	42 (18)	44 (20)	50 (24)	62 (33)
540	44 (20)	46 (21)	52 (26)	64 (35)
570	46 (21)	48 (22)	54 (27)	66 (36)
600	48 (22)	50 (24)	56 (28)	68 (37)

In Table 5-4 you must determine which of the columns you want to use based on the number of metadevice names needed in the largest diskset. You must configure both servers with the same size root file system and the same values entered in the /kernel/drv/md.conf file. Refer to Section 3.1.19, "Metadevice Naming and Creation," on page 3-21 for help in determining which of the columns you should use.

5.3 Sizing File Systems for Install

The following table estimates the space required for the various file systems after Solaris2.4 Hardware: 3/95 release, the Solaris 2.4 Hardware: 3/95 patches, Solstice DiskSuite, Solstice HA and required patches have been installed. Note that the size of the root partition should be obtained from Table 5-4 for a given number of SPARCstorage Array drives and Solstice DiskSuite metadevices that you want to allocate.

---

Note - The Solstice HA space requirements in Table 5-5 include no free space. You should provide additional free space for future additions and short term needs. If you exhaust the free space you must reinstall the operating system (on both servers) to obtain additional free space. You should error on the side of extra free space; 20 percent or more is suggested. The /var file system will contain system messages and logs and can fill quickly, even more free space is recommended for /var.

---

In addition to the calculations in Table 5-5, you must allocate six Mbytes on slice 4 of the boot disk on each of the Solstice HA servers. This space is used for metadevice state database replicas and UFS logs.

Table 5-5

File System Name	Solstice HA Space Requirements	Your Additional Requirements	Total Space Needed
/	Value from Table 5-4	+ _______	= ________
/opt	110 Mbytes	+ _______	= ________
/usr	180 Mbytes	+ _______	= ________
/var	20 Mbytes	+ _______	= ________

· How to Install Solaris on the Administration Workstation

This section contains an example of the appropriate instructions for installing Solaris 2.4 on a Solstice HA system, using the character user interface (CUI) Solaris install program.

1. Turn on the CD-ROM, the SPARCstation 4 monitor, and the SPARCstation 4.

2. Insert the Solaris 2.4 CD.

3. Power up the system.

4. ^(TM) 4. Use the JumpStart default selections.

   JumpStart instructions are included in the SPARC: Installing Solaris Software manual.

5. The system will reboot.

   When the system comes back up, you will be prompted for a root password.

6. Log in to the system as root.

7. Eject the Solstice CD.

# eject

8. Insert the Solstice 2.4 CD.

   By ejecting and reinserting the CD, Volume Management will recognize the CD.

9. When the installation completes, change to the directory on the CD-ROM to where the Solaris 2.4 patches reside. Refer to the Solaris 2.4 Latest News document for a listing of the patches on the Solaris 2.4 Hardware: 3/95 CD-ROM. Then enter the following command:

# cd /cdrom/cdrom0/s0/Patches

10. Install the Solaris 2.4 patches by entering the following command:

# ./install_patches Installing Patches (using install_patches 1.25) Installation will be logged in /var/sadm/install_data/Patches_log install_patches completed successfully #

11. Reboot the system.

· How to Install the Terminal Concentrator

1. Configure the terminal concentrator.

   Use the instructions in Chapter 11 of the SPARCcluster High Availability Server Hardware Planning and Installation Manual to configure the terminal concentrator.

   Enter the IP address, subnet mask, and the network broadcast address for the terminal concentrator.

2. Enable terminal concentrator security.

   At this point, the terminal concentrator is operating with limited security. Terminal concentrator configuration is protected by an administrative password (the terminal concentrator IP address) which is documented in the terminal concentrator manuals and widely known. Because the port access is unrestricted, any user who can connect to the terminal concentrator can also connect to the Solstice HA server console and has access to a root login or can get into OpenBoot command interpreter by sending a break signal.

   Unless access to the public network serving the terminal concentrator is adequately restricted you will probably want to enhance the access security of the terminal concentrator.

   Using the command line interface (CLI), you can set separate internal passwords for administrative access and port access, using either specific port numbers or using the port selector. All port access is protected using the single port password. A more complex approach that allows individual user and password access is possible using the security host feature. For more information on this approach see Appendix B, "Terminal Concentrator Security" or the Terminal Concentrator Binder Set delivered with your system.

   To enable basic password security on your terminal concentrator open a telnet(1) connection and enter the following commands.

---

Note - There will be about a 30 delay after you enter the admin command reset annex all.

---

# telnet terminal_concentrator ... Enter Annex port name or number: cli Annex Command Line Interpreter * Copyright 1991 Xylogics, Inc. annex: su Password: terminal_concentrator_password annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports admin : set annex password new_terminal_concentrator_password You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : set port port_password port_password You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : set annex enable_security y You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : reset annex all admin : quit annex# su annex: hangup Resetting line and disconnecting. Connection closed by foreign host. #

· How to Install Solaris on the Solstice HA Servers

1. Log in to the administration workstation as root.

2. Start OpenWindows.

# /usr/openwin/bin/openwin

3. Open two shelltool(1) windows on the administration workstation.

4. Open a telnet connection in each of the windows to one of the Solstice HA servers through the terminal concentrator. Follow each of the steps in this procedure in both windows.

   Ports 2 and 3 of the terminal concentrator are connected to the respective server console serial ports. These two ports are numbered 5002 and 5003. Run the following command to open the telnet connection to a server in one of the windows.

# telnet terminal_concentrator_name 5002

Run the following command to open a telnet connection in the other window to the other server.

# telnet terminal_concentrator_name 5003

5. Power on the two Solstice HA servers.

   You can view the power on self tests via the two shelltool windows.

6. If either server attempts to boot, you will want to send a break to enter the OpenBoot PROM.

   To sent a break, you must first enter the telnet escape character Control-].

^] telnet> send brk ok

7. Run the following commands to set the variables from the OpenBoot PROM.

ok set-defaults Setting NVRAM parameters to default values. ok setenv watchdog-reboot? true watchdog-reboot?= true ok

8. Insert a Solaris 2.4 Hardware: 3/95 CD-ROM in the CD of each Solstice HA servers.

9. In each of the two windows, boot the install image from the CD-ROM.

   For example if you have inserted the Solaris 2.4 CD-ROM, enter:

ok boot cdrom

Some or all of the following system identification screens may not appear if the installation software can get the information from the name service.

10. Select option 8 in each of the shelltool windows. If you are not using shelltool windows, select the appropriate terminal type. The screens used in this example may appear different depending on the terminal type you select.

What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 3) DEC VT100 4) Heathkit 19 5) Lear Siegler ADM31 6) PC Console 7) Sun Command Tool 8) Sun Workstation 9) Televideo 910 10) Televideo 925 11) Wyse Model 50 12) X Terminal Emulator (xterms) 13) Other Type the number of your choice and press Return: 8 starting rpc services: rpcbind sysidnis ypbind done.

11. When the following screen is displayed, press F2.

- The Solaris Installation Program ----------------------------- You are now interacting with the Solaris installation program. The program is divided into a series of short sections. At the end of each section, you will see a summary of the choices you've made, and be given the opportunity to make changes. As you work with the program, you will complete one or more of the following tasks: 1 - Identify peripheral devices 2 - Identify your system 3 - Install Solaris software About navigation... - The mouse cannot be used - If your keyboard does not have function keys, or they do not respond, press ESC; the legend at the bottom of the screen will change to show the ESC keys to use for navigation. --------------------------------------------------------------- F2_Continue F6_Help

12. If the following screen displays, press F2. Otherwise, skip to Step 15.

- Identify This System ----------------------------------------- On the next screens, you must identify this system as networked or non-networked, and set the default time zone and date/time. If this system is networked, the software will try to find the information it needs to identify your system; you will be prompted to supply any information it cannot find. > To begin identifying this system, press F2. --------------------------------------------------------------- F2_Continue F6_Help

13. Answer any questions about the network configuration.

    The types of questions asked will depend on the name service you are using at your site. If the installation software can find all of the network information you will not see any questions.

14. Answer any questions about the time zone and date.

15. If the following screen is displayed, press F4 to perform an initial install. Otherwise, go to the next step.

    Caution - The instructions in this chapter are for initial install. Never choose the "upgrade option" on a Solstice HA system.

- Upgrade System? ---------------------------------------------- This system is upgradable. Choosing the upgrade option means any bundled Solaris software will be updated to the new release, and as many local modifications as possible will be saved. While your system is upgradable, you can choose the initial option; however, files on your disk will be overwritten and data will be lost. CAUTION: If you choose the upgrade option, it is especially important to back up your system. However, backing up is also recommended for the initial option if there is any data on the disk that you want to save. > To start the upgrade option, choose F2. > To start the initial option, choose F4. --------------------------------------------------------------- F2_Upgrade F4_Initial F5_Exit F6_Help

16. When the following screen is displayed, press F2.

- Install Solaris Software - Initial --------------------------- The screens that follow let you tailor how Solaris is installed on your system. The main tasks you must perform to install Solaris software on your system are: - Selecting a system type - Selecting Solaris software - Selecting disks to hold the software you've selected - Specifying how files systems are laid out on the disks After completing these tasks, a summary of your selections (called a profile) is displayed. You can go back and change selections as many times as you like before starting to install Solaris. > To continue, press F2. --------------------------------------------------------------- F2_Continue F3_Go Back F5_Exit F6_Help

17. Select the Standalone system type then press F2.

- System Type -------------------------------------------------- On this screen you must specify one of the following system types. A system type determines where a system will get its directories and file systems, and whether it provides portions of Solaris software to other systems. > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. [X] Standalone [ ] Server [ ] Dataless Client --------------------------------------------------------------- F2_Continue F3_Go Back F5_Exit F6_Help

18. Select the Entire Distribution plus OEM support then press F2.

- Software ----------------------------------------------------- On this screen you must select the Solaris software to install on your system. The software groups shown below are bundled and defined by SunSoft. You can accept the default [X], or select another. NOTE: After selecting a software group, you can add or remove software from it by selecting F4 to customize. However, this requires understanding of software dependencies and how Solaris software is packaged. > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]; then press F4 to customize or F2 to continue. [X] Entire Distribution plus OEM support .. 448.33 MB (F4 to Customize) [ ] Entire Distribution ................... 448.27 MB [ ] Developer System Support .............. 360.24 MB [ ] End User System Support ............... 267.21 MB [ ] Core System Support ................... 164.50 MB --------------------------------------------------------------- F2_Continue F3_Go Back F4_Customize F5_Exit F6_Help

Optionally, you may choose to only install the software required to run Solstice HA and Solstice DiskSuite. The required software includes the End User Support software group in addition to the SUNWmfrun, SUNWssadv, SUNWssaop, and SUNWssamn packages.

If you are planning to use HA-ORACLE, you must install software required for Solstice HA in addition to the SUNWbtool, SUNWsprot, SUNWarc, and SUNWlibm packages.

---

Caution - Use caution when you are partitioning the boot disk if you choose to load only the minimally required parts of Solaris 2.4. If you fail to leave adequate space for future additions to the software you may need to repartition the disk and reload the Solaris distribution.

---

19. Select the local disk where Solaris 2.4 will be installed, along with the other local disk where you plan to install the ORACLE distribution if you are planning to use HA-ORACLE.

    Caution - The bootdrive you select on one host must be the same size and have the same device number on the other server. Otherwise, when you invoke hasetup(1M), data could be lost and the metadevice state database replicas may not be set up correctly.

- Disks -------------------------------------------------------- On this screen you must select the disks for installing Solaris software. Start by looking at the Suggested Minimum field; this value is the approximate space needed to install the software you've selected. Keep selecting disks until the Total Selected value exceeds the Suggested Minimum value. > To make selections, use the arrow keys to highlight options and press Return to mark them [X]. Disk Device (Size) Available Space ============================================= - [X] c0t0d0 (1002 MB) bootdrive 1002 MB | [X] c0t1d0 (1002 MB) 1002 MB | [ ] c1t0d0 (1002 MB) 1002 MB | [ ] c1t0d1 (1002 MB) 1002 MB | [ ] c1t0d2 (1002 MB) 1002 MB v [ ] c1t0d3 (1002 MB) 1002 MB Total Selected: 1002 MB --------------------------------------------------------------- F2_Continue F3_Go Back F5_Exit F6_Help

---

Caution - You must select the correct local disk. In Chapter 3, "Installation Planning," you decided which local disk would contain Solaris 2.4. You must select that disk now. On the previous screen, c0t0d0 was selected as the disk that will contain Solaris 2.4 (that is, the bootdrive).

---

20. If the following screen is displayed, press F2.

- Preserve Data? ----------------------------------------------- At least one of the disks you've selected has file systems or unnamed slices that you may want to save. > To save file systems or unnamed slices, press F4. > To allow current file systems and unnamed slices to be overwritten when Solaris software is installed, press F2. --------------------------------------------------------------- F2_Continue F3_Go Back F4_Preserve F5_Exit F6_Help

21. Select the auto-layout feature by pressing F2.

- Automatically Layout File Systems? --------------------------- Do you want to use the auto-layout feature to automatically layout file systems on your disks? Manually laying out file systems on disks requires advanced system administration skills. > To use the auto-layout feature, press F2. > To manually layout file systems, press F4. --------------------------------------------------------------- F2_Auto Layout F3_Go Back F4_Manual Layout F5_Exit F6_Help

22. On the Auto-Layout File Systems screen, select the /opt and /var file systems in addition to the default selections for automatic layout. Then press F2.

- Auto-layout File Systems ------------------------------------ On this screen you must select all the file system you want auto-layout to create, or accept the defaults shown. NOTE: For small disks (less than 200 MB), it may be necessary for auto-layout to break up some of the file systems you request into smaller file systems to fit the available disk space. So, after auto-layout completes, you may find file systems in the layout that you did not select from the list below. File Systems for Auto-layout ======================================== [X] / [X] swap [X] /usr [X] /opt [ ] /usr/openwin [X] /var --------------------------------------------------------------- F2_Continue F5_Cancel F6_Help

---

Note - Only select auto-layout for /opt and /var. Do not select auto-layout for /usr/openwin, because Slice 4 will be used for another purpose.

---

23. When the following screen is displayed, press F4 to customize the disk layout.

- File System and Disk Layout -------------------------------- The summary below is your current file system and disk layout, based on the information you've supplied. NOTE: If you press F4 to customize, you should understand file systems, their intended purpose on the disk, and how changing them may affect the operation of the system. > To accept the layout shown, press F2. > To customize the layout, press F4. File system/Mount point Disk/Slice Size =========================================================== - / c0t0d0s0 14 MB | swap c0t0d0s1 128 MB | /usr c0t0d0s6 227 MB | /opt c0t0d0s5 173 MB | /var c0t0d0s3 110 MB | /export/home c0t0d0s7 346 MB v /export/home0 c0t1d0s7 1002 MB --------------------------------------------------------------- F2_Continue F3_Go Back F4_Customize F5_Exit F6_Help

24. Select the bootdrive (c0t0d0) to customize by pressing F4.

Select Disk to Customize > To select a disk, use the arrow keys to highlight it, and press F4. Disk (Size) Configured File Systems =============================================================== c0t0d0 (1002 MB) /, swap, /var, /opt, /usr, /export/home c0t1d0 (1002 MB) /export/home0 --------------------------------------------------------------- F2_OK F4_Customize F6_Help

25. Scroll through the list of file systems and remove the 346 Mbytes allocated for /export/home. Also remove the /export/home mount point. You can use either the arrow keys on the key pad or the Tab key to move the cursor around the Customize Disk screen.

    Note - The slice sizes entered in the following steps are for an example configuration. Refer to Table 5-5 on page 5-7 to calculate the sizes for your configuration.

- Customize Disk: c0t0d0 -------------------------------------- Entry: Recommended: MB Minimum: MB =============================================================== Slice Mount Point Size (MB) 0 / 14 1 swap 128 2 overlap 1002 3 /var 110 4 0 5 /opt 173 6 /usr 227 7 0 =============================================================== Capacity: 1002 MB Allocated: 652 MB Rounding Error: 4 MB Free: 346 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

26. Refer to Table 5-5 for the appropriate amount of space to allocate to the root (/) file system.

    In this example 35 Mbytes is allocated.

- Customize Disk: c0t0d0 -------------------------------------- Entry: / Recommended: 14 MB Minimum: 12 MB =============================================================== Slice Mount Point Size (MB) 0 / 35 1 swap 128 2 overlap 1002 3 /var 110 4 0 5 /opt 173 6 /usr 227 7 0 =============================================================== Capacity: 1002 MB Allocated: 673 MB Rounding Error: 3 MB Free: 326 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

27. Refer to Table 5-5 for the appropriate amount of space to allocate to the

    /var file system.

- Customize Disk: c0t0d0 -------------------------------------- Entry: /usr Recommended: 227 MB Minimum: 193 MB =============================================================== Slice Mount Point Size (MB) 0 / 35 1 swap 128 2 overlap 1002 3 /var 130 4 0 5 /opt 173 6 /usr 227 7 0 =============================================================== Capacity: 1002 MB Allocated: 693 MB Rounding Error: 3 MB Free: 306 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

28. Place 6 Mbytes in slice 4 for metadevice state databases and local UFS logs. Do not give this slice a mount point.

    Note - The amount of free space may vary by a small amount on different disks.

- Customize Disk: c0t0d0 -------------------------------------- Entry: Recommended: MB Minimum: MB =============================================================== Slice Mount Point Size (MB) 0 / 35 1 swap 128 2 overlap 1002 3 /var 130 4 6 5 /opt 173 6 /usr 227 7 0 =============================================================== Capacity: 1002 MB Allocated: 699 MB Rounding Error: 3 MB Free: 300 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

29. Refer to Table 5-5 for the appropriate amount of space to allocate to the

    /opt file system.

- Customize Disk: c0t0d0 -------------------------------------- Entry: /opt Recommended: 173 MB Minimum: 150 MB =============================================================== Slice Mount Point Size (MB) 0 / 35 1 swap 128 2 overlap 1002 3 /var 130 4 6 5 /opt 283 6 /usr 227 7 0 =============================================================== Capacity: 1002 MB Allocated: 809 MB Rounding Error: 3 MB Free: 190 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

30. Refer to Table 5-5 for the appropriate amount of space to allocate to the

    /usr file system. After you have allocated space for every file system, press F2.

- Customize Disk: c0t0d0 -------------------------------------- Entry: /usr Recommended: 227 MB Minimum: 193 MB =============================================================== Slice Mount Point Size (MB) 0 / 35 1 swap 128 2 overlap 1002 3 /var 130 4 6 5 /opt 283 6 /usr 418 7 0 =============================================================== Capacity: 1002 MB Allocated: 1000 MB Rounding Error: 2 MB Free: 0 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

31. (Optional) Press F4 to customize the second local disk for ORACLE. Otherwise, press F2 and skip to Step 34.

- Select Disk to Customize ------------------------------------- > To select a disk, use the arrow keys to highlight it, and press F4. Disk (Size) Configured File Systems =============================================================== c0t0d0 (1002 MB) /, swap, /var, /opt, /usr c0t1d0 (1002 MB) /export/home0 --------------------------------------------------------------- F2_OK F4_Customize F6_Help

32. (Optional) If you are going to use the HA-ORACLE data service, the entire second local disk can be assigned to the ORACLE distribution. After changing the /export/home0 mount point to /oracle, press F2.

- Customize Disk: c0t1d0 -------------------------------------- Entry: Recommended: MB Minimum: MB =============================================================== Slice Mount Point Size (MB) 0 0 1 0 2 overlap 1002 3 0 4 0 5 0 6 0 7 /oracle 1002 =============================================================== Capacity: 1002 MB Allocated: 1002 MB Free: 0 MB --------------------------------------------------------------- F2_OK F4_Options F5_Cancel F6_Help

33. (Optional) Press F2 to continue.

- Select Disk to Customize ------------------------------------- > To select a disk, use the arrow keys to highlight it, and press F4. Disk (Size) Configured File Systems =============================================================== c0t0d0 (1002 MB) /, swap, /var, /opt, /usr c0t1d0 (1002 MB) /oracle --------------------------------------------------------------- F2_OK F4_Customize F6_Help

34. Verify the file system and disk layout for the two local disks then Press F2 to continue with Solaris installation.

- File System and Disk Layout ---------------------------------- The summary below is your current file system and disk layout, based on the information you've supplied. NOTE: If you press F4 to customize, you should understand file systems, their intended purpose on the disk, and how changing them may affect the operation of the system. > To accept the layout shown, press F2. > To customize the layout, press F4. File system/Mount point Disk/Slice Size ============================================================= / c0t0d0s0 35 MB swap c0t0d0s1 128 MB /usr c0t0d0s6 407 MB /opt c0t0d0s5 283 MB /var c0t0d0s3 130 MB /oracle c0t1d0s7 1002 MB ----------------------------------------------------------- - F2_Continue F3_Go Back F4_Customize F5_Exit F6_Help

35. Press F2 to bypass mounting remote file systems.

- Mount Remote File Systems? ---------------------------------- Do you want to mount software from a remote file server? This may be necessary if you had to remove software because of disk space problems. > To go to the Mount Remote File System screen, press F4. > To bypass mounting remote file systems, press F2. --------------------------------------------------------------- F2_Continue F3_Go Back F4_Remote Mounts F6_Help

36. Examine the Profile screen. To change any of the installation information, press F4. To use the file system and disk layout as presented, press F2.

- Profile ------------------------------------------------------ The information below is your profile for installing Solaris software. It is a summary of the choices you've made on previous screens. > To go back to the beginning to make changes, Press F4. =============================================================== System Type: Standalone Software: Solaris 2.4, Entire Distribution plus OEM's File System and Disk Layout: / c0t0d0s0 35 MB swap c0t0d0s1 128 MB /usr c0t0d0s6 407 MB /opt c0t0d0s5 283 MB /var c0t0d0s3 130 MB /oracle c0t1d0s7 1002 MB --------------------------------------------------------------- F2_Continue F4_Change F5_Exit F6_Help

37. Select Do Not Reboot when the following screen is displayed. Press F2 to continue.

- Begin Installing Solaris ------------------------------------- By default, your system will reboot after Solaris is installed. However, you can bypass rebooting and access a UNIX shell to make changes before rebooting. > To begin installing Solaris, press F2; to go back and make changes press F5. [ ] Reboot [X] Do not reboot --------------------------------------------------------------- F2_Begin Installation F5_Cancel

38. When Solaris 2.4 Hardware: 3/95 installation begins, you will see the following types of messages:

Preparing system to install Solaris. Please wait. Setting up disk c0t0d0: - Creating Solaris disk label (VTOC) Setting up disk c0t1d0: - Creating Solaris disk label (VTOC) Creating and checking UFS file systems: - Creating / (c0t0d0s0) - Creating /var (c0t0d0s3) - Creating /opt (c0t0d0s5) - Creating /usr (c0t0d0s6) - Creating /oracle (c0t1d0s7) Beginning Solaris package installation...

39. When the installation completes, change to the directory on the CD-ROM to where the Solaris 2.4 Hardware: 3/95 patches reside.

    Refer to the Solaris 2.4 Latest News document for a listing of the patches on the Solaris 2.4 Hardware: 3/95 CD-ROM. Then enter the following command:

# cd /cdrom/Patches

40. Install the Solaris 2.4 Hardware: 3/95 patches by entering the following command:

# ./install_patches /a Installing Patches (using install_patches 1.25) Installation will be logged in /a/var/sadm/install_data/Patches_log install_patches completed successfully #

41. Edit the /a/etc/system file on each of the servers. You must edit the /a/etc/system file to exclude the loopback file system. The following two lines should be added to the end of the /a/etc/system file on each of the servers.

* Solstice HA excludes the loopback file system exclude: lofs

42. (Optional) Make other changes to the /a/etc/system file on each of the servers.

    If you are planning to use the HA-ORACLE data service, you may need to make additional changes to the /a/etc/system file. These changes could be made at this time. Consult your ORACLE documentation for the appropriate changes to this file.

43. Reboot both Solstice HA servers.

    When Solaris installation completes, the system will reboot with the following sequence.

# reboot ...

44. Log in to each of the Solstice HA servers as root and eject the CD using the following command:

# eject

45. Turn to Chapter 6, "Installing the Packages and Patches," and follow the procedures given there.