Operating System - Linux
1830186 Members
3469 Online
109999 Solutions
New Discussion

Urgent help - config RHEL(Linux) for EVA5000

 
yyghp
Super Advisor

Urgent help - config RHEL(Linux) for EVA5000

I have presented 2 LUNs on 2 EVA5000 to serverA, and I have installed QLogic driver and utility on that server.
I can see 4 Drives with Hardware Brower ( GUI ): /dev/sdb, /dev/sdc, /dev/sde, /dev/sdh, but I can't use /opt/hp/hp_fibreutils/lssd to show them, also, I can't use /opt/hp/hp_fibreutils/scsi_info /dev/sdb to show its related LUN, I can only see:
# scsi_info /dev/sdb
SCSI_ID="0,1,1"
MODEL="COMPAQ HSV110 (C)COMPAQ"
FW_REV="3020"

Why? and how can I know which /dev/sdX maps to which LUN ?
Thanks !
3 REPLIES 3
Ivan Ferreira
Honored Contributor

Re: Urgent help - config RHEL(Linux) for EVA5000

I think you can unpresent all the virtual disk, present them one by one and run fdisk and mkfs, and install a label (maybe like the WWID or the VDISK name). If the VDISK have different sizes, the size in fdisk may help you to determine the VDISK that correspond with the special file.

Remember that even when you recognize the special file -> VDISK relationship, you will never know where the data actually is because the EVA distribute the data across all disks.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Eric van Dijken
Trusted Contributor

Re: Urgent help - config RHEL(Linux) for EVA5000

On Tru64 we have a list like:

91: /dev/disk/dsk7c COMPAQ HSV110 (C)COMPAQ IDENTIFIER=2042

This list shows the devicename and the WWID and it would be very nice to have a util that displays the same information on Linux.

But like the original author, i havent found a tool/sollution yet.
Watch, Think and Tinker.
Uwe Zessin
Honored Contributor

Re: Urgent help - config RHEL(Linux) for EVA5000

Sorry, but the list you show does not include the LUN WWID - that is a 128-bit value starting with 6. Identifier=2042 is an entry in a vendor-specific code page. This value is only understood by OpenVMS, Tru64 Unix and the AlphaServer + Integrity server console subsystems.
.