| Document revision date: 30 March 2001 | |
![]() |
|
|
|
| Previous |
There is an OpenVMS name for each Fibre Channel storage adapter, for
each path from the storage adapter to the storage subsystem, and for
each storage device. These sections apply to both disk devices and tape
devices, except for Section 1.4.2.3, which is specific to disk devices.
Tape device names are described in TBD.
1.4.2.1 Fibre Channel Storage Adapter Names
Fibre Channel storage adapter names, which are automatically assigned by OpenVMS, take the form FGx0 :
The naming design places a limit of 26 adapters per system. (For the initial release, four adapters are supported per system.) This naming may be modified in future releases to support a larger number of adapters.
Fibre Channel adapters can run multiple protocols, such as SCSI and LAN. Each protocol is a pseudodevice associated with the adapter. For the initial implementation, just the SCSI protocol is supported. The SCSI pseudodevice name is PGx0 , where x represents the same unit letter as the associated FGx0 adapter.
These names are illustrated in Figure 1-12.
Figure 1-12 Fibre Channel Initiator and Target Names
With the introduction of multipath SCSI support, as described in <REFERENCE>(mult_sup_ch), it is necessary to identify specific paths from the host to the storage subsystem. This is done by concatenating the SCSI pseudodevice name, a decimal point (.), and the WWID of the storage subsystem port that is being accessed. For example, the Fibre Channel path shown in Figure 1-12 is named PGB0.4000-1FE1-0000-0D04.
Refer to <REFERENCE>(mult_sup_ch) for more information on the
display and use of the Fibre Channel path name.
The four identifiers associated with each FC disk device are shown in
Figure 1-13. 1.4.2.3 Fibre Channel Disk Device Identification
Figure 1-13 Fibre Channel Disk Device Naming
The logical unit number (LUN) is used by the system as the address of a specific device within the storage subsystem. This number is set and displayed from the HSG console by the system manager. It can also be displayed by the OpenVMS SDA utility.
Each Fibre Channel disk device also has a WWID to provide permanent, unique identification of the device. The HSG device WWID is 128 bits. Half of this identifier is the WWID of the HSG that created the logical storage device, and the other half is specific to the logical device. The device WWID is displayed by the HSG console and the AlphaServer console.
The third identifier associated with the storage device is a user-assigned device identifier. A device identifier has the following attributes:
The device identifier has a value of 567 in Figure 1-13. This value is used by OpenVMS to form the device name so it must be unique throughout the cluster. (It may be convenient to set the device identifier to the same value as the logical unit number (LUN). This is permitted as long as the device identifier is unique throughout the cluster.)
A Fibre Channel storage device name is formed by the operating system
from the constant
$1$DGA
and a device identifier,
nnnnn
. The only variable part of the name is its device identifier, which
you assign at the HSG console. Figure 1-13 shows a storage device that
is known to the host as
$1$DGA567
.
1.5 Using the AlphaServer Console for Configuring FC
The AlphaServer console can be used to view the status of an FC
interconnect. This allows you to confirm that the interconnect is set
up properly before booting. If you plan to use an FC disk device for
booting or dumping, you must perform some additional steps to set up
those FC disk devices at the console. These topics are discussed in the
next sections.
1.5.1 Viewing the FC Configuration from the Console
Console SHOW commands can be used to display information about the devices that the console detected when it last probed the system's I/O adapters. Unlike other interconnects, however, FC disk devices are not automatically included in the SHOW DEVICE output. This is because FC devices are identified by their WWIDs, and WWIDs are too large to be included in the SHOW DEVICE output. Instead, the console provides a command for managing WWIDs, named the wwidmgr command. This command enables you to display information about FC devices and to define appropriate device names for the FC devices that will be used for booting and dumping.
Note the following points about using the wwidmgr command:
Refer to the Wwidmgr User's Manual for a complete description of the wwidmgr command.
The following examples, produced on an AlphaServer 4100 system, show some typical uses of the wwidmgr command. Other environments may require additional steps to be taken, and the output on other systems may vary slightly.
Note the following about Example 1-1:
| Example 1-1 Using wwidmgr -show wwid | ||
|---|---|---|
P00>>>set mode diag Console is in diagnostic mode P00>>>wwidmgr -show wwid polling kgpsa0 (KGPSA-B) slot 2, bus 0 PCI, hose 1 kgpsaa0.0.0.2.1 PGA0 WWN 1000-0000-c920-a7db polling kgpsa1 (KGPSA-B) slot 3, bus 0 PCI, hose 1 kgpsab0.0.0.3.1 PGB0 WWN 1000-0000-c920-a694 [0] UDID:10 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 (ev:none) [1] UDID:50 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 (ev:none) [2] UDID:51 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 (ev:none) [3] UDID:60 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 (ev:none) [4] UDID:61 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 (ev:none) |
Example 1-2 shows how the wwidmgr show wwid -full command displays information about FC devices and how they are connected. The display has two parts:
| Example 1-2 Using wwidmgr -show wwid -full | ||
|---|---|---|
P00>>>wwidmgr -show wwid -full
kgpsaa0.0.0.2.1
- Port: 1000-0000-c920-a7db
kgpsaa0.0.0.2.1
- Port: 2007-0060-6900-075b
kgpsaa0.0.0.2.1
- Port: 20fc-0060-6900-075b
kgpsaa0.0.0.2.1
- Port: 5000-1fe1-0000-0d14
- dga12274.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016
- dga15346.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026
- dga31539.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027
- dga31155.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021
- dga30963.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022
kgpsaa0.0.0.2.1
- Port: 5000-1fe1-0000-0d11
- dga12274.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016
- dga15346.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026
- dga31539.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027
- dga31155.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021
- dga30963.14.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022
kgpsab0.0.0.3.1
- Port: 1000-0000-c920-a694
kgpsab0.0.0.3.1
- Port: 2007-0060-6900-09b8
kgpsab0.0.0.3.1
- Port: 20fc-0060-6900-09b8
kgpsab0.0.0.3.1
- Port: 5000-1fe1-0000-0d13
- dgb12274.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016
- dgb15346.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026
- dgb31539.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027
- dgb31155.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021
- dgb30963.13.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022
kgpsab0.0.0.3.1
- Port: 5000-1fe1-0000-0d12
- dgb12274.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016
- dgb15346.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026
- dgb31539.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027
- dgb31155.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021
- dgb30963.14.0.3.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022
[0] UDID:10 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 (ev:none)
- current_unit:12274 current_col: 0 default_unit:12274
via adapter via fc_nport Con DID Lun
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 10
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 10
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 10
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 10
[1] UDID:50 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 (ev:none)
- current_unit:15346 current_col: 0 default_unit:15346
via adapter via fc_nport Con DID Lun
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 50
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 50
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 50
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 50
[2] UDID:51 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 (ev:none)
- current_unit:31539 current_col: 0 default_unit:31539
via adapter via fc_nport Con DID Lun
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 51
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 51
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 51
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 51
[3] UDID:60 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0021 (ev:none)
- current_unit:31155 current_col: 0 default_unit:31155
via adapter via fc_nport Con DID Lun
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 60
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 60
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 60
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 60
[4] UDID:61 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0022 (ev:none)
- current_unit:30963 current_col: 0 default_unit:30963
via adapter via fc_nport Con DID Lun
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 61
- kgpsaa0.0.0.2.1 5000-1fe1-0000-0d11 No 210213 61
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d13 Yes 210013 61
- kgpsab0.0.0.3.1 5000-1fe1-0000-0d12 No 210213 61
|
You must use the wwidmgr command to set up each device that you will use for booting or dumping. Once a device is set up, the console retains the information it requires to access the device in nonvolatile memory. You only have to rerun the wwidmgr command if the system configuration changes and the nonvolatile information is no longer valid.
The console provides a simplified setup command, called wwidmgr -quickset . This command can be used in either of the following cases:
If neither description applies to your configuration, refer to the Wwidmgr User's Manual for additional instructions.
Example 1-3 illustrates the wwidmgr -quickset command. Note the following:
| Example 1-3 Using 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
|
Example 1-4 shows a boot sequence from an FC system disk. Note the following:
| Example 1-4 Boot Sequence from an FC System Disk | ||
|---|---|---|
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
|
This section describes the basic requirements for setting up an HSG for use with OpenVMS. Note that the steps for setting up an HSG60 and an HSG80 are the same, although the examples show the output for an HSG80. Refer to the HSG80 Array Controller ACS Version 8.4 Configuration and CLI Reference Guide for more information.
These are the steps you must perform to configure an HSG for OpenVMS:
You do not need to set the controller's allocation class value. This parameter is not used by OpenVMS with the HSG. |
In current versions of OpenVMS, you must assign a device identifier to the CCL. This requirement will be removed in a future update. |
You do not need to set the logical unit's preferred path parameter. OpenVMS does not use this value in its path selection. |
| Previous | Next |
|
| privacy and legal statement | ||
| 6318FIBRE_CHANNEL_001.HTML | ||