- Objectives
- Prerequisites
- Introduction
- Management Server Functions
- Section 2.7: Solaris OE Installation Preparation on Each Cluster Node
- Section 2.8: Install the Solaris 8 Operating Environment on Each Cluster Node
- Section 2.9: Install Recommended Solaris OE Patches on Each Cluster Node
- Section 2.10: The Solaris OE Post Installation and Configuration
- Section 2.11: Configure Additional Cluster Management Services
- Appendix A: System Configuration Files
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Section 2.7: Solaris OE Installation Preparation on Each Cluster Node
Prior to installing the Solaris OE on each cluster node, we will reconfigure the OpenBoot™ PROM settings for each cluster node.
NOTE
During many of the following steps, you will be required to enter commands simultaneously into each cluster node. Use the Cluster Control Panel window for this purpose. Double-click the Cluster Console (console mode) icon, as described in the previous section, "Configuring the Cluster Control Panel."
Key Practice: Until the EEPROM configuration has been completed, you should disable the auto-boot EEPROM feature on each cluster node. Disabling the auto-boot feature will alleviate any problems that arise if both systems attempt to boot their Solaris OE, while at the same time, both systems are set with the same (that is, conflicting) SCSI-initiator ID settings, the boot would fail.
We disable auto-booting on each cluster node by configuring the auto-boot? variable to FALSE during this phase of the installation. We do this because, the system has not yet been configured. If there is an accidental reboot of a node and if the system auto-boot? variable has been set to FALSE, the system will reset to the OpenBoot PROM prompt, instead of attempting to boot from the boot disk. At this phase, an attempt to boot from the disk may require an administrator to manually put the system back to the OpenBoot PROM for further configuration changes.
You will be instructed to re-enable this important feature at the end of this procedure.
Step 2.7.1—Disabling the Automatic Boot Capability
Disable auto-booting by entering the following command into both nodes (we want to disable the auto boot capability temporarily until we have built a stable Solaris OE on the machine). The auto-boot variable will be re-enabled later in the exercise.
ok setenv auto-boot? false auto-boot? = false
Step 2.7.2—Changing the SCSI Initiator ID
Enter the following command into the cconsole: host clustnode2 window.
ok setenv scsi-initiator-id 6 scsi-initiator-id = 6
NOTE
For SCSI initiator ID modification, refer to Figure 1-1 and Tables 1-1 through 1-5, specifically noting the disk subsystem cabling and configuration. Because two cluster nodes (both Sun Enterprise™ 220R hardware servers) are connected to the same pair of Sun StorEdge™ D1000 arrays, the OpenBoot PROM settings require modification. We will set the SCSI initiator ID on one of the cluster nodes (clustnode2 in this exercise) to a value of 6 and insert a script into the nvramrc (nonvolatile memory) on clustnode2 to maintain a SCSI initiator ID of 7 for the internal SCSI controller on clustnode2. Setting the global SCSI initiator ID on clustnode2 to 6 will prevent a conflict on the shared SCSI bus that connects both Sun Enterprise 220R servers to the Sun StorEdge D1000 arrays.
By changing the SCSI initiator ID on clustnode2 to a value of 6, we are making a global variable change that affects other devices attached to the internal SCSI controller on clustnode2. Specifically, setting the global SCSI initiator ID to 6 will create a conflict between the internal SCSI controller and the internal CD-ROM drive. To solve this conflict, we will explicitly set the SCSI initiator ID of the internal SCSI controller on clustnode2 to a value of 7 by including specific script commands into the nvramrc.
NOTE
Use the OpenBoot PROM nvedit command in the following procedure. The nvram editor is always set to insert mode. Use the following keystrokes when editing.
Using nvedit Keystrokes
|
Keystroke |
Action |
|
Ctrl+B |
Moves backward one character. |
|
Ctrl+C |
Exits the nvramrc editor, returning to the Open Boot PROM command interpreter. The temporary buffer is preserved, but it is not written back to the nvramrc editor. (Use nvstore afterwards to write it back.) |
|
Delete |
Deletes previous character. |
|
Ctrl+F |
Moves forward one character. |
|
Ctrl+K |
From current position in a line, deletes all text after the cursor and joins the next line to the current line (that is, it deletes the new line). |
|
Ctrl+L |
Lists all lines. |
|
Ctrl+N |
Moves to the next line of the nvramrc editing buffer. |
|
Ctrl+O |
Inserts a new line at the cursor position and stays on the current line. |
|
Ctrl+P |
Moves to the previous line of the nvramrc editing buffer. |
|
<CR> |
Inserts a new line at the cursor position and advances to the next line. |
NOTE
Using nvedit can be tricky because there is no delete command. If you want to delete a line, you must delete all of the characters for the line. Then, use Ctrl+K to join the empty line with the subsequent line.
Step 2.7.3—Setting the Internal SCSI Controller
Set the internal SCSI controller (/pci@1f,4000/scsi@3) SCSI-initiator-ID value to 7 by using the nvedit command. Enter the following commands into the cconsole: host clustnode2 window.
ok printenv nvramrc
nvramrc =
{{ensure that no previous commands or entries exist
in nvram before proceeding}}
ok nvedit {{invoke the nvram editor}}
0: probe-all
1: cd /pci@1f,4000/scsi@3
2: 7 " scsi-initiator-id" integer-property {{note the space
before AND after the first quotation prior
to the word "scsi" in this line}}
3: device-end
4: install-console
5: banner
6: {{at this point use Ctrl + C to exit nvedit}}
ok nvstore
ok printenv nvramrc {{verify that this exactly matches
with your screen output}}
nvramrc = probe-all
cd /pci@1f,4000/scsi@3
7 " scsi-initiator-id" integer-property
device-end
install-console
banner
Step 2.7.4—Enabling the nvramrc Variable
Enter the following command into the cconsole: host clustnode2 window to enable the nvramrc variable.
ok setenv use-nvramrc? true use-nvramrc? = true
Step 2.7.5—Verifying the nvramrc Script
Verify that the nvramrc script works by performing the following steps on clustnode2.
On clustnode2, reset the system by entering the reset command into the OpenBoot PROM prompt.
After clustnode2 resets, enter the printenv scsi-initiator-id command into the OpenBoot PROM prompt to confirm that the global SCSI-initiator-ID is set to 6.
ok reset Resetting ... ok printenv scsi-initiator-id scsi-initiator-id = 6
On clustnode2, use the cd(1) command to navigate to the node (that is, directory) that represents the internal SCSI controller /pci@1f,4000/scsi@3.
At the OpenBoot PROM prompt, enter the .properties command to verify that the internal SCSI initiator ID on clustnode2 is set to 7, as indicated in the next codebox.
ok cd /pci@1f,4000/scsi@3 ok .properties scsi-initiator-id 00000007 . . .
Step 2.7.6—Resetting the auto-boot Variable
After you have verified that the SCSI-initiator-ID settings are correct, reset the EEPROM auto-boot variables back to true on each cluster node.
ok setenv auto-boot? true auto-boot? = true
Summary of Key Practices
|
Disable the OpenBoot PROM auto-boot feature on each cluster node until EEPROM configuration is complete. Be careful when using nvedit because editing can be tricky (that is, it is always set to insert mode). |