| 前へ | 次へ | 目次 | 索引 |
ブートやダンプに使用する個々のデバイスのセットアップには， wwidmgrコマンドを使用します。デバイスをセットアップすると，コンソールからデバイスにアクセスするために必要な情報は不揮発性メモリに保存されます。システム構成が変更され，不揮発性情報が無効になった場合， wwidmgrコマンドを再実行する必要があります。
コンソールに用意されているコマンドは wwidmgr -quicksetというシンプルなコマンドです。このコマンドは，以下のどちらの場合にも使用できます。
上記のどちらも自分のケースに当てはまらない場合は，『Wwidmgr Users' Manual』を参照してください。
例 7-3 は， wwidmgr-quicksetコマンドの実行例です。以下の点に着目してください。
| 例 7-3 widmgr -quickset の使用 |
|---|
P00>>>wwidmgr -quickset -udid 10
Disk assignment and reachability after next initialization:
6000-1fe1-0000-0d10-0009-8090-0677-0016
via adapter: via fc nport: connected:
dga10.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes
dga10.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No
dgb10.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes
dgb10.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No
P00>>>wwidmgr -quickset -udid 50
Disk assignment and reachability after next initialization:
6000-1fe1-0000-0d10-0009-8090-0677-0016
via adapter: via fc nport: connected:
dga10.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes
dga10.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No
dgb10.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes
dgb10.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No
6000-1fe1-0000-0d10-0009-8090-0677-0026
via adapter: via fc nport: connected:
dga50.1001.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes
dga50.1002.0.2.1 kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No
dgb50.1003.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes
dgb50.1004.0.3.1 kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No
P00>>>initialize
Initializing...
P00>>>show device
polling ncr0 (NCR 53C810) slot 1，bus 0 PCI，hose 1 SCSI Bus ID 7
dka500.5.0.1.1 DKA500 RRD45 1645
polling kgpsa0 (KGPSA-B) slot 2，bus 0 PCI，hose 1
kgpsaa0.0.0.2.1 PGA0 WWN 1000-0000-c920-a7db
dga10.1001.0.2.1 $1$DGA10 HSG80 R024
dga50.1001.0.2.1 $1$DGA50 HSG80 R024
dga10.1002.0.2.1 $1$DGA10 HSG80 R024
dga50.1002.0.2.1 $1$DGA50 HSG80 R024
polling kgpsa1 (KGPSA-B) slot 3，bus 0 PCI，hose 1
kgpsab0.0.0.3.1 PGB0 WWN 1000-0000-c920-a694
dgb10.1003.0.3.1 $1$DGA10 HSG80 R024
dgb50.1003.0.3.1 $1$DGA50 HSG80 R024
dgb10.1004.0.3.1 $1$DGA10 HSG80 R024
dgb50.1004.0.3.1 $1$DGA50 HSG80 R024
polling isp0 (QLogic ISP1020) slot 4，bus 0 PCI，hose 1 SCSI Bus ID 15
dkb0.0.0.4.1 DKB0 RZ1CB-CS 0844
dkb100.1.0.4.1 DKB100 RZ1CB-CS 0844
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0 DVA0 RX23
polling ncr1 (NCR 53C810) slot 4，bus 0 PCI，hose 0 SCSI Bus ID 7
dkc0.0.0.4.0 DKC0 RZ29B 0007
polling tulip0 (DECchip 21040-AA) slot 3，bus 0 PCI，hose 0
ewa0.0.0.3.0 00-00-F8-21-09-74 Auto-Sensing
|
例 7-4 は，FC システム・ディスクからブートするときのシーケンスです。以下の点に着目してください。
| 例 7-4 FC システム・ディスクによるブート・シーケンス |
|---|
P00>>>set bootdef_dev dga50.1002.0.2.1,dga50.1001.0.2.1,dgb50.1003.0.3.1,
dgb50.1004.0.3.1
P00>>>b
(boot dga50.1002.0.2.1 -flags 0,0)
dga50.1002.0.2.1 is not connected
dga50.1002.0.2.1 is not connected
dga50.1002.0.2.1 is not connected
dga50.1002.0.2.1 is not connected
failed to open dga50.1002.0.2.1
(boot dga50.1001.0.2.1 -flags 0,0)
block 0 of dga50.1001.0.2.1 is a valid boot block
reading 919 blocks from dga50.1001.0.2.1
bootstrap code read in
Building FRU table
base = 200000，image_start = 0，image_bytes = 72e00
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
OpenVMS (TM) Alpha Operating System，Version V7.2
...
$ SHOW DEVICE
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DGA10: (FCNOD1) Online 0
$1$DGA50: (FCNOD1) Mounted 0 V72_SSB 4734189 303 1
$1$DGA51: (FCNOD1) Online 0
$1$DGA60: (FCNOD1) Online 0
$1$DGA61: (FCNOD1) Online 0
$ SHOW LOGICAL SYS$SYSDEVICE
"SYS$SYSDEVICE" = "$1$DGA50:" (LNM$SYSTEM_TABLE)
$ SHO DEV/MULTI
Device Device Error Current
Name Status Count Paths path
$1$DGA10: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11
$1$DGA50: (FCNOD1) Mounted 0 4/ 4 PGA0.5000-1FE1-0000-0D12
$1$DGA51: (FCNOD1) Online 0 4/ 4 PGA0.5000-1FE1-0000-0D13
$1$DGA60: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D14
$1$DGA61: (FCNOD1) Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11
Device Device Error Current
Name Status Count Paths path
$1$GGA42: Online 0 4/ 4 PGB0.5000-1FE1-0000-0D11
|
7.7 OpenVMS で使用するためのストレージ・コントローラのセットアップ
HP ストレージ・アレイ・コントローラと，そのコントローラを OpenVMS で使用できるように構成するための情報が記載してあるマニュアルは以下のとおりです。
ftp://ftp.compaq.com/pub/products/storageworks/techdoc/raidstorage/AA-RH4BD-TE.pdf
|
ftp://ftp.compaq.com/pub/products/storageworks/techdoc/enterprise/AA-RR03B-TE.pdf
|
OpenVMS では，HSG および HSV のコマンド・コンソール LUN (CCL) に対して一意のデバイス識別子を定義する必要はありませんが，一部の管理ツールでは必要な場合があります。この識別子を定義すると，SHOW DEVICE コマンドを使用して表示可能な CCL デバイスを作成できるため，OpenVMS では，常に一意のデバイス識別子を定義するように指示されます。対象のデバイスが OpenVMS で直接制御できない場合でも， SHOW DEVICE/FULL コマンドを使用して，ストレージ・コントローラへの複数のパスを表示したり，以下の例で $1$GGA3 に示すように，障害が発生したパスを診断できます。以下の例では，2 つのパスのうち 1 つに障害が発生しています。
Paver> sh dev gg /mul
Device Device Error Current
Name Status Count Paths path
$1$GGA1: Online 0 2/ 2 PGA0.5000-1FE1-0011-AF08
$1$GGA3: Online 0 1/ 2 PGA0.5000-1FE1-0011-B158
$1$GGA4: Online 0 2/ 2 PGA0.5000-1FE1-0015-2C58
$1$GGA5: Online 0 2/ 2 PGA0.5000-1FE1-0015-22A8
$1$GGA6: Online 0 2/ 2 PGA0.5000-1FE1-0015-2D18
$1$GGA7: Online 0 2/ 2 PGA0.5000-1FE1-0015-2D08
$1$GGA9: Online 0 2/ 2 PGA0.5000-1FE1-0007-04E3
Paver> show dev /full $1$gga9:
Device $1$GGA9:, device type Generic SCSI device, is online, shareable, device
has multiple I/O paths.
Error count 0 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 0 Default buffer size 0
WWID 02000008:5000-1FE1-0007-04E0
I/O paths to device 2
Path PGA0.5000-1FE1-0007-04E3 (PAVER), primary path, current path.
Error count 0 Operations completed 0
Path PGA0.5000-1FE1-0007-04E1 (PAVER).
Error count 0 Operations completed 0
|
完全なデバイス名を作成するには，ディスク用のデバイス識別子を文字列 $1$DGA の後に付けます。すべてのディスクにクラスタ内で一意のデバイス識別子を割り当てる必要があります。デバイス識別子として 0 〜 32767 の数値を指定できますが， HSV ではデバイス識別子 0 は無効です。 9999 より大きいデバイス識別子を指定すると，他のシステムに MSCP サービスを提供することができません。
7.8 共用 FC システム・ディスクを備えたクラスタの作成
OpenVMS Cluster システムにノードを構成するには， CLUSTER_CONFIG.COM( または CLUSTER_CONFIG_LAN.COM) コマンド・プロシージャを実行します。(ほとんどのプロンプトで詳細な情報が提供されるフル・バージョンと，簡易バージョンの 2 通りが用意されています。)
割り当てクラス・パラメータが FC に適用されない点を除き，共用 Fibre Channel (FC) バスは CLUSTER_CONFIG の目的に従って共用 SCSI バスと類似した扱いを受けます。 FC ストレージ・デバイスを組み込んだ構成にパラレル SCSI ストレージ・デバイスがあれば，ノード割り当てクラス値とポート割り当てクラス値の設定規則は有効です。
新しい OpenVMS Cluster システムを構成するには，まずシングル・システムかスタンドアロン・システムでクラスタリングを有効にします。これで，そのクラスタにノードを追加できます。
例 7-5 は， CLUSTER_CONFIG_LAN.COM の簡易バージョンを FCNOD1 というスタンドアロン・ノードでクラスタリングを有効にする方法を示したものです。このプロシージャの最後に， FCNOD1 は再ブートして 1 ノード・クラスタを構成します。
例 7-6 は， FCNOD1 で CLUSTER_CONFIG_LAN.COM の簡易バージョンを実行して， FCNOD2 という第 2 のノードを追加する方法を示しています。このプロシージャの最後に，クラスタは， FCNOD2 が FCNOD1 と同じ FC システム・ディスクからブートできる構成になります。
以下の手順は，両方の例に共通です。
| 例 7-5 スタンドアロン FC ノードにおけるクラスタリングの有効化 |
|---|
$ @CLUSTER_CONFIG_LAN BRIEF
Cluster Configuration Procedure
Executing on an Alpha System
DECnet Phase IV is installed on this node.
The LAN，not DECnet，will be used for MOP downline loading.
This Alpha node is not currently a cluster member
MAIN MENU
1. ADD FCNOD1 to existing cluster，or form a new cluster.
2. MAKE a directory structure for a new root on a system disk.
3. DELETE a root from a system disk.
4. EXIT from this procedure.
Enter choice [1]: 1
Is the node to be a clustered node with a shared SCSI or Fibre Channel bus (Y/N)? Y
Note:
Every cluster node must have a direct connection to every other
node in the cluster. Since FCNOD1 will be a clustered node with
a shared SCSI or FC bus，and Memory Channel，CI，and DSSI are not
present, the LAN will be used for cluster communication.
Enter this cluster's group number: 511
Enter this cluster's password:
Re-enter this cluster's password for verification:
Will FCNOD1 be a boot server [Y]? Y
Verifying LAN adapters in LANACP database...
Updating LANACP LAN server process volatile and permanent databases...
Note: The LANACP LAN server process will be used by FCNOD1 for boot
serving satellites. The following LAN devices have been found:
Verifying LAN adapters in LANACP database...
LAN TYPE ADAPTER NAME SERVICE STATUS
======== ============ ==============
Ethernet EWA0 ENABLED
CAUTION: If you do not define port allocation classes later in this
procedure for shared SCSI bus，all nodes sharing a SCSI bus
must have the same non-zero ALLOCLASS value. If multiple
nodes connect to a shared SCSI bus without the same allocation
class for the bus，system booting will halt due to the error or
IO AUTOCONFIGURE after boot will keep the bus offline.
Enter a value for FCNOD1's ALLOCLASS parameter [0]: 5
Does this cluster contain a quorum disk [N]? N
Each shared SCSI bus must have a positive allocation class value. A shared
bus uses a PK adapter. A private bus may use: PK，DR，DV.
When adding a node with SCSI-based cluster communications，the shared
SCSI port allocation classes may be established in SYS$DEVICES.DAT.
Otherwise，the system's disk allocation class will apply.
A private SCSI bus need not have an entry in SYS$DEVICES.DAT. If it has an
entry，its entry may assign any legitimate port allocation class value:
n where n = a positive integer，1 to 32767 inclusive
0 no port allocation class and disk allocation class does not apply
-1 system's disk allocation class applies (system parameter ALLOCLASS)
When modifying port allocation classes，SYS$DEVICES.DAT must be updated
for all affected nodes，and then all affected nodes must be rebooted.
The following dialog will update SYS$DEVICES.DAT on FCNOD1.
There are currently no entries in SYS$DEVICES.DAT for FCNOD1.
After the next boot，any SCSI controller on FCNOD1 will use
FCNOD1's disk allocation class.
Assign port allocation class to which adapter [RETURN for none]: PKA
Port allocation class for PKA0: 10
Port Alloclass 10 Adapter FCNOD1$PKA
Assign port allocation class to which adapter [RETURN for none]: PKB
Port allocation class for PKB0: 20
Port Alloclass 10 Adapter FCNOD1$PKA
Port Alloclass 20 Adapter FCNOD1$PKB
WARNING: FCNOD1 will be a voting cluster member. EXPECTED_VOTES for
this and every other cluster member should be adjusted at
a convenient time before a reboot. For complete instructions,
check the section on configuring a cluster in the "OpenVMS
Cluster Systems" manual.
Execute AUTOGEN to compute the SYSGEN parameters for your configuration
and reboot FCNOD1 with the new parameters. This is necessary before
FCNOD1 can become a cluster member.
Do you want to run AUTOGEN now [Y]? Y
Running AUTOGEN -- Please wait.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
upgrade will be complete.
|
| 例 7-6 共用 FC システム・ディスクがあるクラスタへノードを追加する |
|---|
$ @CLUSTER_CONFIG_LAN BRIEF
Cluster Configuration Procedure
Executing on an Alpha System
DECnet Phase IV is installed on this node.
The LAN，not DECnet，will be used for MOP downline loading.
FCNOD1 is an Alpha system and currently a member of a cluster
so the following functions can be performed:
MAIN MENU
1. ADD an Alpha node to the cluster.
2. REMOVE a node from the cluster.
3. CHANGE a cluster member's characteristics.
4. CREATE a duplicate system disk for FCNOD1.
5. MAKE a directory structure for a new root on a system disk.
6. DELETE a root from a system disk.
7. EXIT from this procedure.
Enter choice [1]: 1
This ADD function will add a new Alpha node to the cluster.
WARNING: If the node being added is a voting member，EXPECTED_VOTES for
every cluster member must be adjusted. For complete instructions
check the section on configuring a cluster in the "OpenVMS Cluster
Systems" manual.
CAUTION: If this cluster is running with multiple system disks and
common system files will be used，please，do not proceed
unless appropriate logical names are defined for cluster
common files in SYLOGICALS.COM. For instructions，refer to
the "OpenVMS Cluster Systems" manual.
Is the node to be a clustered node with a shared SCSI or Fibre Channel bus (Y/N)? Y
Will the node be a satellite [Y]? N
What is the node's SCS node name? FCNOD2
What is the node's SCSSYSTEMID number? 19.111
NOTE: 19.111 equates to an SCSSYSTEMID of 19567
Will FCNOD2 be a boot server [Y]? Y
What is the device name for FCNOD2's system root
[default DISK$V72_SSB:]? Y
What is the name of FCNOD2's system root [SYS10]?
Creating directory tree SYS10 ...
System root SYS10 created
CAUTION: If you do not define port allocation classes later in this
procedure for shared SCSI bus，all nodes sharing a SCSI bus
must have the same non-zero ALLOCLASS value. If multiple
nodes connect to a shared SCSI bus without the same allocation
class for the bus，system booting will halt due to the error or
IO AUTOCONFIGURE after boot will keep the bus offline.
Enter a value for FCNOD2's ALLOCLASS parameter [5]:
Does this cluster contain a quorum disk [N]? N
Size of pagefile for FCNOD2 [RETURN for AUTOGEN sizing]?
A temporary pagefile will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.
Size of temporary pagefile [10000]?
Size of swap file for FCNOD2 [RETURN for AUTOGEN sizing]?
A temporary swap file will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.
Size of temporary swap file [8000]?
Each shared SCSI bus must have a positive allocation class value. A shared
bus uses a PK adapter. A private bus may use: PK，DR，DV.
When adding a node with SCSI-based cluster communications，the shared
SCSI port allocation classes may be established in SYS$DEVICES.DAT.
Otherwise，the system's disk allocation class will apply.
A private SCSI bus need not have an entry in SYS$DEVICES.DAT. If it has an
entry，its entry may assign any legitimate port allocation class value:
n where n = a positive integer，1 to 32767 inclusive
0 no port allocation class and disk allocation class does not apply
-1 system's disk allocation class applies (system parameter ALLOCLASS)
When modifying port allocation classes，SYS$DEVICES.DAT must be updated
for all affected nodes，and then all affected nodes must be rebooted.
The following dialog will update SYS$DEVICES.DAT on FCNOD2.
Enter [RETURN] to continue:
$20$DKA400:<VMS$COMMON.SYSEXE>SYS$DEVICES.DAT;1 contains port
allocation classes for FCNOD2. After the next boot，any SCSI
controller not assigned in SYS$DEVICES.DAT will use FCNOD2's
disk allocation class.
Assign port allocation class to which adapter [RETURN for none]: PKA
Port allocation class for PKA0: 11
Port Alloclass 11 Adapter FCNOD2$PKA
Assign port allocation class to which adapter [RETURN for none]: PKB
Port allocation class for PKB0: 20
Port Alloclass 11 Adapter FCNOD2$PKA
Port Alloclass 20 Adapter FCNOD2$PKB
Assign port allocation class to which adapter [RETURN for none]:
WARNING: FCNOD2 must be rebooted to make port allocation class
specifications in SYS$DEVICES.DAT take effect.
Will a disk local only to FCNOD2 (and not accessible at this time to FCNOD1)
be used for paging and swapping (Y/N)? N
If you specify a device other than DISK$V72_SSB: for FCNOD2's
page and swap files，this procedure will create PAGEFILE_FCNOD2.SYS
and SWAPFILE_FCNOD2.SYS in the [SYSEXE] directory on the device you
specify.
What is the device name for the page and swap files [DISK$V72_SSB:]?
%SYSGEN-I-CREATED，$20$DKA400:[SYS10.SYSEXE]PAGEFILE.SYS;1 created
%SYSGEN-I-CREATED，$20$DKA400:[SYS10.SYSEXE]SWAPFILE.SYS;1 created
The configuration procedure has completed successfully.
FCNOD2 has been configured to join the cluster.
The first time FCNOD2 boots，NETCONFIG.COM and
AUTOGEN.COM will run automatically.
|
| 前へ | 次へ | 目次 | 索引 |