MaC15

updated

16 years ago

M

MaC15

1 Rookie

36 Posts

0

3335

October 18th, 2010 07:00

IBM Power7 + Clariion + PowerPath

Hello guys,

I have this issue:

I tried to migrate from IBM Power6 to IBM Power 7. I rolled back because in AIX the bootlist didn't show the 4 paths to HD in SAN.

For example, in power 6 it shows right:

hdisk2 blv=hd5
hdisk28 blv=hd5
hdisk4
hdisk20

In power 7, I recreated the bosboot with 4 HD (bootlist -m normal hdisk2 hdisk28 hdisk4 hdisk20) but then appears only 2 HD and 2 dashes (-) :

# bootlist -m normal -o

hdisk2 blv=hd5

hdisk28

-

-

Power Path version is the last available: 5.3 SP1

==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   1 fscsi1                    hdisk20   SP A5     active  alive      0      0
   1 fscsi1                    hdisk28   SP B4     active  alive      0      0
   0 fscsi0                    hdisk2    SP B5     active  alive      0      0
   0 fscsi0                    hdisk4    SP A4     active  alive      0      0

For the record, I know that this is probably a IBM AIX issue (because powerpath shows 4 HD), but maybe it happened to someone.

Someone had the same issue ?

Thanks,

Mariano.

  • kelleg

    6 Operator

    4537 Posts

    1220

    0

    Posted November 29th, 2010 10:00

    Mariano,

    Did your procedure fix your problem? If so, could you please mark this thread as answered - that way when someone else has a similar problem, they will be able to search and use your procedure as it is "answered".

    Thanks,

    glen

  • Nollaig1

    1 Rookie

    137 Posts

    1220

    1

    Posted October 21st, 2010 06:00

    Hello Mariano,

      Have a look at knowledgebase article emc92878 in powerlink . A similar issue occurred when upgrading to ML03 in an older version of Powerpath.

    The article lists the cause and workaround as well. Might be worth checking against your system in case its something similar?

    I hope this helps,

        Nollaig

  • MaC15

    1 Rookie

    36 Posts

    1220

    0

    Posted October 21st, 2010 07:00

    Great info Nollaig. I will ckech it.

    Regards,

    Mariano.

  • MaC15

    1 Rookie

    36 Posts

    1220

    0

    Posted October 22nd, 2010 06:00

    I folowed the procedure in emc92878 and didn't work out.

    Someone here has IBM Power 7 + Boot disk in Clariion ?

    Regards,
    Mariano.

  • tcmaij

    2 Posts

    1220

    0

    Posted November 25th, 2010 07:00

    Hello,

    perhaps this has nothing to do with other hardware or os. Last weekend I had a similar problem with blv after migrating on existing systems to a higher TL level of AIX (from AIX 5.3 TL9 to 12)

    A long while ago I used this script to remove all disks in my environment:

    ==============================================================================================


    # Synchronizing Disk Names: use it when you are confused with you disks
    # Your disks will be reconfigured after a reboot. Data will be save

    #!/bin/ksh

       lsdev -Cc disk | awk '{ print $1 }' | while read HDname; do
                 odmdelete -q "name = $HDname" -o CuAt
                 odmdelete -q "value = $HDname" -o CuAt
                 odmdelete -q "name = $HDname" -o CuDv
                 odmdelete -q "value3 = $HDname" -o CuDvDr
                 odmdelete -q "name = $HDname" -o CuVPD
       done
       rm -f /dev/hdisk*
       rm -f /dev/rhdisk*
       savebase

    ==============================================================================================

    Then reboot and use the following EMC procedure: emc92878

    em:
    After upgrading AIX 5.2 to ML03 (Maintenance Level 3), the bootlist command shows - (dash) in the device list for an available hdisk# a
    below:
    Before upgrade to ML03 :
    #bootlist -m normal -o
    hdisk17
    hdisk6
    #
    After upgrade to ML03 :
    #bootlist -m normal -o
    - <--- (error)
    hdisk17
    #
    Change: Upgrade AIX 5.2 from ML02 to ML03
    Root Cause:
    This issue has been seen if the hdiskpower entry is located before hdisk entry in the ODM CuDv table. AIX code checks the first device th
    the wwpm and LUN and assumes that all devices are of subclass "fcp".
    The first device matched in this case is hdiskpower0 because it has the same wwpn and lun#. However, the subclass is "pseudo" which i
    recognised by AIX code.
    Fix:
    In this fix description , we are assuming that rootvg is on hdiskpower0
    #powermt display dev=0
    Pseudo name=hdiskpower0
    Symmetrix ID=000287460464
    Logical device ID=027F
    state=alive; policy=SymmOpt; priority=0; queued-IOs=0
    ==============================================================================
    ---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
    ### HW Path I/O Paths Interf. Mode State Q-IOs Errors
    ==============================================================================
    1 fscsi1 hdisk17 FA 13cA active alive 0 0
    0 fscsi0 hdisk6 FA 4cA active alive 0 0
    #bootlist -m normal -o
    hdisk17
    - <<<<<<< hdisk6 is missing
    #
    Procedure :
    1. save hdiskpower0 entry in a file : odmget -q"name=hdiskpower0" CuDv > /tmp/hdiskpower0.add
    2. save hdisk6 (hdisk with - in bootlist) entry in a file : odmget -q"name=hdisk6" CuDv > /tmp/hdisk6.add
    3. delete hdiskpower0 entry fron CuDv : odmdelete -o CuDv -q"name=hdiskpower0"
    4. delete hdisk6 entry fron CuDv : odmdelete -o CuDv -q"name=hdisk6"
    5. adds hdisk6 back : odmadd /tmp/hdisk6.add
    6. check if bootlist is ok : bootlist -m normal -o
    7. adds hdiskpower0 back : odmadd /tmp/hdiskpower0.add
    8. check if bootlist is ok : bootlist -m normal -o
    9. if all the above is ok , you can save the changes to boot image : savebase -v
    10. reboot the host
    11. check if bootlist is ok : bootlist -m normal -o
    or for more details : bootlist -m normal -v -r

    In my case I removedall hdiskpowerX entries before the hdisk with blv on it. Try it out!

  • MaC15

    1 Rookie

    36 Posts

    1220

    0

    Posted November 25th, 2010 09:00

    The solution was remove all hdiskpower and reinstall Power Path.

    Maybe my procedure could help someone else:

    1)

    pprootdev off

    Reboot

    2)

    cp /etc/objrepos/CuAt /etc/objrepos/CuAt.bak

    cp /etc/objrepos/CuDv /etc/objrepos/CuDv.bak

    cp /etc/objrepos/CuDvDr /etc/objrepos/CuDvDr.bak

    cp /etc/objrepos/CuVPD /etc/objrepos/CuVPD.bak

    3)

    vary off all the volume groups (apart from rootvg, of course)

    4)

    powermt remove dev=all

    lsdev -Cc disk -Fname | grep power | xargs -n1 rmdev -dl

    odmdelete -q "name like hdiskpower*" -o CuAt

    odmdelete -q "name like hdiskpower*" -o CuDv

    odmdelete -q "value3 like hdiskpower*" -o CuDvDr

    odmdelete -q "name like hdiskpower*" -o CuVPD

    odmdelete -q name=powerpath0 -o CuDv

    odmdelete -q name=powerpath0 -o CuAt

    odmdelete -q value3=powerpath0 -o CuDvDr

    rm /dev/powerpath0

    5)

    Remove PowerPath software: 

    /etc/rc.agent stop

    installp -u EMCpower

    6)

    cd /dev

    rm hdiskpower*

    rm rhdiskpower*

    7)

    odmget CuAt | grep hdiskpower

    odmget CuDv  | grep hdiskpower

    odmget CuDvDr  | grep hdiskpower

    odmget CuVPD | grep hdiskpower

    odmget CuDep  | grep hdiskpower

    8)

    bosboot -ad /dev/ipldevice

    savebase -v

    Reboot

    9)

    Install PowerPath:

    installp -agXd . EMCpower

    10)

    /usr/lpp/EMC/CLARiiON/bin/emc_cfgmgr

    powermt config

    11) Create bootlist:

        bootlist -m normal hdisk1 hdisk2 hdisk3 hdisk4

        bootlist -m normal -o

        bosboot -ad /dev/ipldevice   

    (Check if dash gone).

    12) pprootdev on

    13) Reboot.

    14) bootlist -m normal -o

    Regards,

    Mariano.

  • MaC15

    1 Rookie

    36 Posts

    1220

    0

    Posted November 29th, 2010 14:00

    Yes, it worked with the procedure I posted (item 5).

    Done.

    Thanks!