Originally posted by: lslarry

ppl, got strange behavior of sddpcm.

pcmpath utility doesn't show device information. looks like somethere inside sddpcm used regexp like "hdisk??"

in aix7.1 we got perfect utility rendev. so I've renamed faceless hdiskNN to pretty hdTSKNN. and got misunderstanding from pcmpath side :)
bash-3.2# oslevel -s
7100-01-03-1207
bash-3.2# lsdev -Cc disk
hdisk0 Available 00-08-00 SAS Disk Drive
hdisk1 Available 00-08-00 SAS Disk Drive
hdora00 Available 02-08-02 IBM MPIO FC 2105
hdora01 Available 02-08-02 IBM MPIO FC 2105
hdora02 Available 02-08-02 IBM MPIO FC 2105
hdora03 Available 02-08-02 IBM MPIO FC 2105
hdps00 Available 02-08-02 IBM MPIO FC 2105
bash-3.2# lspath
Enabled hdisk0 sas0
Enabled hdisk1 sas0
Enabled hdora00 fscsi0
Enabled hdora01 fscsi0
Enabled hdps00 fscsi0
Enabled hdora02 fscsi0
Enabled hdora03 fscsi0
Enabled hdora00 fscsi0
Enabled hdora01 fscsi0
Enabled hdps00 fscsi0
Enabled hdora02 fscsi0
Enabled hdora03 fscsi0
Enabled hdora00 fscsi1
Enabled hdora01 fscsi1
Enabled hdps00 fscsi2
Enabled hdora02 fscsi1
Enabled hdora03 fscsi1
Enabled hdora00 fscsi1
Enabled hdora01 fscsi1
Enabled hdps00 fscsi2
Enabled hdora02 fscsi1
Enabled hdora03 fscsi1
Enabled hdora00 fscsi2
Enabled hdora01 fscsi2
Enabled hdps00 fscsi1
Enabled hdora02 fscsi2
Enabled hdora03 fscsi2
Enabled hdora00 fscsi2
Enabled hdora01 fscsi2
Enabled hdps00 fscsi1
Enabled hdora02 fscsi2
Enabled hdora03 fscsi2
Enabled hdora00 fscsi3
Enabled hdora01 fscsi3
Enabled hdps00 fscsi3
Enabled hdora02 fscsi3
Enabled hdora03 fscsi3
Enabled hdora00 fscsi3
Enabled hdora01 fscsi3
Enabled hdps00 fscsi3
Enabled hdora02 fscsi3
Enabled hdora03 fscsi3
bash-3.2# lscfg -vl hdps00
hdps00 U789C.001.DQD9472-P1-C4-T1-W5005076300C8A60B-L5302000000000000 IBM MPIO FC 2105

Manufacturer................IBM
Machine Type and Model......2105800
Serial Number...............30226739
EC Level....................4.25
Device Specific.(Z0)........10
Device Specific.(Z1)........0080
Device Specific.(Z2)........0075
Device Specific.(Z3)........26403
Device Specific.(Z4)........05
Device Specific.(Z5)........00

bash-3.2# pcmpath query device

Total Dual Active and Active/Asymmetrc Devices : 5

bash-3.2#pcmpath query device 1

hdisk1 is not SDDPCM supported device

bash-3.2# pcmpath query device 2

No device file found

bash-3.2# pcmpath query device hdora00

Invalid command

Usage: pcmpath query adapter <n> aa/ap
pcmpath query device <n>/<m> <n> -d <device_model> -i <x>/(<x> <y>)
pcmpath query port [n]
pcmpath query adaptstats <n> aa/ap
pcmpath query devstats <n>/<m> <n> -d <device_model> -i <x>/(<x> <y>)
pcmpath query portstats [n]
pcmpath query portmap -s
pcmpath query essmap -s
pcmpath query wwpn
pcmpath query version
pcmpath set adapter <n> online/offline aa/ap
pcmpath set device <n> path <m> online/offline
pcmpath set device <n>/(<n> <n>) algorithm rr/fo/lb/lbp
pcmpath set device <n>/(<n> <n>) hc_interval <t>
pcmpath set device <n>/(<n> <n>) hc_mode nonactive/enabled/failed
pcmpath set device <n>/(<n> <n>) cntlhc_interval <t>
pcmpath set device <n>/(<n> <n>) cntlhc_delay <t>
pcmpath set device <n>/(<n> <n>) retry_timeout <t>
pcmpath set device <n>/(<n> <n>) recoverDEDpath yes/no
pcmpath open device <n> path <m>
pcmpath clear device <n>/(<n> <n>) count error/all
pcmpath disable/enable ports <connection> ess <essid>
single port = R1-Bx-Hy-Zz
all ports on card = R1-Bx-Hy
all ports on bay = R1-Bx
refer portmap output for the connection string and ESS serial number

Examples of valid device model include:
2105 - Displays all 2105 models (ESS)
2145 - Displays all 2145 models
1750 - Displays all 1750 devices (DS 6000)
2107 - Displays all 2107 devices (DS 8000)
1724 - Displays all 1724 devices (DS 4100)
1814 - Displays all 1814 devices (DS 3950 and DS 4200 and DS 4700 and DS 5020)
1722 - Displays all 1722 devices (DS 4300)
1742 - Displays all 1742 devices (DS 4400 and DS 4500)
1815 - Displays all 1815 devices (DS 4800)
1818 - Displays all 1818 devices (DS 5000)
1820 - Displays all 1820 devices (RSSM)

bash-3.2#

Originally posted by: jvk

Most likely sddpcm does not support renamed devices (hdisks) at this time . Not sure how is with renamed fcs/fscsi but there you can hit add. problems.

Originally posted by: lslarry

bingo!
doesn't. but must, imnsho. moreover, it's simple, imho, just
'odmget -q parent="fscsiNN" CuDv'

p.s. see no reason to rename fcs

Originally posted by: SystemAdmin

rendev in many user company's opinion has not reached "safe use" status yet. just search fix central for apars/fixes...

Originally posted by: ColombianJoker

I've found bosboot command have problems with renamed disk devices too.

Originally posted by: SystemAdmin

Have you tried rebooting, or at least stopping use of the SDDPCM devices and restarting the pcmserv daemon? I would imagine that SDDPCM keeps some of this info in memory, and a rendev will likely render what's in memory invalid.