System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

 
Michael Mtweve
Occasional Advisor

HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

I am trying to add storage disk in redhat 5.7 from eva8100 and iscsi P2000G3 without success.

 

The display in lsscsi comand is as shwon below:

 

[root@svlhq30 ~]# lsscsi
[0:0:0:0] cd/dvd hp DVD D DS8D3SH HHE7 /dev/sr0
[3:0:0:0] storage HP HSV210 6200 -
[3:0:1:0] storage HP HSV210 6200 -
[3:0:2:0] storage HP HSV210 6200 -
[3:0:3:0] storage HP HSV210 6200 -
[6:0:0:0] storage HP P2000 G3 iSCSI T230 -

 

How can proceed in creating logical volume from this point.

 

5 REPLIES
Matti_Kurkela
Honored Contributor

Re: HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

You're seeing the storage controller devices (marked "storage") only, not the disk LUNs (marked "disk").

 

Have you rebooted the RedHat server or rescanned the FibreChannel adapters?

 

To rescan the adapters, you need the /usr/bin/rescan_scsi_bus.sh script. It comes with the sg3_utils RPM: if your system is registered to the RedHat Network, simply run "yum install sg3_utils" to install it.

 

If you have already done that, something is probably wrong in the storage system configuration. You may have created new LUNs, but have you presented them to the server (i.e. listed the FibreChannel WWNs that are allowed to access the LUns in the storage system configuration)?

 

Likewise, with iSCSI storage it is typically not enough to define a new LUN: you must also configure which servers are allowed to use it.

 

This RedHat document should be very helpful in FC/iSCSI configuration issues:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/index.html

 

Pay special attention to chapter 9 ("Scanning Storage Interconnects") for FibreChannel, and chapters 10-13 for iSCSI.

 

Once your disks/LUNs are visible as regular /dev/sd* disk devices, you can use them just like regular local disks. If you see more new disk devices than you expected to see, you might need to install multipathing support first.

 

RHEL 5 native dm-multipath documentation:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/DM_Multipath/index.html

 

LVM documentation:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Logical_Volume_Manager_Administration/index.html

 

MK
Michael Mtweve
Occasional Advisor

Re: HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

Hello Matti;

 

Thank you for your response  I have scanned the systems and here is the out put:

[root@svlhq30 ~]# rescan-scsi-bus.sh
Host adapter 0 (ata_piix) found.
Host adapter 1 (ata_piix) found.
Host adapter 2 (lpfc) found.
Host adapter 3 (lpfc) found.
Host adapter 4 (bnx2i) found.
Host adapter 5 (bnx2i) found.
Host adapter 6 (iscsi_tcp) found.
Scanning SCSI subsystem for new devices
Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: hp Model: DVD D DS8D3SH Rev: HHE7
Type: CD-ROM ANSI SCSI revision: 05
Scanning host 1 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 2 for all SCSI target IDs, all LUNs
Scanning host 3 for all SCSI target IDs, all LUNs
Scanning for device 3 0 0 0 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: HSV210 Rev: 6200
Type: RAID ANSI SCSI revision: 05
Scanning for device 3 0 1 0 ...
OLD: Host: scsi3 Channel: 00 Id: 01 Lun: 00
Vendor: HP Model: HSV210 Rev: 6200
Type: RAID ANSI SCSI revision: 05
Scanning for device 3 0 2 0 ...
OLD: Host: scsi3 Channel: 00 Id: 02 Lun: 00
Vendor: HP Model: HSV210 Rev: 6200
Type: RAID ANSI SCSI revision: 05
Scanning for device 3 0 3 0 ...
OLD: Host: scsi3 Channel: 00 Id: 03 Lun: 00
Vendor: HP Model: HSV210 Rev: 6200
Type: RAID ANSI SCSI revision: 05
Scanning host 4 for all SCSI target IDs, all LUNs
Scanning host 5 for all SCSI target IDs, all LUNs
Scanning host 6 for all SCSI target IDs, all LUNs
Scanning for device 6 0 0 0 ...
OLD: Host: scsi6 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: P2000 G3 iSCSI Rev: T230
Type: RAID ANSI SCSI revision: 05
0 new device(s) found.
0 device(s) removed.

 

Attached herewith is the configuration for P2000G3 iscsi storage in which the server has been given explicity read/write access. 

 

 

Howeveer the Once your disks/LUNs are not visible as regular /dev/sd* disk devices.

 

Regards;

 

Michael Mtweve

Matti_Kurkela
Honored Contributor

Re: HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

I'm not very familiar with EVA configuration, but I think this indicates the presentation of the vdisk from the EVA has in fact not been successful. If I recall correctly, you should double-check the WWNs used in identifying the server: you should be able to see the WWNs with:

cat /sys/class/fc_host/host2/port_name
cat /sys/class/fc_host/host3/port_name

 These WWNs should be listed in the EVA configuration (either directly, or using an aliasing mechanism that allows you to assign the WWNs as belonging to a server named "svlhq30" and then use names in LUN presentation.

 

With FibreChannel, there are several ways to configure disk presentation. In EVA, I think these were mostly encapsulated in a "host type" setting. It must be set correctly, or the disk presentation may not work.

 

 

Regarding the iSCSI storage, you need to use the iscsiadm command to connect to bind to the storage first.

 

Please run:

iscsiadm -m iface

 What is the output?

 

The storage is configured to present the disk to iSCSI initiator named "svhq30.bot". From your command prompt, I see your server hostname is actually "svlhq30" (i.e. SVLHQ30 for emphasis). If you haven't overridden the initiator name, the default name should be the same as the server hostname. As far as the storage is concerned, the iSCSI initiator "svlhq30" is not the same as "svhq30.bot".

 

The above iscsiadm command should tell us what is the actual iSCSI initiator name your system is currently using. The name in the storage access configuration must match the initiator name configured on the server, otherwise the storage won't allow access.

 

After the names are confirmed to match, the next step is to run "iscsiadm -m discovery" with the appropriate parameters. I do not have enough information on your iSCSI network configuration, so I cannot determine the parameters for you.

 

This page should be helpful:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/scanningnewdevs-iscsi-offload.html

MK
Michael Mtweve
Occasional Advisor

Re: HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

Hello Matti;

 

[root@svlhq30 fc_host]# hostname
svlhq30.bot
[root@svlhq30 fc_host]# iscsiadm -m iface
iscsiadm: Could not look up host's ifaces via scsi bus.
iscsiadm: Could not look up host's ifaces via scsi bus.
default tcp,<empty>,<empty>,<empty>,<empty>
iser iser,<empty>,<empty>,<empty>,<empty>
bnx2i.3c:d9:2b:fb:e6:1f bnx2i,3c:d9:2b:fb:e6:1f,<empty>,<empty>,<empty>
bnx2i.3c:d9:2b:fb:e6:1d bnx2i,3c:d9:2b:fb:e6:1d,<empty>,<empty>,<empty>

 

[root@svlhq30 fc_host]# cat /sys/class/fc_host/host2/port_name
0x10000000c9d0e01d
[root@svlhq30 fc_host]# cat /sys/class/fc_host/host3/port_name
0x10000000c9d0e07e

 

I have added theserver (initiator here is the iqn)

[root@svlhq30 class]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:1c1e8e9eced4

 

the same has been used to configure it the target (storage unit HP p2000 g3)

 

Attached is the screen shot of the configuration 

 

regards;

 

Michael Mtweve

 

 

 

Matti_Kurkela
Honored Contributor

Re: HOW TO ADD DISK FROM EVA8100 TO REDHAT 5

Your screenshot indicates that the "Profile" setting in the storage configuration for svhq30.bot is set to "HP-UX". Are you sure that's correct? HP-UX does not use the same SCSI addressing mode as Windows/Linux. If the difference exists in iSCSI too, this very well might be the cause of your problem.

 

> [root@svlhq30 fc_host]# cat /sys/class/fc_host/host2/port_name
> 0x10000000c9d0e01d
> [root@svlhq30 fc_host]# cat /sys/class/fc_host/host3/port_name
> 0x10000000c9d0e07e

 

Tell these to your EVA8100 administrator: they are the FibreChannel Port WWNs of your FC interfaces. If the storage administrator has put the wrong WWNs in the configuration, your system won't see any FibreChannel disks/LUNs.

If there is a FibreChannel fabric switch in your FC environment, the WWNs might be required for two purposes:

  1. LUN masking in the EVA itself
  2. fabric zoning configuration in the fabric switch.
MK