VPar Issue with I/O Paths

[Virgil Chereches_2]

I have the following problem with a VPar on a SD system:
I've made a stable Vpar setup with 2 vpars, each having one cell and one I/O chassis; 2 cpus were declared unbound:

rohan.crm.orange.intra:/# vparstatus -v
[Virtual Partition Details]
Name: rohan
State: Up
Attributes: Dynamic,Autoboot
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 3/5
Bound by User [Path]: 4.10
4.11
4.12
Bound by Monitor [Path]:
Unbound [Path]: 4.13

[IO Details]
4.0
4.0.1.0.0.0.0.0.0.0.0 BOOT
4.0.1.0.0.2.0.0.0.0.0 ALTBOOT

[Memory Details]
Specified [Base /Range]:
(bytes) (MB)
Total Memory (MB): 8192
[Virtual Partition Details]
Name: boromir
State: Down
Attributes: Dynamic,Autoboot
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 3/5
Bound by User [Path]: 6.10
6.11
6.12
Bound by Monitor [Path]:
Unbound [Path]:

[IO Details]
6.0
6.0.1.0.0.0.0.0.0.0 BOOT
6.0.1.0.2.0.0.0.0.0 ALTBOOT

[Memory Details]
Specified [Base /Range]:
(bytes) (MB)
Total Memory (MB): 8192

Also, I linked the FC cards on I/O chassis owned by rohan (path 4.0) to an EMC storage directly.
If I boot the system without Vpar from the rohan's boot disk I can see disks on both I/O paths (4/0/4/0/0 and
4/0/14/0/0). Running ODE from isl show the same info (see bellow).
I/O Configuration:
Path Component Name ID Model Model Hdwr Firm
---------- ----------------------------------- ----- ----- ----- ----- -----
4/0 System Bus Adapter 7H 804H CH 0 0
4/0/0 Elroy PCI Bridge DH 782H AH 0 0
4/0/0/0/0 Serial Controller 103CH 1048H 103CH 1223H 02H
4/0/0/1/0 Ethernet Controller 1011H 0019H 103CH 104FH 41H
4/0/1 Elroy PCI Bridge DH 782H AH 0 0
4/0/1/0/0 Symbios SCSI Ultra160 LVD HBA 1000H 0021H 103CH 1330H 01H
4/0/1/0/0.0.0
HP 36.4G MAS3367NC - - - - HPC3
4/0/1/0/0.2.0
HP 36.4G MAS3367NC - - - - HPC3
4/0/2 Elroy PCI Bridge DH 782H AH 0 0
4/0/3 Elroy PCI Bridge DH 782H AH 0 0
4/0/4 Elroy PCI Bridge DH 782H AH 0 0
4/0/4/0/0 HP 6795A 2G/1G Fibre Chan. Adapter 103CH 1029H 103CH 128CH 0BH
4/0/4/0/0.8.0.35.0.0.0
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.0
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.1
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.2
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.3
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.4
EMC disk array - - - - 5670
4/0/4/0/0.8.0.35.0.1.5
EMC disk array - - - - 5670
4/0/6 Elroy PCI Bridge DH 782H AH 0 0
4/0/8 Elroy PCI Bridge DH 782H AH 0 0
4/0/9 Elroy PCI Bridge DH 782H AH 0 0
4/0/10 Elroy PCI Bridge DH 782H AH 0 0
4/0/11 Elroy PCI Bridge DH 782H AH 0 0
4/0/11/0/0 Symbios SCSI Ultra160 LVD HBA 1000H 0021H 103CH 1330H 01H
4/0/11/0/0.0.0
HPC5683A DDS4 Tape Drive - - - - C111
4/0/11/0/0.2.0
HP DVD-ROM DVD-305 - - - - 1.01
4/0/12 Elroy PCI Bridge DH 782H AH 0 0
4/0/12/0/0 Ethernet Controller 14E4H 1645H 103CH 128BH 15H
4/0/14 Elroy PCI Bridge DH 782H AH 0 0
4/0/14/0/0 HP 6795A 2G/1G Fibre Chan. Adapter 103CH 1029H 103CH 128CH 0BH
4/0/14/0/0.8.0.51.0.0.0
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.0
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.1
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.2
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.3
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.4
EMC disk array - - - - 5670
4/0/14/0/0.8.0.51.0.1.5
EMC disk array - - - - 5670

If I boot the Vpar rohan (using vpmon) the ioscan output show this:

rohan.crm.orange.intra:/# ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
cell 0 4 cell CLAIMED BUS_NEXUS
ioa 0 4/0 sba CLAIMED BUS_NEXUS System Bus Adapter (804)
ba 0 4/0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
tty 0 4/0/0/0/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/diag/mux0 /dev/mux0 /dev/tty0p0 /dev/tty0p1 /dev/tty0p2
lan 0 4/0/0/1/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0 /dev/lan0
ba 1 4/0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 0 4/0/1/0/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
target 0 4/0/1/0/0.0 tgt CLAIMED DEVICE
disk 0 4/0/1/0/0.0.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 1 4/0/1/0/0.2 tgt CLAIMED DEVICE
disk 1 4/0/1/0/0.2.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
target 2 4/0/1/0/0.7 tgt CLAIMED DEVICE
ctl 0 4/0/1/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ba 2 4/0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 3 4/0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 4 4/0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 4/0/4/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td0
fcp 0 4/0/4/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ba 5 4/0/6 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 6 4/0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 7 4/0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 8 4/0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 9 4/0/11 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 1 4/0/11/0/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
target 3 4/0/11/0/0.0 tgt CLAIMED DEVICE
tape 0 4/0/11/0/0.0.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c1t0d0BESTn /dev/rmt/c1t0d0DDSb
/dev/rmt/0mb /dev/rmt/c1t0d0BEST /dev/rmt/c1t0d0BESTnb /dev/rmt/c1t0d0DDSn
/dev/rmt/0mn /dev/rmt/c1t0d0BESTb /dev/rmt/c1t0d0DDS /dev/rmt/c1t0d0DDSnb
target 4 4/0/11/0/0.2 tgt CLAIMED DEVICE
disk 2 4/0/11/0/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
target 5 4/0/11/0/0.7 tgt CLAIMED DEVICE
ctl 1 4/0/11/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ba 10 4/0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 2 4/0/12/0/0 igelan CLAIMED INTERFACE HP A6847-60101 PCI 1000Base-SX Adapter
ba 11 4/0/14 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 4/0/14/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td1
fcp 1 4/0/14/0/0.8 fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 5 4/0/14/0/0.8.0.51.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 6 4/0/14/0/0.8.0.51.0.0 tgt CLAIMED DEVICE
disk 7 4/0/14/0/0.8.0.51.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
target 7 4/0/14/0/0.8.0.51.0.1 tgt CLAIMED DEVICE
disk 8 4/0/14/0/0.8.0.51.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 9 4/0/14/0/0.8.0.51.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d1 /dev/rdsk/c5t1d1
disk 10 4/0/14/0/0.8.0.51.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d2 /dev/rdsk/c5t1d2
disk 11 4/0/14/0/0.8.0.51.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d3 /dev/rdsk/c5t1d3
disk 12 4/0/14/0/0.8.0.51.0.1.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d4 /dev/rdsk/c5t1d4
disk 13 4/0/14/0/0.8.0.51.0.1.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d5 /dev/rdsk/c5t1d5
ext_bus 7 4/0/14/0/0.8.0.255.3 fcpdev CLAIMED INTERFACE FCP Device Interface
target 8 4/0/14/0/0.8.0.255.3.3 tgt CLAIMED DEVICE
ctl 5 4/0/14/0/0.8.0.255.3.3.0 sctl CLAIMED DEVICE EMC SYMMETRIX
/dev/rscsi/c7t3d0
memory 0 4/5 memory CLAIMED MEMORY Memory
processor 0 4/10 processor CLAIMED PROCESSOR Processor
processor 1 4/11 processor CLAIMED PROCESSOR Processor
processor 2 4/12 processor CLAIMED PROCESSOR Processor
processor 3 4/13 processor CLAIMED PROCESSOR Processor
cell 1 6 cell CLAIMED BUS_NEXUS
memory 1 6/5 memory CLAIMED MEMORY Memory
processor 4 6/13 processor CLAIMED PROCESSOR Processor
tty 1 64 vcn NO_HW DEVICE Virtual Console Client
tty 2 65 vcs NO_HW DEVICE Virtual Console Server


As one can see, no EMC disks on I/O path 4/0/4/0/0!
Searching through forum I've found the following thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=69768
and a interesting information posted by Stefan Farrelly:
-----------------------------------------------------------------------------
2. If you use the command vparmodify to add/modify i/o paths you MUST do a test boot off the primary and mirror disks after. Weve had cases of adding an i/o path, it will boot from primary, but off mirror all the i/o paths change necessitating going to lvm maintenance mode, reimporting vg00, and then reimporting all the other vg's and rebuilding the mirror. Not a nice job.

3. Know your i/o paths. Now when you add new hardware you cant see it in ioscan on any vpar until you work out its io path and add it using vparmodify first! This requires either a good manual or knowledge beforehand of exactly which slot = which io path, or a lot of trial and error!

------------------------------------------------------------------------------
It doesn't look like exactly my issue but some similarities certain exists.
Did you folks experienced such a behaviour before?
Any known workarounds?
I must mention that I've applied the latest VPar patches:

rohan.crm.orange.intra:/# swlist -l patch|grep -i vpar
# PHCO_25130 1.0 vPar manpage cumulative patch
# PHCO_28175 1.0 vPar commands man pages patch
# PHKL_24548 1.0 vPar enablement patch
# PHKL_24552 1.0 vPar enablement patch
# PHKL_24554 1.0 vPar enablement patch
# PHKL_24556 1.0 vPar enablement patch
# PHKL_24565 1.0 vPar Enablement patch
# PHKL_24585 1.0 Psets & vPar enablement patch
# PHKL_24960 1.0 vPar enablement patch
# PHKL_25080 1.0 vPar enablement patch
# PHKL_25773 1.0 Psets & vPar Enablement, Reboot Hangs
# PHKL_26037 1.0 vPar enablement patch, callout migration
# PHKL_26979 1.0 vPar enablement patch with kwdb support
# PHKL_27096 1.0 VxVM,EMC,Psets&vPar,slpq1,earlyKRS
# PHKL_27715 1.0 vPars,Interrupt Migration, IPMI
# PHKL_27750 1.0 vPar enablement, KRNG enablement
# PHKL_27757 1.0 par fans,cabtype,sinc,hwpath,cell info,vPar
# PHKL_28139 1.0 vPar enablement patch, select, nanosleep
# PHKL_28237 1.0 vPar enablement, CDUMP enablement patch
# PHKL_29243 1.0 vPar enablement, cumulative patch
# PHKL_29300 1.0 IPMI driver port, LUN change,vPar interface
# PHKL_29535 ...