Hey, no big deal. Everything is good.

Indeed i think i still have a few ideas. First, you need to locate the powermt command. I am quite sure you have it on the system, it is perhaps not in your PATH. i suggest to do a

Code:

# lslpp -f EMC.CLARiiON.aix.rte
# lslpp -f EMC.CLARiiON.fcp.MPIO.rte

and grep the output for powermt. Then put the path the command resides in into your PATH variable.

Then, after you have found it, do a

Code:

#powermt display dev=all

and look what comes up. We have no CLARiiON any more since a few years but if i remember correctly the CLARiiON LUNs are named the same way as the VMAX LUNs: hdiskpowerXX. You cannot use the hdisk-devices, because they represent only single paths to the LUN, you need to use the hdiskpower-pseudodevice.

I guess your hdiskpower-device is missing. I suggest to delete all the devices down to the FC-adapters, then run cfgmgr to rebuild the device hierarchy again. A hdiskpower0 should come up. Then you may try an importvg from this device, not a hdisk-device.

Still the warning of agent.kgb is correct: this might damage the LUNs content. Create a backup copy (or snapshot, but i think there is no snapshot functionality in the CLARiiON) and only then try this.

Then this:

Code:

# lspath
Enabled hdisk0 scsi0
Enabled hdisk1 scsi0
Enabled hdisk2 fscsi0
Failed  hdisk2 fscsi0

Is not looking all too kosher to me. There seems to be trouble in the connection between LUN and system. It might be the zoning, it might be something else, but otherwise there should be no failed path.

I hope this helps.

bakunin