Itanium - EFI Shell - Device Mapping

[S.Rider]

How can I corelate the entries in EFI's device mapping table to the actual hardware addresses.
I physically have 2 tapes at 0/0/8/1/1.3.0 & 2/0/8/1/1.3.0, and 2 CDs at 0/0/8/1/1.1.0 & 2/0/8/1/1.1.0, and 4 disks at 0/0/1/1/0.0.0 & 0/0/8/1/0.0.0 & 2/0/1/1/0.0.0 & 2/0/8/1/0.0.0
Here's what I get from the EFI-Shell map.

Device mapping table
fs0 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigD1E35C3E-A
8A7-11DB-8002-D6217B60E588)
fs1 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigD1E35C70-A
8A7-11DB-8004-D6217B60E588)
fs2 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigE0F5386E-A
8B1-11DB-8002-D6217B60E588)
fs3 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigE0F538AA-A
8B1-11DB-8004-D6217B60E588)
fs4 : Acpi(HWP0002,PNP0A03,8)/Pci(1|1)/Scsi(Pun1,Lun0)/CDROM(Entry0)
fs5 : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigF5BDE08E
-A8A7-11DB-8002-D6217B60E588)
fs6 : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigF5BDE0C0
-A8A7-11DB-8004-D6217B60E588)
blk0 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)
blk1 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigD1E35C3E-A
8A7-11DB-8002-D6217B60E588)
blk2 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part2,SigD1E35C52-A
8A7-11DB-8003-D6217B60E588)
blk3 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigD1E35C70-A
8A7-11DB-8004-D6217B60E588)
blk4 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)
blk5 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigE0F5386E-A
8B1-11DB-8002-D6217B60E588)
blk6 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part2,SigE0F5388C-A
8B1-11DB-8003-D6217B60E588)
blk7 : Acpi(HWP0002,PNP0A03,8)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigE0F538AA-A
8B1-11DB-8004-D6217B60E588)
blk8 : Acpi(HWP0002,PNP0A03,8)/Pci(1|1)/Scsi(Pun1,Lun0)
blk9 : Acpi(HWP0002,PNP0A03,8)/Pci(1|1)/Scsi(Pun1,Lun0)/CDROM(Entry0)
blkA : Acpi(HWP0002,PNP0A03,8)/Pci(1|1)/Scsi(Pun1,Lun0)/CDROM(Entry1)
blkB : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)
blkC : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigF5BDE08E
-A8A7-11DB-8002-D6217B60E588)
blkD : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part2,SigF5BDE0AC
-A8A7-11DB-8003-D6217B60E588)
blkE : Acpi(HWP0002,PNP0A03,201)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part3,SigF5BDE0C0
-A8A7-11DB-8004-D6217B60E588)

startup.nsh> echo -off

We have 2 nPars on this SuperDome, with one running vPar in each nPar and are trying to create another vPar on each nPar.

[Sameer_Nirmal · Accepted solution]

Run these commands
# ioscan -fnkeC disk
# ioscan -fnkeC tape

[Torsten.]

As mentioned, the "-e" switch for "ioscan" will show you the EFI path.

But if the vPar is already running, you can see the assigned devices only.

Best practise - running the nPar without vPar - is to gather w full ioscan.

Based on this information, or even based on a "vparstatus -A" you can create new vPars and assign resources.

Anyway, once a install kernel is loaded, you see the common hw-pathes in the ignite install screen.

Best way to create vPars is to create a golden image of one of them and restore this image to the new instances.