How get more LUN info

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat How get more LUN info
# 1  
Old 10-26-2006
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
Login or Register to Ask a Question

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 (1 Reply)
Discussion started by: iformats
1 Replies

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"? (1 Reply)
Discussion started by: malayo
1 Replies

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 Replies)
Discussion started by: manoj.solaris
4 Replies

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:... (8 Replies)
Discussion started by: Shirishlnx
8 Replies

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. (2 Replies)
Discussion started by: snjksh
2 Replies

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 ... (10 Replies)
Discussion started by: letters
10 Replies

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 (4 Replies)
Discussion started by: uuontario
4 Replies

8. Solaris

LUN not ready

hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies

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... (3 Replies)
Discussion started by: jameszak
3 Replies

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... (0 Replies)
Discussion started by: s4g3
0 Replies
Login or Register to Ask a Question
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)