Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VIO MPIO Pathing Question

Status
Not open for further replies.

dial8d

Technical User
Feb 6, 2006
80
GB
Been a while since ive done this, so im a little rusty.

Heres the scenario. I have 2 VIO servers running on a p570 (primary and standby) providing virtual scsi luns from a DS8000 to my client lpar.

VIO1 VTD

$ lsmap -vadapter vhost3
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost3 U9117.570.65FFE2A-V1-C50 0x00000004

VTD rspwg222FDC8K26
LUN 0x8200000000000000
Backing device hdisk70
Physloc U7879.001.DQDNWNB-P1-C4-T1-W500507630608858A-L4013402D00000000

Secondary VIO VTD

$ lsmap -vadapter vhost3
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost3 U9117.570.65FFE2A-V2-C50 0x00000004

VTD rspwg222FDC8K26
LUN 0x8200000000000000
Backing device hdisk63
Physloc U7879.001.DQDNWNA-P1-C4-T1-W500507630608858A-L4013402D00000000

Different hdisk devices, but they are the same lun on the san.

The reserve policy is set to no_reserve on both VIO servers.

On the client, the lun is pickedf up as hdisk 4, and with 2 paths out of vscsi2 and vscsi3

[root@myhost]/u01/app/oracle # lspath
Enabled hdisk0 vscsi0
Enabled hdisk1 vscsi1
Enabled hdisk4 vscsi2
Enabled hdisk4 vscsi3

My question is that dont see a child device for hdisk4 under vscsi3, only under vscsi2

[root@myhost]/u01/app/oracle # lsdev -p vscsi2
hdisk4 Available Virtual SCSI Disk Drive

[root@myhost]/u01/app/oracle # lsdev -p vscsi3
[root@myhost]/u01/app/oracle #

I was expecting to see a child device under vscsi3. Does the fact that im not mean there is a problem with MPIO on my client ?

Thanks in advance.
 
The hdisk child device gets assigned to first vscsi adapter it is discovered under.

If you see both paths with status Enabled in lspath output then you're all right.

What you also want to check is the hdisk's attribute hcheck_interval: must be set to non zero - mostly set to 60 - for disabled paths (e.g. 2nd VIO server down for upgrade) to be automatically re-set to Enabled after paths are restored (2nd VIO server back up and running).

list with:
[tt]lsattr -E -l hdisk4[/tt]
change with:
[tt]chdev -a hcheck_interval=60 -l hdisk4[/tt]
or if hdisk4 is already in use (needs a reboot sometime after):
[tt]chdev -a hcheck_interval=60 -l hdisk4 -P[/tt]



HTH,

p5wizard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top