10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
How can I shutdown a vpar from another vpar ? Please provide the command. Thanks. (0 Replies)
Discussion started by: snchaudhari2
0 Replies
2. HP-UX
Hello Guys
Could you please let me know the command to find the resource (vCPU & Memory) capacity limit for the VPAR's (HPUX 11.23) on integrity Virtual host servers running HPUX 11.31 OS.
For eg. I want to know what is the max vCPU and memory that I can assign to one VPAR.
The Base Virtual... (0 Replies)
Discussion started by: prvnrk
0 Replies
3. HP-UX
Hi guys,
I'm moving some vPars from BL860c I2 and BL870c I2 using the DRD clone and relocation. In some case, as instance to upgrade to BL870c I2, the ERRATA document reports some additional driver to be added to the image made by the DRD and then recompile the kernel before the move to the... (0 Replies)
Discussion started by: cecco16
0 Replies
4. Programming
I wasn't sure which forum to post this in. I am trying to compile logsurfer. After I run configure and the make, I get a complaint that paths.h is not found. I see three places where there is a paths.h:
/usr/include/pgsql/server/optimizer/paths.h... (3 Replies)
Discussion started by: brownwrap
3 Replies
5. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
6. HP-UX
Hi All,
Please help me out in below issue in creating vPar.
We have one nPar in which we have to create 2 vPars, out of which first vPar is already created and it is running well which have local disk as a boot device.Now we have to create 2nd vPar which need to use SAN disk for booting.... (3 Replies)
Discussion started by: laxmikant
3 Replies
7. HP-UX
Hi
Can I use a vpar as an ignite server? (1 Reply)
Discussion started by: mahlathini
1 Replies
8. UNIX for Advanced & Expert Users
There is a program that I am trying to run on a shell account. It depends on another program, which I have also copied to the shell account. Both are in my home directory, yet the first program has a different path hardcoded into it, which I cannot use because of permissions problems.
How can I... (3 Replies)
Discussion started by: fahadsadah
3 Replies
9. UNIX for Dummies Questions & Answers
Hello!
If I have file like that:
AAA
->bbb
->ccc
->ddd
->eee
how to create full paths like:
AAA->bbb
AAA->ccc->ddd
AAA->ccc->eee
?
(I'm sorry for mistakes - english is not my native language) :) (4 Replies)
Discussion started by: alias47
4 Replies
10. UNIX for Dummies Questions & Answers
Hi there!
People, i'm a new unix user, and i'm having some problems...
I'm updating some scripts (korn shell) in different servers. I use telnet to access these servers and emacs to write the scripts. One of them is an HP, and there´s no problem. But the other one is an AIX, and when i call... (1 Reply)
Discussion started by: caiohn
1 Replies
vparefiutil(1M) vparefiutil(1M)
NAME
vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database
SYNOPSIS
db_file] hw_path]
DESCRIPTION
The command displays the HP-UX hardware path to EFI path mappings that are stored in the virtual partition database. Legacy and agile
hardware paths will be displayed, if available, as provided by HP-UX. If the virtual partition database is not specified, then the live
database or by default is used. It can also be used to update the hw_path to EFI_path mappings from to the database. The behavior without
any options is to display the HP-UX hardware path to EFI path mappings.
This command is not supported on PA-RISC systems.
Options and Arguments
recognizes the following command line options and arguments:
Specifies the alternate database from which the HP-UX hardware path to EFI
path mappings need to be displayed, updated, or deleted. or live is default if this is not specified.
Updates the database from the info available (from
Displays the HP-UX hardware path to EFI path mapping in machine readable format.
Each mapping is displayed in a separate line as follows:
Deletes the HP-UX hardware path to EFI path mappings in the database.
Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed.
If this is specified, only the HP-UX hardware paths at or below the given
hw_path are displayed, updated, or deleted.
SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser.
RETURN VALUE
returns the following values:
Successful completion.
Error condition occurred.
EXAMPLES
Display the hw_path to EFI_path mappings from the live database.
# vparefiutil
Hardware path - EFI path mapping
================================
Hardware path : 2.0.0.2.0.6.0
: 2.0.0.2.0.6.0
EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.0.3.0.6.0
: 2.0.0.3.0.6.0
EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/
HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.0.3.1.2.0
: 2.0.0.3.1.2.0
EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.8.1.0.3.4.0.0.1.6
: 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.8.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.10.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.12.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
# vparefiutil
Hardware path - EFI path mapping
================================
Hardware path : 2.0.0.2.0.6.0
:
EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.0.3.0.6.0
:
EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/
HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.0.3.1.2.0
:
EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.8.1.0.3.4.0.0.1.6
: 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.8.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.10.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.12.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Display the hw_path to EFI_path mappings from the alternate database in machine readable format.
# vparefiutil -M -D vpdb_foo
2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0
2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/
Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0
2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0
2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::
2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/
EFIHPUXHPUX.EFI::
2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::
# vparefiutil -M -D vpdb_foo
2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::
2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/
Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::
2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::
2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::
2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/
Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI::
2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::
Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar.
# vparefiutil -d -H 2/0/0/3
# vparefiutil
Hardware path - EFI path mapping
================================
Hardware path : 2.0.0.2.0.6.0
:
EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.8.1.0.3.4.0.0.1.6
: 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.8.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.10.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/
EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.12.0
:
EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
# vparefiutil -d -H 2/0/0/3
# vparefiutil
Hardware path - EFI path mapping
================================
Hardware path : 2.0.0.2.0.6.0
:
EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.8.1.0.3.4.0.0.1.6
: 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
Fibre(WWN50001FE1500339ED,Lun1000000000000)/
HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.8.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.10.0
:
EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/
Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI
Hardware path : 2.0.12.1.0.4.1.12.0
:
EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/
HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI
For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path.
Hardware path : 0.0.14.0.0.0.0.0.0.2.0
EFI path : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/
VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/
HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI
SAS Address : 0x500000e01200d3f2
The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain the same. To locate SAS
devices in different OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware
path.
WARNING
The option is provided only to remove the stale HP-UX hardware path to EFI path mappings. If you remove the valid HP-UX hardware path to
EFI path mappings, you may not be able to load vpars. It is always better to follow the operation with a operation to update the database
with the valid HP-UX hardware path to EFI path mappings available from
AUTHOR
was developed by the Hewlett-Packard Company.
SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M),
vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5).
Itanium(R)-Based Systems vparefiutil(1M)