[dm-devel] [PATCH 4/4] [libmultipath] Update hardware table forHPHSV200

[Reilly, Stephen (MRO)]

-----Original Message-----
From: Hannes Reinecke [mailto:hare at suse.de] 
Sent: Wednesday, November 15, 2006 7:50 AM
To: Reilly, Stephen (MRO)
Cc: device-mapper development
Subject: Re: [dm-devel] [PATCH 4/4] [libmultipath] Update hardware table forHPHSV200

Reilly, Stephen (MRO) wrote:
[ Quoting appears to be a lost art ... ]
> 
> Hannes Reinecke wrote:
 >> Reilly, Stephen (MRO) wrote:
>>> The product name does change if the firmware uses 'START_STOP_UNIT' or
>>> ALUA... so why are we adding the revision?
>>
>> Ah, that's news to me.
>> How does the product name change?
 >
> The firmware will change the name
 >
Oh, that's nice.

>> My contacts at HP Boeblingen said that the revision number indicated the 
>> behaviour.
>> What are the names of the fw using START_STOP_UNIT?
> HSV100 and HSV110 EVA3000/5000
EVA is the name of the machine; HSV is the SCSI model name, right?
[Reilly, Stephen (MRO)] Correct, presented both for reference

>> And what are those for using ALUA?
> HSV101, HSV111, HSV200 and HSV210 EVA 3000/5000  EVA4000/6000/8000
> 
What about the old MSA ones? Is there a firmware upgrade available?
If so, will the name change there, too?

			 Vendor Id: 		Product Id: 
MSA1500 A-A -      "HP      "		      "MSA VOLUME      "

MSA1000 A-P - 	 "COMPAQ  "			"MSA1000 VOLUME  "
MSA1500 A-P -      "COMPAQ  "			"MSA1000 VOLUME  "


>> And irrespective of this I think matching by revision is still a valid 
>> addition to the hardware table mechanism.
> However I would not use it determine the START_STOP_UNIT or ALUA implementation
> 
I was under the impression that the name would stay the same. If that's 
not the case then of course we should match onto the name.

Please check the attached patch if it updates the hwtables correctly.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare at suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de