Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

EVA8100 + AIX 5.3 + MPIO not working

enyamada
Advisor

EVA8100 + AIX 5.3 + MPIO not working

Hi.

I´m trying to make a AIX 5.3 (from a LPAR) use vdisks from a EVA8100 box with a FC5759 HBA.

I´m following the http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00373254/c00373254.pdf document.

Before I install the HP ODM fileset, lspv shows 4 hdisks for a single real hdisk, and I can use it with no problem.

However, after installing the fileset, the 4 hdisks become a single one (OK), and other commands show no problem:

{root@sbetb2605}/opt/hphsv/bin> hsvpaths
Disk LUNx LUNd VG S Status T E D F M HBAs Node WWN Ports
hdisk7 1 1 None - Good 4 4 0 0 0 fscsi2 50001fe1500d8df0 d,9,e,a
{root@sbetb2605}/opt/hphsv/bin> lspath
.
.
.
Enabled hdisk7 fscsi2
Enabled hdisk7 fscsi2
Enabled hdisk7 fscsi2
Enabled hdisk7 fscsi2
.
.


However, I can't access this hdisk:

{root@sbetb2605}/opt/hphsv/bin> importvg -y vg1 hdisk7
0516-024 lqueryvg: Unable to open physical volume.
Either PV was not configured or could not be opened. Run
diagnostics.
0516-024 lqueryvg: Unable to open physical volume.
Either PV was not configured or could not be opened. Run
diagnostics.
0516-1140 importvg: Unable to read the volume group descriptor area
on specified physical volume.


and right after I try that, the paths are not ok:

{root@sbetb2605}/opt/hphsv/bin> hsvpaths
Disk LUNx LUNd VG S Status T E D F M HBAs Node WWN Ports
hdisk7 1 1 None - BAD 4 0 0 4 0 fscsi2 50001fe1500d8df0 d,9,e,a
{root@sbetb2605}/opt/hphsv/bin> lspath
.
.
Failed hdisk7 fscsi2
Failed hdisk7 fscsi2
Failed hdisk7 fscsi2
Failed hdisk7 fscsi2
.
.



Any ideas?

Thank you very much

10 REPLIES
Rob Leadbeater
Honored Contributor

Re: EVA8100 + AIX 5.3 + MPIO not working

Hi,

Not too sure on AIX, but have you followed the prerequisites in the platform notes here:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01078023/c01078023.pdf

Hope this helps,

Regards,

Rob
enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

Hi

Yes, all the prerequisites were fulfilled.

Thank you

Bret Graham
Valued Contributor

Re: EVA8100 + AIX 5.3 + MPIO not working

AIX 5.3 with which TL? Can you post the output from 'oslevel -s'? Are you certain that you setup this host in Command View EVA with ostype of "IBM AIX"?

With an EVA8100 I would expect to see 8 paths and not 4 unless you specifically zoned out half the EVA ports. Could you post the output of 'lshsv -p' which is located in /opt/hphsv/bin?

I am on vacation beginning tomorrow but not leaving until tomorrow late morning pacific time. If you can post the data, I'll have a look and see if I can't tell you the problem.

Bret
enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

Hi.

I see only 4 paths because I'm using a single HBA. Anyway, testing with 2 HBAs has similar results (8 paths but with the same problem).

Here's a session:

{root@sbetb2606}/> oslevel -s
5300-06-00-0000

{root@sbetb2606}/> cfgmgr
Method error (/usr/lib/methods/cfgefscsi -l fscsi1 ):
0514-061 Cannot find a child device.
{root@sbetb2606}/> lspv
hdisk0 0003f7633d4523af rootvg active
hdisk1 0003f763702123cf rootvg active
hdisk5 0003f76387a4d7f4 ora-bin-vg
hdisk16 0003f7638bc4bb82 ora-hm-redo-vg
hdisk20 0003f7638bb88a12 ora-hm-data-vg
hdisk21 0003f7638bb8e1ad ora-hm-arch-vg
{root@sbetb2606}/> varyo
varyoffvg varyonvg
{root@sbetb2606}/> varyonvg ora-bin-vg
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
{root@sbetb2606}/> varyonvg ora-hm-redo-vg
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
{root@sbetb2606}/> varyonvg ora-hm-data-vg
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
{root@sbetb2606}/> varyonvg ora-hm-arch-vgf
0516-008 varyonvg: LVM system call returned an unknown
error code (3).
{root@sbetb2606}/> varyonvg ora-hm-arch-vg
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
{root@sbetb2606}/> hsvpaths
Disk LUNx LUNd VG S Status T E D F M HBAs Node WWN Ports
hdisk5 2 2 ora-bin-vg - BAD 4 0 0 4 0 fscsi0 50001fe1500d8df0 d,9,e,a
hdisk16 4 4 ora-hm-redo-vg - BAD 4 0 0 4 0 fscsi0 50001fe1500d8df0 d,9,e,a
hdisk20 1 1 ora-hm-data-vg - BAD 4 0 0 4 0 fscsi0 50001fe1500d8df0 e,a,d,9
hdisk21 3 3 ora-hm-arch-vg - BAD 4 0 0 4 0 fscsi0 50001fe1500d8df0 e,a,d,9
{root@sbetb2606}/> lshsv -p
Disk HBA PortWWN LUN PID Prio Status UUID HBA-Location NPortID
hdisk5 fscsi0 50001fe1500d8dfd 2000000000000 0 1 Failed 600508B4000685330000D00001290000 U787B.001.DNWFX2G-P1-C1-T1 0x30d00
hdisk5 fscsi0 50001fe1500d8df9 2000000000000 1 1 Failed 600508B4000685330000D00001290000 U787B.001.DNWFX2G-P1-C1-T1 0x30e00
hdisk5 fscsi0 50001fe1500d8dfe 2000000000000 2 1 Failed 600508B4000685330000D00001290000 U787B.001.DNWFX2G-P1-C1-T1 0x40200
hdisk5 fscsi0 50001fe1500d8dfa 2000000000000 3 1 Failed 600508B4000685330000D00001290000 U787B.001.DNWFX2G-P1-C1-T1 0x40300
hdisk16 fscsi0 50001fe1500d8dfd 4000000000000 0 1 Failed 600508B4000685330000D000014E0000 U787B.001.DNWFX2G-P1-C1-T1 0x30d00
hdisk16 fscsi0 50001fe1500d8df9 4000000000000 1 1 Failed 600508B4000685330000D000014E0000 U787B.001.DNWFX2G-P1-C1-T1 0x30e00
hdisk16 fscsi0 50001fe1500d8dfe 4000000000000 2 1 Failed 600508B4000685330000D000014E0000 U787B.001.DNWFX2G-P1-C1-T1 0x40200
hdisk16 fscsi0 50001fe1500d8dfa 4000000000000 3 1 Failed 600508B4000685330000D000014E0000 U787B.001.DNWFX2G-P1-C1-T1 0x40300
hdisk20 fscsi0 50001fe1500d8dfe 1000000000000 0 1 Failed 600508B4000685330000D00001530000 U787B.001.DNWFX2G-P1-C1-T1 0x40200
hdisk20 fscsi0 50001fe1500d8dfa 1000000000000 1 1 Failed 600508B4000685330000D00001530000 U787B.001.DNWFX2G-P1-C1-T1 0x40300
hdisk20 fscsi0 50001fe1500d8dfd 1000000000000 2 1 Failed 600508B4000685330000D00001530000 U787B.001.DNWFX2G-P1-C1-T1 0x30d00
hdisk20 fscsi0 50001fe1500d8df9 1000000000000 3 1 Failed 600508B4000685330000D00001530000 U787B.001.DNWFX2G-P1-C1-T1 0x30e00
hdisk21 fscsi0 50001fe1500d8dfe 3000000000000 0 1 Failed 600508B4000685330000D00001590000 U787B.001.DNWFX2G-P1-C1-T1 0x40200
hdisk21 fscsi0 50001fe1500d8dfa 3000000000000 1 1 Failed 600508B4000685330000D00001590000 U787B.001.DNWFX2G-P1-C1-T1 0x40300
hdisk21 fscsi0 50001fe1500d8dfd 3000000000000 2 1 Failed 600508B4000685330000D00001590000 U787B.001.DNWFX2G-P1-C1-T1 0x30d00
hdisk21 fscsi0 50001fe1500d8df9 3000000000000 3 1 Failed 600508B4000685330000D00001590000 U787B.001.DNWFX2G-P1-C1-T1 0x30e00


Thank you
Bret Graham
Valued Contributor

Re: EVA8100 + AIX 5.3 + MPIO not working

I am wondering if that config method error is being caused by only having one of the two ports connected on that HBA.

One idea is to use the chdev command to disble reservations on the EVA hdisks. Your command would like this:

chdev -l hdisk5 -a reserve_policy=no_reserve

I have run into this once before where something is scanning or similar and reserving the disks.

If it works after dsabling reservations, something else is going on but I am not sure what. You may want to verify the config method error and if no_reserve works, with IBM, as this MPIO solution is supported by both IBM and HP.

If this LPAR will not need to share these specific EVA disks, then using no_reserve is not very dangerous but you must make sure you never present these same vdisks to another LPAR or server. If this LPAR will be a VIO Server or an HACMP node, then you need to disable reservations anyway.

Bret
enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

Unfortunately, changing the reserve_policy didnt work.

Yes, the method error is caused by the absence of a fiber; if I connect one or disable that port (chdev -a autoconfig=defined -l 'fscsiX'), the error dissapears.

Thank you very much.
Tom O'Toole
Respected Contributor

Re: EVA8100 + AIX 5.3 + MPIO not working

I bet you need a new fileset for eva 8100.
Can you imagine if we used PCs to manage our enterprise systems? ... oops.
enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

I´ve already tested the server with a EVA4000 we have here and the same thing happens... So, it doesnt look like to be a EVA8100 issue.


Tks
enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

Hi.

Just in case, I've applied the latest AIX service pack (5300-06-03-0732), although the system was already on a level that is theoretically supported, and... it worked out just on the first try! (no adjust at all).

Thank you every one.

Edson

enyamada
Advisor

Re: EVA8100 + AIX 5.3 + MPIO not working

Solution: apply 5300-06-03-0732 sp.