RE: LUN ID

  • From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
  • To: "Shanmugam, Satheesh B" <satheesh.b.shanmugam@xxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>, "grzegorzof@xxxxxxxxxx" <grzegorzof@xxxxxxxxxx>
  • Date: Wed, 21 Nov 2012 13:32:06 +0100

Hmm, I don't think lun id has to be unique when the lun is coming from 2 
different SAN boxes.
WWID might be a better identifier, but you will need to match it with the list 
of WWID's from the san boxes before you can tell where it is coming from.
If these are 2 different type of SAN boxes, you can look into the 
/sys/block/<sd name>/device/vendor file.
Otherwise you have different tools from different vendors, to aid you with 
identifying from which box a lun originates.
For NetApp you have sanlun , which lists you the actual name of the san on 
which a lun resides.

Perhaps you can find this information also directly in the /sys/ directories, 
but I have never been able to find where exactly.


Regards,

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer


-----Original Message-----
From: Shanmugam, Satheesh B [mailto:satheesh.b.shanmugam@xxxxxxxxxxxx] 
Sent: woensdag 21 november 2012 12:44
To: oracle-l@xxxxxxxxxxxxx; grzegorzof@xxxxxxxxxx; D'Hooge Freek
Subject: RE: LUN ID

Thanks for response. Let me try to explain what the issue here. 
We have ASM disk group created with LUNS from different SAN frame. Now as per 
our standard the diskgroup should have LUNs from same SAN frame. I was thinking 
getting LUN id will give me some clue. Anyone has better solution than this?

Regards,
Satheesh Shanmugam

-----Original Message-----
From: GG [mailto:grzegorzof@xxxxxxxxxx]
Sent: Tuesday, November 20, 2012 9:07 PM
To: Shanmugam, Satheesh B
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: LUN ID

W dniu 2012-11-20 16:16, Shanmugam, Satheesh B pisze:
> We have created asm disk using asmlib and assigned to the diskgroups. This 
> was done a while back. Is there a way now to get LUN ID of these disks? We 
> are in linux running 11.2.0.3 grid.
> Regards,
> Satheesh Shanmugam

Hi,

Troubleshooting a multi-node ASMLib installation [ID 811457.1] On existing or 
freshly labelled systems, you can identify and verify the LUNs, scsi IDs and 
ASM volume labelling on each cluster node with the following command:

|#*blkid|grep sd.*oracleasm|while read a b;do echo -n $a$b" 
scsi_id=";(echo $a|tr -d [:digit:]|tr -d [:]|cut -d"/" -f3|xargs -i scsi_id -g 
-s /block/{})done;*|

above is one long line .

Output :
|root@rmvsx1:~ # blkid|grep sd.*oracleasm|while read a b;do echo -n
$a$b" scsi_id=";(echo $a|tr -d [:digit:]|tr -d [:]|cut -d"/" -f3|xargs -i 
scsi_id -g -s /block/{})done;|
|/dev/sda1:LABEL="DATA0" TYPE="oracleasm" 
scsi_id=14945540000000000646174612d3000000000000000000000|
|/dev/sdb1:LABEL="DATA0" TYPE="oracleasm" 
scsi_id=14945540000000000646174612d3000000000000000000000

|Regards
GregG


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates.

This transmission may contain information that is privileged, confidential, 
legally privileged, and/or exempt from disclosure under applicable law. If you 
are not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution, or use of the information contained herein (including 
any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments 
are believed to be free of any virus or other defect that might affect any 
computer system into which it is received and opened, it is the responsibility 
of the recipient to ensure that it is virus free and no responsibility is 
accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as 
applicable, for any loss or damage arising in any way from its use. If you 
received this transmission in error, please immediately contact the sender and 
destroy the material in its entirety, whether in electronic or hard copy 
format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures 
relating to European legal entities.
--
//www.freelists.org/webpage/oracle-l


Other related posts: