MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

ODM driver update for EVA8400 in VIO Server

 
SOLVED
Go to solution
kernel-erik
Occasional Visitor

ODM driver update for EVA8400 in VIO Server

we have an IBM VIO server (2.x)  currently with HP EVA8k and XP12k LUNs. now we are

moving them to EVA8400.

the ODM fileset we have right now is:

 

devices.fcp.disk.HP.hsv.mpio.rte                             v. 1.0.1.0

 

and to detect 8400  LUNs (which will be listed as HP 450 in AIX/VIO), 1.0.4.1. but installing the

pre-requisite version 1.0.2.0 results in error. details below of the installp

attemp:

 

installp   -ad /home/padmin/tmp/eva/HP_HSV_MPIO_1020U devices.fcp.disk.HP.hsv.mpio.rte

<snip>

installp: APPLYING software for:
        devices.fcp.disk.HP.hsv.mpio.rte 1.0.2.0


ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdDv.


ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdAt.


ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdPathAt!

update:  Failed while executing the devices.fcp.disk.HP.hsv.mpio.rte.pre_u script.


installp:  The installation has FAILED for the "usr" part
        of the following filesets:
        devices.fcp.disk.HP.hsv.mpio.rte 1.0.2.0

installp: Cleaning up software for:
        devices.fcp.disk.HP.hsv.mpio.rte 1.0.2.0

 

Installation Summary
--------------------
Name                        Level           Part        Event       Result
-------------------------------------------------------------------------------
devices.fcp.disk.HP.hsv.mpi 1.0.2.0         USR         APPLY       FAILED
devices.fcp.disk.HP.hsv.mpi 1.0.2.0         USR         CLEANUP     SUCCESS
</snip>

 

Also tried with smityt - same error.

Any ideas how to deal with this?

 

 

 

here's the READEM that comes with the tar file (from HP site):

############

============================================================
   README for the MPIO for EVA version 1.0.4.1 product.

   This version, 1.0.4.1, will recognize HSV400 and
   HSV450 disk devices provided by the EVA6400 and
   EVA8400 disk arrays.
============================================================

The MPIO for EVA version 1.0.4.1 product, HP_HSV_MPIO_1041U,
is an installable (.bff) file, and is an upgrade to the
MPIO version 1.0.2.0 product, HP_HSV_MPIO_1020U.

AIX systems with MPIO version 1.0.2.0 already installed,
may install version 1.0.4.1 without removing any HSV1xx or
HSV2xx or HSV3xx hdisk definitions from the system.

After installing version 1.0.4.1, run the cfgmgr command to
bring in the HSV4x0 Luns. The command "lsdev -Cc disk" should
now show those Luns correctly identified.

If MPIO for EVA version 1.0.2.0 has not been installed on
the system, then all versions can be installed at the
same time, from the same directory. That is why versions
1.0.1.0 and 1.0.2.0 are included in this package.

############

1 REPLY 1
kernel-erik
Occasional Visitor
Solution

Re: ODM driver update for EVA8400 in VIO Server

no solutions from both HP and IBM Support. As I've scheduled a downtim yesterday, what I came up

is to uninstall the existing ODM fileset devices.fcp.disk.HP.hsv.mpio.rte v 1.0.1 and apply the

required version (including the pre-reqs). to do this:

 

1. remove the virtual device mappings using the exising HSV210 LUNS (crazy but I can't find any other way)

2. remove the HSV210 devices

3. uninstall the 1.0.1.0 fileset

4. reboot

 

now, previous attempts comlain of the following:

 

ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdDv.
ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdAt.
ERROR: ODM definitions for device type disk/fcp/hsv300 already exist in PdPathAt!

so after rebooting, I removed those ODM entries using odmdelete. Funny that they are still

there even the fileset was removed.

the entries can be queried using:

 

odmget PdDv | grep hsv
odmget PdPathAt | grep hsv
odmget PdAt | grep hsv

 

and delete them, with the syntax like:

 

odmdelete -q "uniquetype = disk/fcp/hsv400" -o PdPathAt

 

for all the entries with hsv. after this, i was able to install the required versions:

 

<snip>

+-----------------------------------------------------------------------------+
                                Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name                        Level           Part        Event       Result
-------------------------------------------------------------------------------
devices.fcp.disk.HP.hsv.mpi 1.0.2.0         USR         APPLY       SUCCESS
devices.fcp.disk.HP.hsv.mpi 1.0.4.1         USR         APPLY       SUCCESS
devices.fcp.disk.HP.hsv.mpi 1.0.2.0         USR         COMMIT      SUCCESS
devices.fcp.disk.HP.hsv.mpi 1.0.4.1         USR         COMMIT      SUCCESS

---- end ----

[Jan 15 2012, 11:43:19]

</snip>

 

and then redefine the virtual device mappings. i needed to re-apply the reserve_policy  no_reserve attributes

on the HSV210 and HSV450 LUNS since we have a dual VIO setup.

 

and then:

 

hdisk14       Available 04-09-02      HP HSV450 Enterprise Virtual Array
hdisk15       Available 04-09-02      HP HSV450 Enterprise Virtual Array
hdisk16       Available 04-09-02      HP HSV450 Enterprise Virtual Array
hdisk17       Available 04-09-02      HP HSV450 Enterprise Virtual Array
hdisk28       Available 04-09-02      HP HSV210 Enterprise Virtual Array
hdisk29       Available 04-09-02      HP HSV210 Enterprise Virtual Array
hdisk30       Available 04-09-02      HP HSV210 Enterprise Virtual Array
hdisk31       Available 04-09-02      HP HSV210 Enterprise Virtual Array
hdisk32       Available 04-09-02      HP HSV210 Enterprise Virtual Array

 

hth.