SUMMARY: New disks in EMC symmetrix - Veritas vxvm

From: John Rams <johnrams_at_cox.net>
Date: Wed Jun 04 2003 - 10:56:02 EDT
Thanks to Reggie Beavers, Bucky Swider, Dick Asteline, Bertrand Hutin, Scot
Needy, Mohan Doraiswamy, Johan Hartzenberg.

Summary from Bucky Swider's mail is: (this is the case of powerpath). Also
included all mails because all has great information.

A brief outline of the steps to see new symmetrix disks:

- If lun addresses are NOT in /kernel/drv/sd.conf:
   - add new lun addresses at the proper target
   - touch /reconfigure
   - reboot

- If lun addresses were already in sd.conf:
  - drvconfig
  - disks  (under Sol 8, you can do the same with devfsadm).

- If powerpath :
   - powercf -q
   - powermt config

- Now run 'format' to put a label on the disks
- 'vxdctl enable' to allow veritas to rescan the devices

- Use vxdisksetup/vxdiskadd/veritas gui etc. to bring the new disk into
veritas control

----------
First step is to get the emc 'inq' utility off of their website.  It shows
what disks are accessible to the host.  Then compare that list to a 'vxdisk
list' output from volume manager.  The delta is probably the new disks.  Be
sure to account for multipathing- any disks on multiple paths will show many
devices (at least one for each path, maybe one for a powerpath device, maybe
one for Veritas DMP).

There is really no good way to tell if another host is using a device.  The
person setting up the symm should only present devices to each host that is
for that host's use only.  However, for clustering, application portability,
etc. luns can be presented to multiple hosts- however, that would probably
be a situation that you would already be aware of.

Hope this helps.  Good communication with the person setting up the symm can
really ease things- they can tell you the new LUN addresses you're looking
for.
-------------------------
The person who installed the disks (eg the subsystem vendor) needs to tell
you what the LUN IDs are.

You must put these into the /kernel/drv/sd.conf against the correct Target
numbers.  You will probably figure out the target number by looking at the
existing disks' target numbers in sd.conf.

Normally each "port" on the disk subsystem gets one target number, so if
you have c2t5d6 on a specific port, and LUN-ID #7 was added to the same
port, then the new disk becomes
c2t5d7 - you add the line for taget 5 lun 7 to sd.conf and reboot.

Note:  You don't need to reboot if the tartget and LUNs are already in
sd.conf at the time of the previous reboot.  In this case you can just run
devfsadm to discover the new devices.

Once Solaris sees the new devices (creating links in /dev/dsk and
/dev/rdsk) then you can run the Veritas command "vxdctl enable".  This will
prompt the veritas config manager to re-scan the OS for new disks.  After
this, the disks are seen if you run vxdisk list.  They will have a state of
"error" untill you put them under veritas vxvm control - It is best to use
vxdiskadm for this purpose.

The difficult part is to get the target and LUN ID nrs.  The disk vendor
should give you these.  On some systems the target number is configured
using a Loop-ID on the disk subsystem, so in those cases the vendor
effectively pre-assigns the target numbers (as opposed to it being done by
Solaris and the HBA device driver).  Finally one other thing to watch out
for:  If the vendor gives you the LUN IDs, check whethet they are Hex or
Decimal.  If Hex, then first convert to Devimal before you put them into
sd.conf

  _Johan

P.S. I almost forgot.  If the new disks are "virgin disks" you need to
manually label them before "vxdctl enable" will work.  Simply do the
following:
      format
            format reports new disks detected as size XXX
      select disk
            format prompts do you want to label the disk?
      respond Y
      Then repeat for all other disks.
      Then quit.
      the run the veritas command to check the new disks
            vxdctl enable
----------------------------
You'd first want to make sure that the OS can see
these drives: 'devfsadm; vxdctl enable'  (in Solaris 8, devfsadm would do)

To look at what is on the disk: 'vxdisk -s list' and
'vxdisk list cxtxdxs2' are good.
-------------
First the target/lun needs to be in the sd.conf file.

You can use syminq (if you have solution enabler installed) or inq which at
one time could be downloaded from EMC to verify that the luns are visible.
----------------------
First to know disks are used by other systems

run

system1# vxdisk -o alldgs list
DEVICE       TYPE      DISK         GROUP        STATUS
c0t0d0s2     sliced    c0t0d0       rootdg       online
c0t1d0s2     sliced    c0t1d0       rootdg       online
c1t0d0s2     sliced    -            -            error
c1t0d125s2   sliced    c1t0d125     oradg       online
(.....edited for brevity)
c4t3d0s2     sliced    -            -            error
c4t3d164s2   sliced    -           (proddg)      online
check the disk groups... if the new disk has different name
example... proddg is new disk from other host.. that means that disk is used
by other disk group/system

or you can use inq or syminq utility from EMC to find out disk

system1# syminq

         Device                            Product              Device
------------------------- --------- ---------------------
------------------
         Name        Type  Vendor    ID               Rev  Ser Num   Cap
(KB)
-------------------------- --------- ---------------------

/dev/rdsk/c0t0d0s2         FUJITSU   MAN3184M SUN18G  1502 0149Z023 17689266

disk numbers on ser num column ... 012,052,092,0d2
make sure that disk is not seeing any system... best way ask you SAN
engineer to check the disk is zoned correctly

to add disk to Veritas

1. run
# format
see is there any new disk
if new disk not used any system so far it will ask for label

2. run
vxdctl enable

3. run

# vxdisk list
for new disk u can see like this
c1t0d165s2     sliced    -            -            error
run vxdiskadm to add disk to disk group

I hope this will help ... if not let me know

 check new disk is available
----------------------
As long as all the machines are running VxVM on Solaris, you can see the
labels with..

vxdisk -o alldgs list

The disks with a diskgroup in parenthesis are not imported, but there is
a valid diskgroup visible on the disk.  They might be in use by other
machines.
-----------------------------
first check that the Solaris devices exists with format. Use devfsadm -v to
create the devices if they are missing. You may have to fix
/kernel/drv/sd.conf if the luns are > 8.
they use vxdctl enable and vxdiskadm.
---------------------------------
Check with your EMC SA 1st but...
add this to /etc/system
*******************************************************
* Add this for Symetrix
*******************************************************
set scsi_options = 0x3f8
set sd:sd_io_time = 0x78
*


Check your sd.conf You will need to add one line per disk
Format your target an lun for your needs.

tail /kernel/drv/sd.conf
name="sd" class="scsi" target=0 lun=0;
name="sd" class="scsi" target=0 lun=1;
name="sd" class="scsi" target=0 lun=2;
name="sd" class="scsi" target=0 lun=3;
name="sd" class="scsi" target=0 lun=4;
name="sd" class="scsi" target=0 lun=5;
name="sd" class="scsi" target=0 lun=6;
name="sd" class="scsi" target=0 lun=7;
name="sd" class="scsi" target=0 lun=8;
name="sd" class="scsi" target=0 lun=9;
----------------------------

Thanks
John

  ----- Original Message -----
  From: John Rams
  To: sunmanagers@sunmanagers.org
  Sent: Wednesday, May 28, 2003 11:59 PM
  Subject: New disks in EMC symmetrix - Veritas vxvm


  Managers:

  Could you help guide me to detect what the new EMC disks are and bring them
under Veritas VxVM control? (Soalris 8, VxVM 3.1.1)

  Are there any native EMC commands to figure out what disks are configured
and what are new? Reason for this is someone in a remoe location added those
and have no idea whether those disks are being used by other systems.

  Would need to do this on a E 4500 connected to an EMC symmetrix. Format and
vxdiskadm displays so many disks that are not used.

  How to confirm though? Will summarize.

  Thanks
  John
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Wed Jun 4 10:51:02 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:11 EST