Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Installing and Managing HP-UX Virtual Partitions (vPars) > Chapter 3 Managing Virtual Partitions

Hardware Path Formats

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Beginning with vPars version A.02.02, the way to specify hardware paths has changed. This was done so that older vPars configuration databases remain compatible with additional hardware that is being supported.

For example, given a path where its sequential digits are 4 0 1 0 0 0 0, it is not possible to determine whether this path means a device at "4/0/1/0/0.0.0" or a device at "4/0/1/0/0/0/0.0.0.0.0.0.0". The former structure is cell/sba/lba/dev/function, and the latter structure is cell/sba/lba/pci_bridge/dev/function where pci_bridge has the format m/n. Therefore, the following rules have been created. These rules apply when using either the vPars GUI or the command-line interface.

When entering a hardware path, the sequence and number of slashes (/)
and dots (.) in the hardware path that you input determines the resultant hardware path as follows:

Table 3-1 Hardware Path Format Rules

Path Format Description

Example

What the vPars Commands will do with the Entered Path

one or more occurrences of the / and .

0/1.

path will be padded

only occurrences of the /

1/0
1/0/1


path will not be padded

only occurrences of the .

1.0
1.0.

 

In the above table, padding means to pad using .0 up to six elements after the first dot.

Example Using Legacy Paths

If a path was entered using slashes and dots and while using pre-A.02.02 software, you cannot enter the same path format using A.02.02 or later software. You must enter the path using the exact same digits but with dots instead of slashes as delimiters.

For example, if a path using A.02.01 software was entered as:

  • # vparmodify -p winona2 -m io:4/0/1/0/0.0.0:BOOT

then vparstatus would show the path as "4.0.1.0.0.0.0". To do the same vparmodify command above but using A.02.02 or later, the command would be:

  • # vparmodify -p winona2 -m io:4.0.1.0.0.0.0:BOOT

To change the above path to be the ALTBOOT setting, the command is:

  • # vparmodify -p winona2 -m io:4.0.1.0.0.0.0:ALTBOOT

Example Using Combo Cards

Using vPars A.02.02, when setting a path, you can either use one or more
occurrences of the / and . in the path so that the resultant path is the correctly padded path (this path is the same as the path shown in the ioscan output), OR use a correctly padded path directly using only dots (this path is the same as the path shown in the vparstatus output).In the former case above, the ioscan output for a combo-card (combination of SCSI and LAN on a single PCI card) may show:

  • disk 0 12/0/8/0/0/4/0.0.0 ... SEAGATE ST39103LC

Then, the vPars command would be

  • # vparmodify -p winona2 -a io:12/0/8/0/0/4/0.0.0

Note that this path of 12/0/8/0/0/4/0.0.0 becomes correctly padded to 12.0.8.0.0.4.0.0.0.0.0.0.0, in accordance to the table above. Subsequently, the vparstatus output would show this path as 12.0.8.0.0.4.0.0.0.0.0.0.0, which can be used if you wish to cut and paste the path as in the command "vparmodify -p winona2 -m io:12.0.8.0.0.4.0.0.0.0.0.0.0:BOOT".

In the latter case above, the vparstatus output for a combo-card may be:

  • 12:0.8.0.0.4.0.0.0.0.0.0.0 BOOT

Then, the vPars command would be:

  • # vparmodify -p winona2 \
    -m io:12.0.8.0.0.4.0.0.0.0.0.0.0:ALTBOOT

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2002 Hewlett-Packard Development Company, L.P.