Command View EVA: cannot setup a linux Host

[REMARS]

Hi,

Under Command view 4.1 EVA (windows 2003 server) , I can't create a linux host because Linux is not in the OS list.
Maybe I can choose 'Unknown OS' but I don't know the hex string to put.

Hardware EVA 3000 /HSV 100.

Please Help me

Stephane

Best regards

[Peter Mattei]

Hi Stephane
For smooth system operation, set the host type for Linux to Sun Solaris except in a LifeKeeper Cluster environment.
Linux and Solaris have the same behaviour.

You will find the information in one of the Linux manuals on
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&docIndexId=3124&locale=en_US&prodTypeId=12169&prodSeriesId=315127


Cheers
Peter

[Uwe Zessin]

On the EVA3000 you usually use "Sun Solaris" for Linux hosts, except for some Cluster solutions which require the "Custom" setting with a bitmask.

[REMARS]

Thank you for your answer,

I'm trying to validate the multipath with builtin qlogic driver in SuSE linux SLES 9 SP2 http://portal.suse.com/sdb/en/2005/04/sles_multipathing.html


My server has 2 qla2300 cards, and my EVA 3000, 2 HSV 100. My lun is presented to my server (as host Sun Solaris :) ). 2 paths are working and two paths are faulty :


red (3600508b400104cb200004000004d0000)
[size=16 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [enabled]
\_ 0:0:0:1 sda 8:0 [failed]
\_ 1:0:1:1 sdg 8:96 [failed]
\_ round-robin 0 [active][best]
\_ 0:0:1:1 sdc 8:32 [active]
\_ 1:0:0:1 sde 8:64 [active]

Preferred path/mode choosen : no preference

Is it a normal behaviour ?

Thanks a lot

cheers

[Uwe Zessin · Accepted solution]

For Linux, you need "Path A failover" or "Path B failover".

Whether it is correct that two out of four paths appear "faulty" I don't know as I haven't worked with this software combination, yet.

A possible reason is that the EVA3000 is not a true "active/active" storage array. A single virtual disk is maintained by one controller at a time and you only can do I/O through this controller's host ports. The other controller still presents the virtual disk so that the failover software on the host knows about these 'standby' paths it can fail over to, but if you inquire these LUNs you will get a "not ready" response. The driver should not declare such a path "faulty" I'd say.

I would first change the path preferrence, reboot the server and check again.

[REMARS]

You are right

According to the documentation. EVA 3000 is not active/active (contrary to EVA 4000).

The faulty paths are pointing to pseudo LUN.

So, I must setup the path mode as Path A Failover Only or Path B Failover Only.

Everything seems to be working ...


Thanks a lot

Stephane

[Uwe Zessin]

No, those are not "pseudo LUNs". Those are real LUNs, presented by the non-owning controller, which report "not ready".

If you send a SCSI "start unit" command to such a LUN, you implicitly tell the EVA to do a failover for this virtual disk.

[REMARS]

Thanks , now things are clear in my head

Cheers


Stephane

[REMARS]

closed !