How to identify the EMC LUN ID in Solaris / HP-UX / Linux / Aix / Windows – CLARiiON arrays

Download inquiry utility from the following URL:

ftp://ftp.emc.com/pub/symm3000/inquiry/

You will get all platforms executable..eg. Just upload and change attribute to executable (Unix make it 755).

FTP directory /pub/symm3000/inquiry/v7.3.2.0/ at ftp.emc.com

To view this FTP site in Windows Explorer, click Page, and then click Open FTP Site in Windows Explorer.


Up to higher level directory

01/30/2012 10:12AM      5,524,724 inq.Celerral
01/30/2012 10:12AM     14,380,712 inq.HPUXIA64
01/30/2012 10:12AM      5,547,542 inq.LinuxAMD64
01/30/2012 10:12AM      9,145,122 inq.LinuxIA64
01/30/2012 10:12AM      5,686,240 inq.LinuxPPC64
01/30/2012 10:12AM      4,678,485 inq.aix32_51
01/30/2012 10:12AM      4,975,389 inq.aix64_51
01/30/2012 10:12AM      2,920,504 inq.exe_wnt
01/30/2012 10:12AM      8,495,104 inq.hpux1100
01/30/2012 10:12AM      9,485,952 inq.hpux64
01/30/2012 10:12AM      5,609,293 inq.linux
01/30/2012 10:12AM      5,576,300 inq.sol64
01/30/2012 10:12AM      5,433,808 inq.solar26
01/30/2012 10:12AM      5,293,017 inq.solarisx86_64
01/30/2012 10:12AM      3,286,072 inq.windowsamd64_exe
01/30/2012 10:12AM     16,913,976 inq.winia_exe
01/30/2012 10:12AM      1,887,856 inq_zLinux.zip

 

bash-3.2# ./inq.sol64 -clariion
Inquiry utility, Version V7.3-1404 (Rev 2.0)      (SIL Version V7.3.2.0 (Edit Level 1404)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

..................

--------------------------------------------------------------------------------------------------------------------------------
DEVICE                                             :VEND    :PROD            :REV   :SER NUM    :CAP(kb)      :VLU :CLUN :State
--------------------------------------------------------------------------------------------------------------------------------
/dev/rdsk/c0t321DC5813826721Dd0s2                  :LSI     :Logical Volume  :3000  :LSI Inte   :   291991552:    :    :
/dev/rdsk/c2t362F2B1ED5C8A9FAd0s2                  :LSI     :Logical Volume  :3000  :LSI Inte   :   291991552:    :    :
/dev/rdsk/c10t6006016004A03000963594D41CAAE111d0s2 :DGC     :VRAID           :0531  :484FC5B7   :    83886080:   b :00072:ASSIGNED
/dev/rdsk/c10t6006016004A030007183113A1CAAE111d0s2 :DGC     :VRAID           :0531  :414FC5B6   :   209715200:   4 :00065:ASSIGNED
/dev/rdsk/c10t6006016004A030007383113A1CAAE111d0s2 :DGC     :VRAID           :0531  :424FC5B6   :   209715200:   5 :00066:ASSIGNED
/dev/rdsk/c10t6006016004A030007583113A1CAAE111d0s2 :DGC     :VRAID           :0531  :434FC5B6   :   209715200:   6 :00067:ASSIGNED
/dev/rdsk/c10t6006016004A030007783113A1CAAE111d0s2 :DGC     :VRAID           :0531  :444FC5B6   :   209715200:   7 :00068:ASSIGNED
/dev/rdsk/c10t6006016004A030007983113A1CAAE111d0s2 :DGC     :VRAID           :0531  :454FC5B6   :   209715200:   8 :00069:ASSIGNED
/dev/rdsk/c10t6006016004A030006ACE1FC71CAAE111d0s2 :DGC     :VRAID           :0531  :474FC5B7   :   419430400:   a :00071:ASSIGNED
/dev/rdsk/c10t6006016004A030006D83113A1CAAE111d0s2 :DGC     :VRAID           :0531  :3F4FC5B6   :   209715200:   2 :00063:ASSIGNED
/dev/rdsk/c10t6006016004A030006F83113A1CAAE111d0s2 :DGC     :VRAID           :0531  :404FC5B6   :   209715200:   3 :00064:ASSIGNED
/dev/rdsk/c10t6006016004A030007B83113A1CAAE111d0s2 :DGC     :VRAID           :0531  :464FC5B6   :   209715200:   9 :00070:ASSIGNED
/dev/rdsk/c10t6006016004A030007D3CF0181CAAE111d0s2 :DGC     :VRAID           :0531  :3E4FC5B6   :   419430400:   1 :00062:ASSIGNED
/dev/rdsk/c10t6006016004A0300088C464CE1BAAE111d0s2 :DGC     :VRAID           :0531  :3D4FC5B5   :   209715200:   0 :00061:ASSIGNED

Now Just take a look at the CLUN column, this column gives the LUN ID  on the Clariion array for corresponding devices.

Veritas: Initializing A New Disk

1. Physically add the drive the system

2. Make the drive visible to the OS
a. # format
b. you will see a list of disks currently visible to the system, take note of these because you will need to identify the new disk
c. quit out of the format utility, you may need to enter quit a few times to drop out of all the menus
d. # devfsadm (note this command only works on solaris8 and newer releases)
e. # format
f. you will see a list of disks on the system, based on your notes from step b. you should be able to identify the new disk
g. select the new disk
h. it should prompt you that the disk is unlabelled and it will ask if you want to create a label now, repond yes
i. quit out of format

3. make drive visible to veritas
a. # vxdctl enable
b. # vxdisk list (you should see the new disk in the error state, not to worry, we will fix that shortly)

4. place disk under veritas control
a. # /etc/vx/bin/vxdisksetup –i cxtydz
b. # vxdisk list (the disk should now show up in the online state)

Veritas: Resizing A Veritas Volume

1. In some cases you may need to add additional disk space if there is no space available on the existing drives. Follow the steps outlined above to complete that task.

2. Once you have disk space prepared we can begin the resize.

3. NOTE: If your particular volume configuration is relies on columns you will need to have extra space on a device within each column. Example, If you have a 3 column stripe you essentially have data on 3 disks. To increase the space in this volume you will have to locate equal free space on 3 devices, in order to grow each column in the volume. These may be the same devices currently in the volume or you may need to add additional devices. It would be possible to have 2x18G drives and 2x9G drives in a 3 column stripe; you’d just have the 2x9G drives concatenated in the same column to keep overall column balance.

4. Identify available free space
# vxdg –g disk-group-name free (this command will list all areas of free space on each disk in the disk group in 512-byte blocks; note, be sure to consider data redundancy in your calculations)

5. resize the volumes
a. # /etc/vx/bin/vxresize –F filesystem-type
–g disk-group-name volume-name +size-to-add &

b. breaking down the command above, -F is either ufs or vxfs; when specifying size you can do it one of 2 ways. Either you say +size or just size. The difference being if veritas sees a plus sign he will add that much space to the existing volume. If if veritas doesn’t see a + sign he will attempt to resize the volume to what ever size you have specified. Don’t get these confused or else you could end up shrinking a volume you intended to grow.
c. # vxtask monitor (this will allow you to see the progress being made)

6. Keep in mind this is an activity that can be done on the fly, systems can remain up. It has been tested many times over and it has been proven safe.

Veritas: Setting Persistent Volume Permissions

By default, a newly created volume will only have

for the root user only, i.e below is a ‘test’ volume under disk group testdg:

/dev/vx/dsk/testdg# ls -l
total 0
brw------- 1 root root 79,76000 Jun 9 14:33 test

The on the volume can be changed by using the chmod command:

/dev/vx/dsk/testdg# chmod 777 test
/dev/vx/dsk/testdg# ls -l
total 0
brwxrwxrwx 1 root root 79,76000 Jun 9 14:33 test

However, because chmod is an OS command, after the system reboots, the on the volume are restored to what they were before, root.

In order to permanently change the , a VERITAS Volume Manager command is needed to change the permission records within the disk group configuration:

vxedit set user=username group=groupname mode=**** volumename

Here is an example:

# ls -l
total 0
brw------- 1 root root 79,76000 Jun 9 14:33 test
/dev/vx/dsk/testdg# vxedit set mode=777 test
/dev/vx/dsk/testdg# ls -l
total 0
brwxrwxrwx 1 root root 79,76000 Jun 9 14:33 test

This will allow the volume to retain its even after the system reboots.

Veritas: Replacing a bad drive

1. remove disk from veritas control if it belongs to a disk group; if it doesn’t belong to a disk group proceed to step 2
a. # vxdiskadm
b. select option 4 to “remove a disk for replacement”
c. enter the veritas disk name to remove
d. choose the disk you want to use to replace it if it exists on the server, if you are going to replace it with a new disk not in the system yet enter none
e.
2. if drive is locally attached unconfigure it (won’t apply to all hardware)
a. #cfgadm –al
b. #cfgadm –c unconfigure Ap_Id
c. if step b fails proceed to step 3
3. physically remove the drive from the disk array
4. put new disk drive in disk array
5. confirm server can see new drive(won’t apply to all hardware)
a. # cfgadm –al
b. if the occupant column is showing unconfigured for the new disk you must configure it, if it is configured proceed to step 6
c. # cfgadm –c configure Ap_Id
6. place disk under veritas control
a. # vxdiskadm
b. select option 5 “replace a failed or removed disk