- 论坛徽章:
- 0
|
a1000
这是我在网上找的文档,不知是否适用于我的情况
Since the factory default scsi-initiator-id for all adapter cards on the system is 7, it is suggested that the scsi-initiator-id for all the SunSwift cards on one host be 7 and those on the other host be set to 6. Therefore, the procedure outlined below must be done on only one of the cluster hosts.
The easiest way to accomplish this configuration is to set the Initiator ID for one of the cluster hosts to 6 and then to change the scsi-initiator-id for the on-board SCSI controller to 7. This configuration is set from the OpenBoot(TM) PROM (OBP) Monitor.
Table 3-3 SCSI Initiator ID Settings Controller Instance Cluster Node A Initiator ID Cluster Node B Initiator ID
0 (internal) 7 7
1 7 6
2 7 6
Setting Up the nvramrc Script in the OBP Monitor The OpenBoot PROM Monitor builds its own device tree based on the devices attached to the system when the boot sequence is invoked. The OBP Monitor has a set of default aliases for the commonly occurring devices in the system.
A nvramrc script contains a series of OpenBoot PROM commands that are executed during the boot sequence. It is assumed that this file is nonexistent and will be created. The steps to create or edit a nvramrc script are similar. You need to be familiar with nvramrc Editor Keystroke Commands. Table 3-4 lists the most useful commands.
Enter the OBP Monitor by shutting down the system:
# shutdown -g0 -y -i0
Set the NVRAM parameters to the default values.
ok set-defaults
Setting NVRAM parameters to default values.
ok
Set the scsi-initiator-id to 6.
ok setenv scsi-initiator-id 6
scsi-initiator-id = 6
ok
Enter the nvedit command to create and store an nvramrc script.
The line numbers (0:, 1:, and so on) are printed by the OpenBoot PROM Monitor. See Table 3-4 for the nvramrc editor keystroke commands.
ok nvedit
0: dev scsi
1: 7 encode-int " scsi-initiator-id" property
2: device-end [Control-c]
ok
--------------------------------------------------------------------------------
Caution - Insert exactly one space after the double quote and before scsi-initiator-id.
--------------------------------------------------------------------------------
Store or discard the changes.
The changes you make using the nvedit command are done on a temporary copy of the nvramrc script. You can continue to edit this copy without risk. Once you are through editing, save the modifications. If you are not sure about the changes, discard them. If, for any reason, you do not want to save the contents of the nvedit buffer, type:
ok nvquit
ok
To store the changes, type:
ok nvstore
ok
--------------------------------------------------------------------------------
Note - Before proceeding any further, you must have successfully created the nvramrc script and saved it by using nvstore.
--------------------------------------------------------------------------------
Verify the contents of the nvramrc script you created in Step 4.
ok printenv nvramrc
nvramrc = dev scsi
7 encode-int " scsi-initiator-id" property
device-end
ok
If the output differs from what you have entered, go back to Step 4 and edit nvramrc again.
Do a test of the nvramrc script by entering the nvramrc evaluate command. Verify the scsi-initiator-id of the host.
ok nvramrc evaluate
ok printenv scsi-initiator-id
scsi-initiator-id = 6
ok
If the overall scsi-initiator-id for this host is not 6, then repeat Step 3 before continuing with the verification.
Verify that the nvramrc script works properly. If the scsi-initiator-id for the on-board SCSI controller is not set to 7, then re-edit the nvramrc script by repeating Step 4 and Step 5.
ok cd scsi
ok .properties
hm-rev 00 00 00 22
scsi-initiator-id 00000007
device_type scsi
clock-frequency 02625a00
intr 00000020 00000000
interrupts 00000020
reg 0000000e 08800000 00000010
0000000e 08810000 00000040
name SUNW,fas
ok
In the preceding output, the scsi-initiator-id has a value of 00000007 so the script worked properly.
Instruct the OpenBoot PROM Monitor to use the nvramrc script.
ok setenv use-nvramrc? true
ok printenv use-nvramrc?
use-nvramrc? = true
ok
On the cluster host node2, verify that the scsi-initiator-id has a value of 7.
ok printenv scsi-initiator-id
scsi-initiator-id = 7
ok printenv use-nvramrc?
use-nvramrc? = false
ok
If the output is not 7 and false, repeat this procedure on node2 to set the scsi-initiator-id to 7 on this node.
ok setenv scsi-initiator-id 7
and/or
ok setenv use-nvramrc ? false
Load the patches for the fas driver (104246-02) and the sd driver (103622-02) on both nodes in the cluster.
Connect the MultiPacks to both hosts and reboot both systems using the
-r option.
ok boot -r
You have completed the last step of the OBP Monitor setup.
|
|
免费注册
发表于 2002-06-28 18:13
发表于 2002-06-29 15:16