[ofa-general] Re: [PATCH v2] infiniband-diags/scripts: Add 'ibcheckspeed' and 'ibcheckportspeed' to scripts

[Keshetti Mahesh]

My badness. I have not used 'iblinkinfo' before.
So, I guess there is no need for the above script. Apart from that, I feel
there should be a program/script which will first scan the fabric to find the
maximum common supported width/speed and then report the warning messages
of the links/ports which are configured with active width/speed less
than the found
value. Is there any tool already exists which does the same ?

-
Keshetti Mahesh

On Thu, Sep 10, 2009 at 9:32 PM, Ira Weiny <weiny2 at llnl.gov> wrote:
> Also, iblinkinfo will report links which it finds capable of either faster or wider operation.  iblinkinfo checks both ends of the link as Hal mentions.  It reports this with output like.
>
> Switch 0x0005ad0000092106 Cisco Switch SFS7000D:
> ...
>           7    8[  ] ==( 4X 2.5 Gbps Active/  LinkUp)==>       8   12[  ] "MT47396 Infiniscale-III Mellanox Technologies" ( Could be 5.0 Gbps)
> ...
>
> Also the portstatus console command in OpenSM will report links which are running at "reduced speed or width".  Although this does not check the remote port.
>
> OpenSM $ help portstatus
> portstatus [ca|switch|router]
> summarize port status
>   [ca|switch|router] -- limit the results to the node type specified
> OpenSM $ portstatus
> "ALL" port status:
>   115 port(s) scanned on 9 nodes in 26 us
>   85 down
>   30 active
>   32 at 4X
>   22 at 2.5 Gbps
>   8 at 5.0 Gbps
>   2 at 10.0 Gbps
>
> Possible issues:
>   2 disabled
>      0x0008f10400411b18 5 (ISR9024D Voltaire)
>      0x0005ad0000092106 13 (Cisco Switch SFS7000D)
>   6 with reduced speed
>      0x0008f10500200220 33 (Voltaire 4036 - 36 QDR ports switch)
>      0x0008f10500200220 19 (Voltaire 4036 - 36 QDR ports switch)
>      0x0005ad0000092106 21 (Cisco Switch SFS7000D)
>      0x0005ad0000092106 20 (Cisco Switch SFS7000D)
>      0x0005ad0000092106 9 (Cisco Switch SFS7000D)
>      0x0005ad0000092106 8 (Cisco Switch SFS7000D)
>
>
> Ira
>
> On Thu, 10 Sep 2009 09:23:35 -0400
> Hal Rosenstock <hal.rosenstock at gmail.com> wrote:
>
>> On Thu, Sep 10, 2009 at 9:02 AM, Keshetti Mahesh
>> <keshetti.mahesh at gmail.com>wrote:
>>
>> > Added 'ibcheckspeed' and 'ibcheckportspeed': Similar to
>> > 'ibcheckwidth/ibcheckportwidth' in functionality and implementation.
>> > Reports error/warning messages if the LinkSpeedActive is configured as
>> > 2.5 Gbps when the LinkSpeedSupported is more than 2.5 Gbps.
>> >
>>
>> ibportstate checks for more than this in terms of speed (and width)
>> anomalies.
>>
>> Would it be better for these scripts to use that tool now ? Alternatively,
>> the additional speed/width anomaly checks could be implemented in these
>> scripts but it does involve checking the peer port so there's a little more
>> to it.
>>
>> -- Hal
>>
>>
>> >
>> > Signed-off-by: Keshetti Mahesh < keshetti.mahesh at gmail.com>
>> > ---
>> >  infiniband-diags/scripts/ibcheckportspeed.in |  146
>> > ++++++++++++++++++++++++++
>> >  infiniband-diags/scripts/ibcheckportwidth.in |    2 +-
>> >  infiniband-diags/scripts/ibcheckspeed.in     |  135
>> > ++++++++++++++++++++++++
>> >  3 files changed, 282 insertions(+), 1 deletions(-)
>> >  create mode 100644 infiniband-diags/scripts/ibcheckportspeed.in
>> >  create mode 100644 infiniband-diags/scripts/ibcheckspeed.in
>> >
>> <snip...>
>>
>
>
> --
> Ira Weiny
> Math Programmer/Computer Scientist
> Lawrence Livermore National Lab
> 925-423-8008
> weiny2 at llnl.gov
>