IMPORTANT: For optimal performance when configuring any P9000 disk array with a Tru64
host, HP does not recommend:
• Sharing of CHA (channel adapter) microprocessors
• Multiple host groups sharing the same CHA port
NOTE: As illustrated in “Microprocessor port sharing (OpenVMS)” (page 53), there is no
microprocessor sharing with 8-port module pairs. With 16- and 32-port module pairs, alternating
ports are shared.
Table 14 Microprocessor port sharing (OpenVMS)
Ports sharedNr. of ports per
microprocessor
DescriptionModelChannel
adapter
N/A18-port 2GB CHIP Pair8HSRAE020A
CL1 - 1 & 5; 3 & 7
CL2 - 2 & 6; 4 & 8
216-port 2GB CHIP Pair16HSRAE006A
CL1 - 1 & 5; 3 & 7
CL2 - 2 & 6; 4 & 8
232-port 2GB CHIP Pair32HSRAE007A
N/A18-port 4GB CHIP Pair8FS2RAE021A
CL1 - 1 & 5; 3 & 7
CL2 - 2 & 6; 4 & 8
216-port 4GB CHIP Pair16FS2RAE022A
CL1 - 1 & 5; 3 & 7
CL2 - 2 & 6; 4 & 8
232-port 4GB CHIP Pair32FS2RAE023A
Defining the paths
Use Command View Advanced Edition or Remote Web Console to define paths between hosts
and volumes (LUNs) in the disk array.
This process is also called “LUN mapping.” In Remote Web Console, LUN mapping includes:
• Configuring ports
• Enabling LUN security on the ports
• Creating host groups
• Assigning Fibre Channel adapter WWNs to host groups
• Mapping volumes (LDEVs) to host groups (by assigning LUNs)
Path configuration for OpenVMS requires the following steps:
1. Define one command device LUN per array and present it to the OpenVMS hosts across all
connected paths.
2. If host mode option 33 is not enabled, for all LUNs, determine the device number as follows
(once OpenVMS sees the P9000 disks):
OpenVMS device name ($1$dgaxxx), where xxx = CU with LDEV appended (Then convert
the created number from hex to decimal)
Example
For a LUN with a CU of 2 and an LDEV of 59:
CU with LDEV appended = 259
259 hex = 601 decimal
The example LUN is presented to OpenVMS as $1$dga601.
Installing and configuring the disk array 53
To Next Page
Loading...
