VERITAS Volume Manager 3.2 for HP-UX Release Notes

Initializing the VERITAS Volume Manager for HP-UX

Chapter 1 53

enclosure is added to this file, VxVM does not initialize or control all disks on the

controller. For example:

$ cat /etc/vx/enclr.exclude

encl2

Step 3. Run vxinstall:

# vxinstall

The vxinstall program examines all controllers attached to the system and lists

them. You are asked if you want to use enclosure-based naming. If you do not want

to use enclosure-based names, enter n, and proceed to step 6.

Generating list of attached enclosures....

VxVM will use the following format to name disks on the host:

In the above format, <enclosurename> is the logical name of

the enclosure to which the disk belongs. VxVM assigns

default enclosure names which can be changed according

to the user requirements.

Some examples would be:

hitachi0_2 - second disk detected in enclosure

‘hitachi0’

enggdept_2 - second disk detected in enclosure

‘enggdept’

dgc1_1 - first disk detected in enclosure ‘dgc1’

jbod_1 - first disk detected in the jbod category

For non-public loop disks (Ex. FC disks directly connected to

the host or through hubs), you could choose to use the

c#t#d#s# naming format.

Do you want to use enclosure based names for all disks?

[y,n,q,?] (default: n) n

Step 4. If you want to use enclosure-based names for the disks on the system, enter y.

vxinstall detects and displays a list of disk arrays connected to your system.