Unsolved
This post is more than 5 years old
111 Posts
0
835
HPUX, VxVM, PowerPath and dead paths
Hi guys and gals,
I got a HPUX server which I migrated to another switch. As a result my /dev/cXtYdZ have changed (well actually only the 'c').
I managed to do a vgreduce on the old 'c' devices and vgextend with the new 'c' devices. So now my /etc/lvmtab looks okay.
My question is about the VxVM DGs in the server. I'm not that familiar with VxVM and all its glory
.
Here's a short output from 'powermt display dev=all':
You can see that 'c6' path is the old dead path and the 'c10' is the new one.
Here's an output from 'vxdisk path':
I'm having a problem removing the dead path from PowerPath control (powermt check force) since its been used by the VxVM.
Also what does all the "NoLicense" mean? Does that part of VxVM DMP? Do I have to disable it? How can I remove the 'c6' from VxVM? And can I do all that online?
Many questions, many thanks![:)](https://ip1.i.lithium.com/dd27beaa29a80811a70f20c8a647539eb6235b61/68747470733a2f2f636f6d6d756e6974792e656d632e636f6d2f696d616765732f656d6f7469636f6e732f68617070792e676966)
Maxim
I got a HPUX server which I migrated to another switch. As a result my /dev/cXtYdZ have changed (well actually only the 'c').
I managed to do a vgreduce on the old 'c' devices and vgextend with the new 'c' devices. So now my /etc/lvmtab looks okay.
My question is about the VxVM DGs in the server. I'm not that familiar with VxVM and all its glory
Here's a short output from 'powermt display dev=all':
root@host:/ # powermt display dev=all
Symmetrix ID=000XXXXXXXXX
Logical device ID=08D5
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
==============================================================================
10 0/3/1/0.41.2.21.0.1.2 c10t1d2 FA 7bB active alive 0 0
6 0/3/1/0.98.16.19.0.1.2 c6t1d2 FA 7bB active dead 0 1
8 0/7/1/0.42.2.19.0.1.2 c8t1d2 FA 10bB active alive 0 0
Symmetrix ID=000XXXXXXXXX
Logical device ID=08D9
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
==============================================================================
10 0/3/1/0.41.2.21.0.1.3 c10t1d3 FA 7bB active alive 0 0
6 0/3/1/0.98.16.19.0.1.3 c6t1d3 FA 7bB active dead 0 1
8 0/7/1/0.42.2.19.0.1.3 c8t1d3 FA 10bB active alive 0 0
Symmetrix ID=000XXXXXXXXX
Logical device ID=08DD
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
==============================================================================
10 0/3/1/0.41.2.21.0.1.4 c10t1d4 FA 7bB active alive 0 0
6 0/3/1/0.98.16.19.0.1.4 c6t1d4 FA 7bB active dead 0 1
8 0/7/1/0.42.2.19.0.1.4 c8t1d4 FA 10bB active alive 0 0
...
You can see that 'c6' path is the old dead path and the 'c10' is the new one.
Here's an output from 'vxdisk path':
root@host:/ # vxdisk path
SUBPATH DANAME DMNAME GROUP STATE
c6t1d2 c6t1d2 disk00 PTKM01 ENABLED
c8t1d2 c6t1d2 disk00 PTKM01 NoLicense
c10t1d2 c6t1d2 disk00 PTKM01 NoLicense
c6t1d3 c6t1d3 disk01 PTKM01 ENABLED
c8t1d3 c6t1d3 disk01 PTKM01 NoLicense
c10t1d3 c6t1d3 disk01 PTKM01 NoLicense
c6t1d4 c6t1d4 disk02 PTKM01 ENABLED
c8t1d4 c6t1d4 disk02 PTKM01 NoLicense
c10t1d4 c6t1d4 disk02 PTKM01 NoLicense
...
I'm having a problem removing the dead path from PowerPath control (powermt check force) since its been used by the VxVM.
Also what does all the "NoLicense" mean? Does that part of VxVM DMP? Do I have to disable it? How can I remove the 'c6' from VxVM? And can I do all that online?
Many questions, many thanks
Maxim
Sabey1
35 Posts
0
May 27th, 2009 12:00
Did you try to deport/import of your disk group?