Re: [aperi-dev] IDVT: getHBAPortWWN() doesn't work on 2.6 kernel withrec

["Robert Wipfel" <rawipfel@xxxxxxxxxx>]

>>> On Sun, Dec 2, 2007 at  4:46 PM, in message
<OFA187D150.579B4ABD-ONC22573A5.00823367-C22573A5.0082B65A@xxxxxxxxxx>, Simona
Constantin <simona_constantin@xxxxxxxxxx> wrote: 
> Hello Robert,

Hi Simona,

> On Red Hat Enterprise Linux AS release 4 (2.6.9- 55.ELsmp), QLogic still 
> creates the entries in /proc/scsi/qla2xxx/# .  So there should be a check 

Good point, I tried to follow your convention FromSys() versus FromProc(),
and can make that change. The FibreChannel driver vendors are moving stuff out
of /proc and into /sys, especially to add e.g. N_Port_ID Virtualization support
(multiple virtual FibreChannel ports per adapter) is only being done via /sys, soon
this will be the only way it works, and I imagine that those drivers on RHEL5 are
working the same way. I will make that change and re-submit...

Is anyone on the Aperi project testing with RHEL? does the topology viewer
work there?

> and if the getHBAPortWWNFromSys could not retrieve the ctlr.ctlrHBAPortWWN 
> then the getHBAPortWWNFromProc should be invoked.
> 
> I don't know to answer  your questions: 
> 1. what is missing from the model and why the computers and switches are 
> not linked in topology viewer ?
> 2. from what file ( node_name or port_name ) should the WWN be read ?

Anyone?

Thanks,
Robert

> ---
> Simona Constantin
> 
> "Robert Wipfel" <rawipfel@xxxxxxxxxx> 
> Sent by: aperi- dev- bounces@xxxxxxxxxxx
> 12/02/2007 06:35 PM
> Please respond to
> Aperi Development <aperi- dev@xxxxxxxxxxx>
> 
> 
> To
> "Aperi Development" <aperi- dev@xxxxxxxxxxx>
> cc
> 
> Subject
> Re: [aperi- dev] IDVT: getHBAPortWWN() doesn't work on 2.6       kernel 
> withrecent Qlogic driver
> 
> 
> 
> 
> 
> 
>>>> On Thu, Nov 29, 2007 at 11:59 AM, in message
> <OF0B47C0B3.DB7F1337- ON882573A2.00678C6E- 882573A2.00685D28@xxxxxxxxxx>, 
> Tom
> Guinane <guinane@xxxxxxxxxx> wrote: 
>> If Simona can take a look at it during her Monday (in Europe) and 
> provide 
>> a response, we could discuss this at our Monday development call and 
> make 
>> a decision on whether to include in R0.4. 
> 
> Thanks Tom,
> 
> I put some more info in the IDVT test report posted to aperi- dev
> separately. While the fix below will store a fibre channel ID into the
> Aperi model, and the topology viewer will then show that there
> is an FCPort for the corresponding Computer, I am having trouble
> figuring out how to fix things so that the Fabric viewer will also show
> a link from the Computer to its Switch port. Please if anyone can
> comment on how this is supposed to work, that will be very helpful,
> what is supposed to be stored in this field of the model? and what in
> the model is used to visualize the link from Computer to switch?
> 
>> -     private void getHBAPortWWN(StringBuffer buf,  Controller ctlr)
>> +   private void getHBAPortWWNFromSys(String host, Controller ctlr)
>> +   {
>> +   /*
>> +    * Open up fc_host node_name file and parse Port Number.
>> +    */
>> +      String myFile = "/sys/class/fc_host/" + host + "/node_name";
> 
> I guess this should be port_name (probably not node_name) ? 
> 
>> +                                ctlr.ctlrHBAPortWWN = wwn;
>> +                                ctlr.ctlrType = Controller.FCAL;
> 
> This at least stores something into ctlrHBAPortWWN (I've tried both
> port_name and node_name from /sys/class/fc_host/host#/) but so far
> I haven't been able to get the Topology viewer to diagram a link from
> computer to its switch port
> 
> Fwiw, with no code changes at all, using the Interim build, there is
> nothing stored for each Computer's FCPort, and the topology viewer will
> show links from switch ports to "Unknown" computers...
> 
> Hth,
> Robert
> 
> _______________________________________________
> aperi- dev mailing list
> aperi- dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aperi- dev