GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: PVLink 31 Failed!
Operating System - HP-UX
1848176
Members
4623
Online
104022
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2008 10:27 AM
01-30-2008 10:27 AM
PVLink 31 Failed!
hi all,
I am running HP-UX 11.23 and have 4 200GB LUNS from an EVA. After creating a VG and 4 LVs each LV using 1 of the LUNS.
My Vgdisplay is as follows:
--- Volume groups ---
VG Name /dev/vgrman
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 64
Cur PV 4
Act PV 4
Max PE per PV 12799
VGDA 8
PE Size (Mbytes) 16
Total PE 51192
Alloc PE 51192
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vgrman/lvr01
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr02
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr03
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr04
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c13t0d1
PV Name /dev/dsk/c15t0d1 Alternate Link
PV Name /dev/dsk/c17t0d1 Alternate Link
PV Name /dev/dsk/c19t0d1 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d2
PV Name /dev/dsk/c17t0d2 Alternate Link
PV Name /dev/dsk/c19t0d2 Alternate Link
PV Name /dev/dsk/c13t0d2 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d3
PV Name /dev/dsk/c17t0d3 Alternate Link
PV Name /dev/dsk/c19t0d3 Alternate Link
PV Name /dev/dsk/c13t0d3 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d4
PV Name /dev/dsk/c17t0d4 Alternate Link
PV Name /dev/dsk/c19t0d4 Alternate Link
PV Name /dev/dsk/c13t0d4 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
The Server has Secure Path installed using Active/Active. There are 4 paths to the disks as you can see from the output above. Does anyone have an idea why this error keeps happening in the syslog?
Jan 30 12:09:30 Pendb3 vmunix: LVM: VG 64 0x010000: PVLink 31 0x0d0100 Failed! The PV is still accessible. Also I forgot to mention there is other storge on this server from an XP24K and it is able to use Secure Path.
Joe
I am running HP-UX 11.23 and have 4 200GB LUNS from an EVA. After creating a VG and 4 LVs each LV using 1 of the LUNS.
My Vgdisplay is as follows:
--- Volume groups ---
VG Name /dev/vgrman
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 64
Cur PV 4
Act PV 4
Max PE per PV 12799
VGDA 8
PE Size (Mbytes) 16
Total PE 51192
Alloc PE 51192
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vgrman/lvr01
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr02
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr03
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
LV Name /dev/vgrman/lvr04
LV Status available/syncd
LV Size (Mbytes) 204768
Current LE 12798
Allocated PE 12798
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c13t0d1
PV Name /dev/dsk/c15t0d1 Alternate Link
PV Name /dev/dsk/c17t0d1 Alternate Link
PV Name /dev/dsk/c19t0d1 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d2
PV Name /dev/dsk/c17t0d2 Alternate Link
PV Name /dev/dsk/c19t0d2 Alternate Link
PV Name /dev/dsk/c13t0d2 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d3
PV Name /dev/dsk/c17t0d3 Alternate Link
PV Name /dev/dsk/c19t0d3 Alternate Link
PV Name /dev/dsk/c13t0d3 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c15t0d4
PV Name /dev/dsk/c17t0d4 Alternate Link
PV Name /dev/dsk/c19t0d4 Alternate Link
PV Name /dev/dsk/c13t0d4 Alternate Link
PV Status available
Total PE 12798
Free PE 0
Autoswitch On
Proactive Polling On
The Server has Secure Path installed using Active/Active. There are 4 paths to the disks as you can see from the output above. Does anyone have an idea why this error keeps happening in the syslog?
Jan 30 12:09:30 Pendb3 vmunix: LVM: VG 64 0x010000: PVLink 31 0x0d0100 Failed! The PV is still accessible. Also I forgot to mention there is other storge on this server from an XP24K and it is able to use Secure Path.
Joe
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2008 10:49 AM
01-30-2008 10:49 AM
Re: PVLink 31 Failed!
I always forget the right command, because I don't use this software.
AFAIR a "spmgr display" will give you more information.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
AFAIR a "spmgr display" will give you more information.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2008 10:50 AM
01-30-2008 10:50 AM
Re: PVLink 31 Failed!
If I am not mistaken the 0x0d0100 translates to the c13 path. Is the error only for 0x0d0100 or it repeats for
0x0d0000
0x0d0100
0x0d0200
etc.
If it repeats for all the c13 paths, check you FC wiring and zoning.
Run ioscan and see if the devices on that path are still "CLAIMED".
0x0d0000
0x0d0100
0x0d0200
etc.
If it repeats for all the c13 paths, check you FC wiring and zoning.
Run ioscan and see if the devices on that path are still "CLAIMED".
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP