[HPADM] SUMMARY VG on EMC SAN



Thanks for the advice it worked fine!!!
Here was the question:
All,
What are the steps I need to do to get the new SAN disk c38t0d2, c39t0d2, c40t0d2, c41t0d2 added to there own VG???
Thanks
Will summerize!
Thomas
--------------------------------------------------------------------------------------------------
ioscan -fnC disk
<snip>
disk 42 0/12/0/0.103.3.239.0.0.2 sdisk CLAIMED DEVICE DGC CX
700WDR5
/dev/dsk/c38t0d2 /dev/rdsk/c38t0d2
disk 29 0/10/0/0.70.3.239.0.0.0 sdisk CLAIMED DEVICE DGC CX
700WDR10
/dev/dsk/c39t0d2 /dev/rdsk/c39t0d2
disk 31 0/12/0/0.103.1.239.0.0.0 sdisk CLAIMED DEVICE DGC CX
700WDR10
/dev/dsk/c40t0d2 /dev/rdsk/c40t0d2
disk 28 0/12/0/0.103.3.239.0.0.0 sdisk CLAIMED DEVICE DGC CX
700WDR10
/dev/dsk/c41t0d2 /dev/rdsk/c41t0d2
<snip>
--------------------------------------------------------------------------------------------------
Here is the "powermt display dev=all" of the other LUNS

CLARiiON ID=APM00052201060 [hostname1]
Logical device ID=600601605B5D1200 [LUN 1]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths &n bsp; Interf. Mode State Q-IOs Errors
==============================================================================
38 0/10/0/0.70.2.239.0.0.0 c38t0d0 SP A0 active alive 0 0
39 0/10/0/0.70.3.239.0.0.0 c39t0d0 SP B1 active alive 0 0
40 0/12/0/0.103.1.239.0.0.0 c40t0d0 SP A1 active alive 0 0
41 0/12/0/0.103.3.239.0.0.0 c41t0d0 SP B0 active alive 0 0
CLARiiON ID=APM00052201060 [hostname2]
Logical device ID=600601605B5D1200 [LUN 2]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
38 0/10/0/0.70.2.239.0.0.1 c38t0d1 SP A0 active alive 0 0
39 0/10/0/0.70.3.239.0.0.1 c39t0d1 SP B1 active alive 0 0
40 0/12/0/0.103.1.239.0.0.1&nbs p; c40t0d1 SP A1 active alive 0 0
41 0/12/0/0.103.3.239.0.0.1 c41t0d1 SP B0 active alive 0

Here are the answers...

----------------------------------------------------------------------
To get them into power path just run: powermt config (then they should show up when you do the display=all)

Then just do a pvcreate against one of the dev files: pvcreate /dev/rdsk/c38t0d2

Then make the VG directory : mkdir /dev/vgnew (vgname)

Then you need to make the group dev: mknod c 64 0x050000 /dev/vgnew/group ( the hex number is the minor number that must be unique among all volume groups, just do a ll /dev/vg*/group to see which ones are already used and use the next higher number ? 050000 was just an example)

Then just do a : vgcreate vgnew /dev/dsk/c38t0d2 /dev/dsk/c39t0d2 /dev/dsk/c40t0d2 /dev/dsk/c41t0d2

Should then be able to display and see: vgdisplay ?v vgnew

----------------------------------------------------------------------
If you are doing it on a production machine and not comfortable with the commands - I will suggest that first you make a full ignite recovery tape.

pvcreate all the disks (you have to make sure that the disks you chose are the new ones assigned by EMC)

First try ls -lart /dev/*/group. This will give you a list of all of the minor numbers in use. The minor number must end in 4 zeros, and the first two (hex) digits must be unique.

mkdir /dev/newvgname
mknod /dev/newvgname/group c 64 0x090000 (YOU MUST BE CAREFUL WHEN YOU CHOSE THE NUMBER HERE - IT SHOULD BE UNIQUE - I MEAN THE NO. 9 IN THIS example. ) When you did ls -lart /dev/*/group ; you should see the used minor numbers. Use the number which is not used.
pvcreate /dev/rdsk/cxtxdx (or with -f option as below to destroy the existing data on the disk ) (replace the x with the correct numbers; be careful)

pvcreate -f /dev/rdsk/cxtxdx
vgcreate /dev/newvgname /dev/dsk/cxtxdx /dev/dsk/cxtxdx

(if you want different options with the vgcreate command - just choose the correct ones; like Max PEs, PE Size, No. of PVs, etc Please make a man on vgcreate)
vgchange -a y newvgname

Then you need to make the LVs for the new VGs.
----------------------------------------------------------------------
Lets suppose that c38t0d2, c39t0d2, c40t0d2, c41t0d2 had belong to VGxx
so
RDSK=/dev/rdsk/c38t0d2 /dev/rdsk/c39t0d2 /dev/rdsk/c40t0d2 /dev/rdsk/c41t0d2
DSK=/dev/dsk/c38t0d2 /dev/dsk/c39t0d2 /dev/dsk/c40t0d2 /dev/dsk/c41t0d2
vgchgid $RDSK
mkdir /dev/VGxx
mknod /dev/VGxx/group c 64 0x0y0000
vgimport /dev/VGxx $DSK
vgchange -a y /dev/VGxx
for i in $(ls /dev/VGxx/ | grep rlvol)
do
fcck -F vxfs /dev/VGxx/rlvol${i}
done

Nous you can do mount FS

Be carrefull about the lvols number which can be differents from the original number
----------------------------------------------------------------------
Since ioscan shows the device files have been created, here are the steps:

umask 077
mkdir /dev/vgXX
mknod /dev/vgXX/group c 64 0xYY0000
pvcreate /dev/rdsk/c38t0d2
pvcreate /dev/rdsk/c39t0d2
pvcreate /dev/rdsk/c40t0d2
pvcreate /dev/rdsk/c41t0d2
vgcreate /dev/vgXX /dev/dsk/c38t0d2 /dev/dsk/c39t2d0 /dev/dsk/c40t0d2 /dev/dsk/c41t0d2

where: vgXX is whatever unique name you wantg for the VG
0xYY0000 where YY is a unique hex number for all
the current VG's. Find all the used numbers with:

ll /dev/*/group

Or you can use SAM to do the same thing. Note that most sysadmins forget the first
step (umask 077). Without this level of security, the device files are vulnerable to
ordinary users.

----------------------------------------------------------------------

----------------------------------------------------------------------





Thomas Northup

thomaslnorthup@xxxxxxxxx


---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.

Relevant Pages

  • [HPADM] new VG on EMC SAN
    ... disk 42 0/12/0/0.103.3.239.0.0.2 sdisk CLAIMED DEVICE DGC CX ...
    (HP-UX-Admin)
  • Re: missing one disk in /dev/rdsk and /dev/dsk
    ... You mean the disk is active or defect? ... The output of the ioscan command won't show the device paths. ... disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ... I agree with you that the 'insf -e' command should recreate those paths. ...
    (comp.sys.hp.hpux)
  • [HPADM] RE: how to see phisycal disks
    ... Class I H/W Path Driver S/W State H/W Type Description ... disk 0 8/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC ... Where S/W State means state of the disk. ...
    (HP-UX-Admin)
  • Re: command-line equivalents of SAM functionality
    ... Class I H/W Path Driver S/W State H/W Type Description ... disk 4 0/0/1/0.6.0 sdisk CLAIMED DEVICE HP DVD-ROM 305 ... disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE FUJITSU MAJ3182MC ...
    (comp.sys.hp.hpux)