HPE Community
Operating System - HP-UX
1835272 Members
2438 Online
110078 Solutions
New Discussion

Cluster lock disk

 
SOLVED
Go to solution
catastro
Super Advisor

‎08-20-2007 12:30 AM

‎08-20-2007 12:30 AM

Cluster lock disk

Hi to all. Hi have a problem in an L3000 class server that is running HP-UX 11iv1 and Service Guard 11.16 and as I recovered my system from a crash qith an ignite tape made the same morning I revered the server, it changed the device file on HP-UX for several disks of my clariion disk enclosure. They have to bethe same as the ones that follows (this is a old ioscan):

ensnada1:/root#ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 8 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GMAU3073NC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 5 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 35
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 6 0/10/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
disk 9 0/10/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t0d2 /dev/rdsk/c7t0d2
disk 10 0/10/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t0d3 /dev/rdsk/c7t0d3
disk 13 0/10/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t0d5 /dev/rdsk/c7t0d5
disk 32 0/10/0/0.1.16.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t0d7 /dev/rdsk/c7t0d7
disk 33 0/10/0/0.1.16.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t1d0 /dev/rdsk/c7t1d0
disk 40 0/10/0/0.1.16.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t1d1 /dev/rdsk/c7t1d1
disk 44 0/10/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t1d2 /dev/rdsk/c7t1d2
disk 48 0/10/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t1d3 /dev/rdsk/c7t1d3
disk 49 0/10/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t1d4 /dev/rdsk/c7t1d4
disk 51 0/10/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t1d5 /dev/rdsk/c7t1d5
disk 53 0/10/0/0.1.16.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t1d6 /dev/rdsk/c7t1d6
disk 55 0/10/0/0.1.16.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t1d7 /dev/rdsk/c7t1d7
disk 58 0/10/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t2d0 /dev/rdsk/c7t2d0
disk 60 0/10/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t2d1 /dev/rdsk/c7t2d1
disk 61 0/10/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t2d2 /dev/rdsk/c7t2d2
disk 63 0/10/0/0.1.16.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t2d3 /dev/rdsk/c7t2d3
disk 84 0/10/0/0.1.16.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c7t2d4 /dev/rdsk/c7t2d4
disk 85 0/10/0/0.1.16.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c7t2d5 /dev/rdsk/c7t2d5
disk 15 0/10/0/0.1.17.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0
disk 19 0/10/0/0.1.17.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d2 /dev/rdsk/c13t0d2
disk 20 0/10/0/0.1.17.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d3 /dev/rdsk/c13t0d3
disk 22 0/10/0/0.1.17.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d5 /dev/rdsk/c13t0d5
disk 36 0/10/0/0.1.17.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d7 /dev/rdsk/c13t0d7
disk 37 0/10/0/0.1.17.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d0 /dev/rdsk/c13t1d0
disk 42 0/10/0/0.1.17.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t1d1 /dev/rdsk/c13t1d1
disk 46 0/10/0/0.1.17.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t1d2 /dev/rdsk/c13t1d2
disk 66 0/10/0/0.1.17.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d3 /dev/rdsk/c13t1d3
disk 67 0/10/0/0.1.17.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d4 /dev/rdsk/c13t1d4
disk 68 0/10/0/0.1.17.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d5 /dev/rdsk/c13t1d5
disk 69 0/10/0/0.1.17.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d6 /dev/rdsk/c13t1d6
disk 71 0/10/0/0.1.17.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t1d7 /dev/rdsk/c13t1d7
disk 74 0/10/0/0.1.17.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d0 /dev/rdsk/c13t2d0
disk 76 0/10/0/0.1.17.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d1 /dev/rdsk/c13t2d1
disk 78 0/10/0/0.1.17.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d2 /dev/rdsk/c13t2d2
disk 79 0/10/0/0.1.17.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d3 /dev/rdsk/c13t2d3
disk 88 0/10/0/0.1.17.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t2d4 /dev/rdsk/c13t2d4
disk 89 0/10/0/0.1.17.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d5 /dev/rdsk/c13t2d5
disk 3 0/12/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 4 0/12/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 7 0/12/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t0d3 /dev/rdsk/c8t0d3
disk 14 0/12/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t0d5 /dev/rdsk/c8t0d5
disk 34 0/12/0/0.1.16.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t0d7 /dev/rdsk/c8t0d7
disk 35 0/12/0/0.1.16.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0
disk 41 0/12/0/0.1.16.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t1d1 /dev/rdsk/c8t1d1
disk 45 0/12/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t1d2 /dev/rdsk/c8t1d2
disk 50 0/12/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d3 /dev/rdsk/c8t1d3
disk 52 0/12/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d4 /dev/rdsk/c8t1d4
disk 54 0/12/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d5 /dev/rdsk/c8t1d5
disk 56 0/12/0/0.1.16.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d6 /dev/rdsk/c8t1d6
disk 57 0/12/0/0.1.16.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t1d7 /dev/rdsk/c8t1d7
disk 59 0/12/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d0 /dev/rdsk/c8t2d0
disk 62 0/12/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d1 /dev/rdsk/c8t2d1
disk 64 0/12/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d2 /dev/rdsk/c8t2d2
disk 65 0/12/0/0.1.16.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d3 /dev/rdsk/c8t2d3
disk 86 0/12/0/0.1.16.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t2d4 /dev/rdsk/c8t2d4
disk 87 0/12/0/0.1.16.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d5 /dev/rdsk/c8t2d5
disk 18 0/12/0/0.1.17.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 23 0/12/0/0.1.17.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 24 0/12/0/0.1.17.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d3 /dev/rdsk/c12t0d3
disk 26 0/12/0/0.1.17.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d5 /dev/rdsk/c12t0d5
disk 38 0/12/0/0.1.17.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d7 /dev/rdsk/c12t0d7
disk 39 0/12/0/0.1.17.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d0 /dev/rdsk/c12t1d0
disk 43 0/12/0/0.1.17.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d1 /dev/rdsk/c12t1d1
disk 47 0/12/0/0.1.17.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d2 /dev/rdsk/c12t1d2
disk 70 0/12/0/0.1.17.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d3 /dev/rdsk/c12t1d3
disk 72 0/12/0/0.1.17.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d4 /dev/rdsk/c12t1d4
disk 73 0/12/0/0.1.17.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d5 /dev/rdsk/c12t1d5
disk 75 0/12/0/0.1.17.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d6 /dev/rdsk/c12t1d6
disk 77 0/12/0/0.1.17.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d7 /dev/rdsk/c12t1d7
disk 80 0/12/0/0.1.17.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d0 /dev/rdsk/c12t2d0
disk 81 0/12/0/0.1.17.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d1 /dev/rdsk/c12t2d1
disk 82 0/12/0/0.1.17.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d2 /dev/rdsk/c12t2d2
disk 83 0/12/0/0.1.17.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d3 /dev/rdsk/c12t2d3
disk 90 0/12/0/0.1.17.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t2d4 /dev/rdsk/c12t2d4
disk 91 0/12/0/0.1.17.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d5 /dev/rdsk/c12t2d5

And now these are the ones that appear in the ioscan:

ensnada1:/root#ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 80 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GMAU3073NC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 1 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 3 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 35
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 4 0/10/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 5 0/10/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t0d2 /dev/rdsk/c6t0d2
disk 6 0/10/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t0d3 /dev/rdsk/c6t0d3
disk 7 0/10/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t0d5 /dev/rdsk/c6t0d5
disk 8 0/10/0/0.1.16.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t0d7 /dev/rdsk/c6t0d7
disk 9 0/10/0/0.1.16.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t1d0 /dev/rdsk/c6t1d0
disk 10 0/10/0/0.1.16.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t1d1 /dev/rdsk/c6t1d1
disk 11 0/10/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t1d2 /dev/rdsk/c6t1d2
disk 12 0/10/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t1d3 /dev/rdsk/c6t1d3
disk 13 0/10/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t1d4 /dev/rdsk/c6t1d4
disk 14 0/10/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t1d5 /dev/rdsk/c6t1d5
disk 15 0/10/0/0.1.16.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t1d6 /dev/rdsk/c6t1d6
disk 16 0/10/0/0.1.16.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t1d7 /dev/rdsk/c6t1d7
disk 17 0/10/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk 18 0/10/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t2d1 /dev/rdsk/c6t2d1
disk 19 0/10/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t2d2 /dev/rdsk/c6t2d2
disk 20 0/10/0/0.1.16.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t2d3 /dev/rdsk/c6t2d3
disk 21 0/10/0/0.1.16.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c6t2d4 /dev/rdsk/c6t2d4
disk 22 0/10/0/0.1.16.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c6t2d5 /dev/rdsk/c6t2d5
disk 23 0/10/0/0.1.17.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 24 0/10/0/0.1.17.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d2 /dev/rdsk/c13t0d2
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 25 0/10/0/0.1.17.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d3 /dev/rdsk/c13t0d3
/dev/dsk/c8t0d3 /dev/rdsk/c8t0d3
disk 26 0/10/0/0.1.17.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t0d5 /dev/rdsk/c13t0d5
/dev/dsk/c8t0d5 /dev/rdsk/c8t0d5
disk 27 0/10/0/0.1.17.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t0d7 /dev/rdsk/c8t0d7
disk 28 0/10/0/0.1.17.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d0 /dev/rdsk/c13t1d0
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0
disk 29 0/10/0/0.1.17.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t1d1 /dev/rdsk/c8t1d1
disk 30 0/10/0/0.1.17.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t1d2 /dev/rdsk/c13t1d2
/dev/dsk/c8t1d2 /dev/rdsk/c8t1d2
disk 31 0/10/0/0.1.17.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d3 /dev/rdsk/c13t1d3
/dev/dsk/c8t1d3 /dev/rdsk/c8t1d3
disk 32 0/10/0/0.1.17.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d4 /dev/rdsk/c8t1d4
disk 33 0/10/0/0.1.17.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c13t1d5 /dev/rdsk/c13t1d5
/dev/dsk/c8t1d5 /dev/rdsk/c8t1d5
disk 34 0/10/0/0.1.17.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t1d6 /dev/rdsk/c8t1d6
disk 35 0/10/0/0.1.17.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t1d7 /dev/rdsk/c8t1d7
disk 36 0/10/0/0.1.17.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d0 /dev/rdsk/c13t2d0
/dev/dsk/c8t2d0 /dev/rdsk/c8t2d0
disk 37 0/10/0/0.1.17.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d1 /dev/rdsk/c8t2d1
disk 38 0/10/0/0.1.17.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d2 /dev/rdsk/c13t2d2
/dev/dsk/c8t2d2 /dev/rdsk/c8t2d2
disk 39 0/10/0/0.1.17.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c8t2d3 /dev/rdsk/c8t2d3
disk 40 0/10/0/0.1.17.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c8t2d4 /dev/rdsk/c8t2d4
disk 41 0/10/0/0.1.17.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c13t2d5 /dev/rdsk/c13t2d5
/dev/dsk/c8t2d5 /dev/rdsk/c8t2d5
disk 42 0/12/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 43 0/12/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 44 0/12/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t0d3 /dev/rdsk/c10t0d3
disk 45 0/12/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t0d5 /dev/rdsk/c10t0d5
disk 46 0/12/0/0.1.16.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t0d7 /dev/rdsk/c10t0d7
disk 47 0/12/0/0.1.16.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t1d0 /dev/rdsk/c10t1d0
disk 48 0/12/0/0.1.16.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t1d1 /dev/rdsk/c10t1d1
disk 49 0/12/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t1d2 /dev/rdsk/c10t1d2
disk 50 0/12/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t1d3 /dev/rdsk/c10t1d3
disk 51 0/12/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t1d4 /dev/rdsk/c10t1d4
disk 52 0/12/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t1d5 /dev/rdsk/c10t1d5
disk 53 0/12/0/0.1.16.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t1d6 /dev/rdsk/c10t1d6
disk 54 0/12/0/0.1.16.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t1d7 /dev/rdsk/c10t1d7
disk 55 0/12/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t2d0 /dev/rdsk/c10t2d0
disk 56 0/12/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t2d1 /dev/rdsk/c10t2d1
disk 57 0/12/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t2d2 /dev/rdsk/c10t2d2
disk 58 0/12/0/0.1.16.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t2d3 /dev/rdsk/c10t2d3
disk 59 0/12/0/0.1.16.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c10t2d4 /dev/rdsk/c10t2d4
disk 60 0/12/0/0.1.16.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c10t2d5 /dev/rdsk/c10t2d5
disk 61 0/12/0/0.1.17.0.0.0.0 sdisk CLAIMED DEVICE DGC CB
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 62 0/12/0/0.1.17.0.0.0.2 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 63 0/12/0/0.1.17.0.0.0.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d3 /dev/rdsk/c12t0d3
disk 64 0/12/0/0.1.17.0.0.0.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d5 /dev/rdsk/c12t0d5
disk 65 0/12/0/0.1.17.0.0.0.7 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t0d7 /dev/rdsk/c12t0d7
disk 66 0/12/0/0.1.17.0.0.1.0 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d0 /dev/rdsk/c12t1d0
disk 67 0/12/0/0.1.17.0.0.1.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d1 /dev/rdsk/c12t1d1
disk 68 0/12/0/0.1.17.0.0.1.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d2 /dev/rdsk/c12t1d2
disk 69 0/12/0/0.1.17.0.0.1.3 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d3 /dev/rdsk/c12t1d3
disk 70 0/12/0/0.1.17.0.0.1.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d4 /dev/rdsk/c12t1d4
disk 71 0/12/0/0.1.17.0.0.1.5 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d5 /dev/rdsk/c12t1d5
disk 72 0/12/0/0.1.17.0.0.1.6 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t1d6 /dev/rdsk/c12t1d6
disk 73 0/12/0/0.1.17.0.0.1.7 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t1d7 /dev/rdsk/c12t1d7
disk 74 0/12/0/0.1.17.0.0.2.0 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d0 /dev/rdsk/c12t2d0
disk 75 0/12/0/0.1.17.0.0.2.1 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d1 /dev/rdsk/c12t2d1
disk 76 0/12/0/0.1.17.0.0.2.2 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d2 /dev/rdsk/c12t2d2
disk 77 0/12/0/0.1.17.0.0.2.3 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d3 /dev/rdsk/c12t2d3
disk 78 0/12/0/0.1.17.0.0.2.4 sdisk CLAIMED DEVICE DGC C5
/dev/dsk/c12t2d4 /dev/rdsk/c12t2d4
disk 79 0/12/0/0.1.17.0.0.2.5 sdisk CLAIMED DEVICE DGC C0
/dev/dsk/c12t2d5 /dev/rdsk/c12t2d5

When I recovered from Ignite tape, there were some errors that made me to wonder if something went wrong in the recovery action. These errors are in the attached file.
Thanks in advance for the help in this issue.
0 Kudos
9 REPLIES 9
Steven E. Protter
Exalted Contributor

‎08-20-2007 12:44 AM

‎08-20-2007 12:44 AM

Solution

Re: Cluster lock disk

Shalom,

Probably the changes you implemented are the source of the trouble.

Fastest way to fix it is to run through cluster reconfiguration.

Change your lock disk to a device that is present in the system and run through the standard serviceguard configuration cycle.

cmquerycl
cmcheckconf
cmapplyconf

This should re-assign the cluster lock disk and get you back into normal operation.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
0 Kudos
catastro
Super Advisor

‎08-20-2007 12:57 AM

‎08-20-2007 12:57 AM

Re: Cluster lock disk

Thanks Steven. The thing is, if I perform the action you say, how is it going to end?
As I have in one server a configuration and in the other one another. The package is runnig now in a server with the first ioscan output, and the two of them have to be the same in order for the cluster to run.
My HP-Openview agent is showing me this error:

WARNING: Cluster lock disk /dev/dsk/c7t0d3 has failed: I/O error

This is happening in the server that has the second ioscan output.
Help please.
0 Kudos
Steven E. Protter
Exalted Contributor

‎08-20-2007 01:03 AM

‎08-20-2007 01:03 AM

Re: Cluster lock disk

Shalom,

I suggest not using Cluster lock disk /dev/dsk/c7t0d3 has failed: I/O error as your cluster lock disk.

I don't know your exact configuration, but to get the cluster functioning, changing the ascii configuration file and running through the three configuration steps will get you back running.

I can safely assume that this disk is not local, nor is it on a local shared scsi device.

I really think the entire problem came from the Clarion reconfiguration which seems to have created new device files.

If the device is gone from ioscan the end result of serviceguard reconfiguration will be a working cluster with a new lock disk.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
0 Kudos
Stephen Doud
Honored Contributor

‎08-20-2007 01:16 AM

‎08-20-2007 01:16 AM

Re: Cluster lock disk

If the device special files that were created by the re-ignite no longer match the configuration that used to be on the server, you have two choices;
a) re-configure /stand/ioconfig (and /etc/ioconfig) back to the way it was

2) vgexport and re-import the VGs so that the restored /etc/lvmtab is now updated with the actual paths to the VGs.

Serviceguard is only concerned about the lock disk path. Any other disk is managed by LVM via /etc/lvmtab. Serviceguard is not concerned with any other disk path.
The /etc/lvmtab is the file that contains a linkage between /dev/dsk/* disks and the actual volume group names.
If this file is no longer accurate on the re-ignited node, do the following:

1) On the node still running Serviceguard package(s), create map files of each cluster VG:
# vgexport -pvs -m /dev/
Repeat for each clustered VG

2) copy these map files to the other server:
# rcp *map ensnada1:/etc/lvmconf

On ensnada1:
3) get a list of all VG minor numbers:
# ll /dev/*/group

4) vgexport all cluster VGs
# vgexport

5) Recreate each Volume Groups' /dev/entries:
# mkdir /dev/
# mknod /dev//group c 64 0xNN0000 (where NN = the previous minor number used for this VG

6) vgimport -vs -m /etc/lvmconf/.map /dev/

Repeat for all cluster VGs.
This should correct the invalid /etc/lvmtab problem, and the packages should start on ensnada1.

To correct the problem with the cluster lock disk:

After doing the above to correct /etc/lvmtab, check for the first PV in the cluster lock VG in /etc/lvmtab:

# cmviewconf | grep vg
# strings /etc/lvmtab | more
/
The first dsk listed is most likely the FIRST_CLUSTER_LOCK_PV entry for the ensnada1 section of the cluster configuration file.
Edit the cluster configuration file and correct it with this path.
Then do a cmcheckconf -f -C

You must halt the cluster to change the cluster binary to look at the new cluster lock PV path with a cmapplyconf.
0 Kudos
catastro
Super Advisor

‎08-20-2007 08:14 PM

‎08-20-2007 08:14 PM

Re: Cluster lock disk

Hi to all.
In my /etc/lvmtab this is what I have:

On the node where the package is running (ensnada2):

/dev/vg00
/dev/dsk/c2t0d0
/dev/dsk/c1t0d0
/dev/vg01
/dev/dsk/c7t0d3
/dev/vg04
/dev/dsk/c7t0d2
/dev/vg05
/dev/dsk/c7t1d0
/dev/dsk/c7t0d7
/dev/dsk/c7t0d5
/dev/vg06
/dev/dsk/c7t1d1
/dev/dsk/c7t1d2
/dev/vg07
/dev/dsk/c7t1d6
/dev/dsk/c7t1d5
/dev/dsk/c7t1d4
/dev/dsk/c7t1d3
/dev/dsk/c7t2d4
/dev/vg08
/dev/dsk/c7t2d3
/dev/dsk/c7t2d2
/dev/dsk/c7t2d1
/dev/dsk/c7t2d5
/dev/vg09
/dev/dsk/c7t2d0
/dev/dsk/c7t1d7
/dev/vg02
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
ensnada2:/root#cmviewconf | grep vg
first lock vg name: /dev/vg01
second lock vg name: (not configured)

And in the node is now having the problem (ensnada1):

/dev/vg01
/dev/dsk/c6t0d3
/dev/dsk/c8t0d3
/dev/dsk/c10t0d3
/dev/dsk/c12t0d3
/dev/vg04
/dev/dsk/c6t0d2
/dev/dsk/c8t0d2
/dev/dsk/c10t0d2
/dev/dsk/c12t0d2
/dev/vg05
/dev/dsk/c6t0d5
/dev/dsk/c6t0d7
/dev/dsk/c6t1d0
/dev/dsk/c8t0d5
/dev/dsk/c8t0d7
/dev/dsk/c8t1d0
/dev/dsk/c10t0d5
/dev/dsk/c10t0d7
/dev/dsk/c10t1d0
/dev/dsk/c12t0d5
/dev/dsk/c12t0d7
/dev/dsk/c12t1d0
/dev/vg06
/dev/dsk/c6t1d1
/dev/dsk/c6t1d2
/dev/dsk/c8t1d1
/dev/dsk/c8t1d2
/dev/dsk/c10t1d1
/dev/dsk/c10t1d2
/dev/dsk/c12t1d1
/dev/dsk/c12t1d2
/dev/vg07
/dev/dsk/c6t1d3
/dev/dsk/c6t1d4
/dev/dsk/c6t1d5
/dev/dsk/c6t1d6
/dev/dsk/c6t2d4
/dev/dsk/c8t1d3
/dev/dsk/c8t1d4
/dev/dsk/c8t1d5
/dev/dsk/c8t1d6
/dev/dsk/c8t2d4
/dev/dsk/c10t1d3
/dev/dsk/c10t1d4
/dev/dsk/c10t1d5
/dev/dsk/c10t1d6
/dev/dsk/c10t2d4
/dev/dsk/c12t1d3
/dev/dsk/c12t1d4
/dev/dsk/c12t1d5
/dev/dsk/c12t1d6
/dev/dsk/c12t2d4
/dev/vg08
/dev/dsk/c6t2d1
/dev/dsk/c6t2d2
/dev/dsk/c6t2d3
/dev/dsk/c6t2d5
/dev/dsk/c8t2d1
/dev/dsk/c8t2d2
/dev/dsk/c8t2d3
/dev/dsk/c8t2d5
/dev/dsk/c10t2d1
/dev/dsk/c10t2d2
/dev/dsk/c10t2d3
/dev/dsk/c10t2d5
/dev/dsk/c12t2d1
/dev/dsk/c12t2d2
/dev/dsk/c12t2d3
/dev/dsk/c12t2d5
/dev/vg09
/dev/dsk/c6t1d7
/dev/dsk/c6t2d0
/dev/dsk/c8t1d7
/dev/dsk/c8t2d0
/dev/dsk/c10t1d7
/dev/dsk/c10t2d0
/dev/dsk/c12t1d7
/dev/dsk/c12t2d0
ensnada1:/root#cmviewconf | grep vg
first lock vg name: /dev/vg01
second lock vg name: (not configured)

I already tried the vgimport / vgexport issue and it did not fix the problem. I don´t know the procedure about doing it the way Steven told me, could anyone tell me how?
I assume, the cluster lock disk on ensnada1 should be /dev/dsk/c7t0d3 (as on ensnada2), but how to change it?
0 Kudos
Steven E. Protter
Exalted Contributor

‎08-20-2007 08:42 PM

‎08-20-2007 08:42 PM

Re: Cluster lock disk

Shalom,

It is interesting that disk /dev/dsk/c7t0d3

It is present on ioscan but unavailable to the cluster configuration.

You may be able to get away with this:

pvcreate /dev/rdsk/c7t0d3

or
pvcreate -f /dev/rdsk/c7t0d3

Then try again.

If not, I will endeavor to answer your latest question.

There is an ascii cluster configuration file for your serviceguard configuration. Normally it resides in /etc/cmcluster but it can be located anywhere.

The file is human readable. There is no naming convention. we name ours clustername.ascii

To change the cluster lock disk, you would find the lock configuration.

Example:

FIRST_CLUSTER_LOCK_VG /dev/vgdb
FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t0d3
# This is the cluster lock physical volume. To change it we'd change /dev/dsk/c7t0d3 to a disk available in the volume group. I can't help you pick a disk, you have to do that yourself.

cmquerycl [-k] [-w full|local|none] [-c cluster_name] [-q quorum_server|-L lock_lun_device] [-n node_name [-L lock_lun_device]]... [-l {net|lvm}] [-v] [-C cluster_ASCII_file]

cmquerycl -n node1 -n node2 -C clusername.ascii

cmcheckconf -C clustername.ascii
cmapplyconf -C clustername.ascii

Docs:
http://docs.hp.com/en/B9903-90054/ch07s04.html

I hope this helps you finish.

Thanks for the feedback.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
0 Kudos
Stephen Doud
Honored Contributor

‎08-20-2007 11:21 PM

‎08-20-2007 11:21 PM

Re: Cluster lock disk

Besides the cluster lock VG (vg01), which volume groups are used by packages? There appears to be a discrepant number of dsk paths in esnada1's lvmtab verses esnada2's /etc/lvmtab.
For example, look at vg01 (the lock VG)
On esnada1, lvmtab shows:
/dev/vg01 <<---- LOCK VG
/dev/dsk/c6t0d3
/dev/dsk/c8t0d3
/dev/dsk/c10t0d3
/dev/dsk/c12t0d3

but on esnada2's lvmtab, we see:
/dev/vg01 <<----- LOCK VG
/dev/dsk/c7t0d3

So there are 1 dsk path for vg01 in esnada2's lvmtab but 4 in esnada1's lvmtab. This is a pattern for all the VGs. (By the way, where is vg00 on esnada1's lvmtab?)
Do you know if there are alternate links to each disk? That is, are there 1, 2, 3 or 4 fibre-channel paths to each LUN?
The commands that I gave are intended to help you resolve the discrepancy between the /etc/lvmtab files using todays' /stand/ioconfig settings.
You may have to halt the packages and do the steps on BOTH nodes, to insure the /etc/lvmtab on both nodes are accurate.


If this is an urgent issue, it may be helpful to open a software support case with HP, to get specific guidance to resolve this issue.
0 Kudos
catastro
Super Advisor

‎08-21-2007 12:33 AM

‎08-21-2007 12:33 AM

Re: Cluster lock disk

Thanks for the help. The issue now has to wait till tomorrow as we have a major problem on our Simmetrix enclosure, and we have to fix it and then do all this.
In ensnada2 I do have an vg00 (I forgot to copy it), and yes, there are four alternate links to each LUN. The config that should be in both nodes is the one that is in ensnada2 (the active node now).
I´ll try all this tomorror. Till then thanks.
0 Kudos
catastro
Super Advisor

‎08-22-2007 08:55 PM

‎08-22-2007 08:55 PM

Re: Cluster lock disk

These are the steps I used and the commands I executed on my systems after the work was done in my Clariion enclosure.
Thanks to the two of you for your help.

# cmviewconf | grep -i -e "node name" -e lock
# cd /etc/cmcluster
# cmgetconf cluster.ascii
Edit the cluster.ascii file in order to include the new lock disks on it.
# cmcheckconf -C cluster.ascii
# cmhaltcl -f
# cmapplyconf -f -C cluster.ascii
# cmruncl
0 Kudos
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.