How get more LUN info

Operating Systems Linux Red Hat How get more LUN info

10-26-2006

Registered User

25, 0

Join Date: Oct 2002

Last Activity: 22 October 2012, 9:20 AM EDT

Posts: 25

Thanks Given: 0

Thanked 0 Times in 0 Posts

How get more LUN info

Hello,

I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ...

Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1 of 3!)... I've found the /proc/scsi/scsi area, but need more info, ie what filer is serving the LUN.

Can someone point me in the right direction?

Thanks

itsupplies

View Public Profile for itsupplies

Find all posts by itsupplies

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Resize Lun

Good afternoon! Help with a solution I have AIX 7.1 works through vios I expanded Lun that it is necessary to make that aix saw this change and to expand the section lvm Sorry for my English

2. UNIX for Dummies Questions & Answers

Which disk is LUN?

how do I know which hdisk from "lsdev -Cc disk" is my LUN on NetApp after zoning from SAN switch? is it "MPIO other FC SCSI Disk Drive"?

3. AIX

Not getting Lun Id

Hi, I am not getiting lun id information on VIO Server. I have used the command fget_config command. just showing # prompt. I would like know wheather any other command is there equiv of fget_config which will display lun id?

4. Emergency UNIX and Linux Support

Reuse a LUN

I have a LUN (From HP-Storage VA7110) that is claimed on 2 servers, but is in used in one of the VG on Server-1 . Now I want to shut Server-1 and re-use that LUN on server-2 . Server-1 Path-1 : /dev/rdsk/c4t0d1 Path-2: /dev/rdsk/c6t0d1 Server-2 Path-1: /dev/rdsk/c5t0d1 Path-2:...

5. Red Hat

How to configure LUN

Hi ALL, what are the steps to detect and configure a new attached lun in RHEL 5.3. rgds, snj.

6. HP-UX

Mounting LUN on HP 11.31

Hello, I want monting a LUN on a RX2660 I have created a LUN of 100Go with HP StorageWorks EVA and associated to my server. For the moment I see it with the command below but after i can't used it # ioscan -fnkC disk Class I H/W Path Driver S/W State H/W Type Description ...

7. Solaris

I have LUN ID, how to find disk relate to that LUN ID?

I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer. thanks

8. Solaris

LUN not ready

hey guys i got this in my logs what does this mean:

9. AIX

Map lun info to phyical disks

I have been ask to write a script to show what phyical disks are linked to what luns. By host name. I was hoping someone had some ideas on how to do this. I am from a linux background and am struggling a bit here...lol...I have been given one command to help me out....lsmap..Anyhelp would be...

10. Solaris

LUN / Diskgroup info

Hi, I was just about to decommission a box when a weird question paused the operation. This box has veritas volume manager installed. I was umounting all the vx volumes and deleting the disk groups so that the storage admin can take back the LUNS. Now this is where i am stuck - i see a disk...

LEARN ABOUT HPUX

cmdisklock

cmdisklock(1m)															    cmdisklock(1m)

NAME

       cmdisklock - manage Serviceguard cluster lock devices.

SYNOPSIS

       cmdisklock check path
       cmdisklock [-f] reset path

DESCRIPTION

       cmdisklock is a tool to check the current state of a Serviceguard cluster lock device.  It can also be used to reset the state of the clus-
       ter lock device.  The need to reset the cluster lock device state could arise if the cluster lock device is replaced or becomes corrupt.

       A cluster lock device can be either an HP-UX LVM cluster lock or a cluster lock LUN device.  HP-UX LVM cluster locks exist only on  a  disk
       in an LVM volume group.	Cluster lock LUNs exist only on disks dedicated to cluster lock.  cmdisklock is useful for checking either type of
       cluster lock and for re-initializing cluster lock LUN devices after a failure or corruption.

       NOTE
       To restore an HP-UX LVM cluster lock, use vgcfgrestore.	cmdisklock will fail until vgcfgrestore is run, and cmdisklock is  unnecessary	as
       long as vgcfgbackup was done after the cluster lock was initialized.  See the Managing Serviceguard manual for details.

       The  syntax  of	the  path  option  depends  on	the  type  of  lock.  For  HP-UX LVM cluster lock disks, the syntax is VG:PV (for example:
       /dev/vglock:/dev/dsk/c0t0d2).  For cluster lock LUN disks, the path is the  disk  device  path.	 For  example,	/dev/sdd1  (on	Linux)	or
       /dev/dsk/c0t1d2 (on HP-UX).

   Options
       cmdisklock supports the following options:

	      check	       Check the current state of the cluster lock device and report the results.

	      reset	       Reset (initialize) the state of the cluster lock device.  This operation should only be performed on a cluster lock
			       LUN device.  For HP-UX LVM cluster lock, use vgcfgrestore as documented in the Managing Serviceguard manual.  After
			       performing a reset, a check can be used to verify that the lock is cleared.

EXAMPLES

       If the cluster lock LUN device becomes corrupted and the cluster is up, messages like the following will appear in syslog.

       Mar  15	12:20:41  usb  cmdisklockd[17599]:  WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label.  Until this situation is cor-
       rected, a single failure could cause all nodes in the cluster to crash.
       Mar 15 12:20:41 usb cmdisklockd[17599]: After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset
       /dev/dsk/c0t1d2' to repair
       Mar 15 12:20:41 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is inaccessible

       Once the above messages appear in syslog on all running nodes, the following command will re-initialize the cluster lock LUN:

       ucd:/> cmdisklock reset /dev/dsk/c0t1d2
       WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label.  Until this situation is corrected, a single failure could cause all nodes
       in the cluster to crash.
       After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset /dev/dsk/c0t1d2' to repair
       /dev/dsk/c0t1d2 is inaccessible
       Resetting cluster lock device /dev/dsk/c0t1d2
       Cluster lock reset completed
       /dev/dsk/c0t1d2 is accessible
       cleared

       After the lock is restored, a message like the following appears in syslog:

       Mar 15 12:23:11 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is accessible

WARNINGS

       CAUTION
       For cluster lock LUN, reset is a potentially destructive operation.  While cmdisklock checks for known volume manager and file  system  use
       (overridden  by	-f),  it does not validate that the device to be reset is actually used by any cluster.  If -f is used on the wrong device
       file, loss of data may result.

       CAUTION
       Care should be taken when doing a reset when the cluster is active as there is a remote possibility that the cluster will  partition  right
       when this command is run and both nodes could end up thinking they have successfully acquired the lock.	To avoid this situation, make sure
       cmcld has logged a message in syslog on all running nodes saying the device is inaccessble, before performing a reset.	Note  that  it	is
       safe to run cmdisklock when the cluster is down.

RETURN VALUE

       cmdisklock returns the following values:

	      0    Successful completion.
	      1    The disk is inaccessible or is not recognized as a cluster lock.

AUTHOR

       cmdisklock was developed by HP.

SEE ALSO

       cmapplyconf(1m), cmviewcl(1m), vgcfgbackup(1m), vgcfgrestore(1m)

						      Requires Optional Serviceguard Software					    cmdisklock(1m)

Red Hat