<br><br>
<div class="gmail_quote">On Mon, Sep 14, 2009 at 2:20 AM, Keshetti Mahesh <span dir="ltr"><<a href="mailto:keshetti.mahesh@gmail.com">keshetti.mahesh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I have a small question. If there are all 5 Gbps (maximum supported<br>speed) ports<br>except one with 10 Gbps in a subnet then what is the expected behavior<br>
of OpenSM<br>while setting active link speed ? </blockquote>
<div> </div>
<div>It depends on the peer port and the link between them.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Does OpenSM force the port with 10<br>Gbps to operate<br>at 5 Gbps or not ?<br></blockquote>
<div> </div>
<div>SM (including OpenSM) sets PortInfo enabled components based on peer ports' supported components and link negotiation determines the active components.</div>
<div> </div>
<div>So in the case where one port supports 10 Gbps speed and it's peer port only supports 5, the SM sets LinkSpeedEnabled components on the peer ports to 5 Gbps (encoded as 3). In the case where the peer port supports 10 Gbps, it is set to 10 Gbps (encoded as 5 or 7 depending on what is supported). The link then negotiates to one of the enabled speeds and sets LinkSpeedActive accoridingly.</div>
<div> </div>
<div>-- Hal</div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><font color="#888888"><br>--<br></font>
<div class="im">Keshetti Mahesh<br><br>On Thu, Sep 10, 2009 at 9:32 PM, Ira Weiny <<a href="mailto:weiny2@llnl.gov">weiny2@llnl.gov</a>> wrote:<br></div>
<div>
<div></div>
<div class="h5">> 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.<br>><br>
> Switch 0x0005ad0000092106 Cisco Switch SFS7000D:<br>> ...<br>> 7 8[ ] ==( 4X 2.5 Gbps Active/ LinkUp)==> 8 12[ ] "MT47396 Infiniscale-III Mellanox Technologies" ( Could be 5.0 Gbps)<br>
> ...<br>><br>> 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.<br>><br>> OpenSM $ help portstatus<br>
> portstatus [ca|switch|router]<br>> summarize port status<br>> [ca|switch|router] -- limit the results to the node type specified<br>> OpenSM $ portstatus<br>> "ALL" port status:<br>> 115 port(s) scanned on 9 nodes in 26 us<br>
> 85 down<br>> 30 active<br>> 32 at 4X<br>> 22 at 2.5 Gbps<br>> 8 at 5.0 Gbps<br>> 2 at 10.0 Gbps<br>><br>> Possible issues:<br>> 2 disabled<br>> 0x0008f10400411b18 5 (ISR9024D Voltaire)<br>
> 0x0005ad0000092106 13 (Cisco Switch SFS7000D)<br>> 6 with reduced speed<br>> 0x0008f10500200220 33 (Voltaire 4036 - 36 QDR ports switch)<br>> 0x0008f10500200220 19 (Voltaire 4036 - 36 QDR ports switch)<br>
> 0x0005ad0000092106 21 (Cisco Switch SFS7000D)<br>> 0x0005ad0000092106 20 (Cisco Switch SFS7000D)<br>> 0x0005ad0000092106 9 (Cisco Switch SFS7000D)<br>> 0x0005ad0000092106 8 (Cisco Switch SFS7000D)<br>
><br>><br>> Ira<br>><br>> On Thu, 10 Sep 2009 09:23:35 -0400<br>> Hal Rosenstock <<a href="mailto:hal.rosenstock@gmail.com">hal.rosenstock@gmail.com</a>> wrote:<br>><br>>> On Thu, Sep 10, 2009 at 9:02 AM, Keshetti Mahesh<br>
>> <<a href="mailto:keshetti.mahesh@gmail.com">keshetti.mahesh@gmail.com</a>>wrote:<br>>><br>>> > Added 'ibcheckspeed' and 'ibcheckportspeed': Similar to<br>>> > 'ibcheckwidth/ibcheckportwidth' in functionality and implementation.<br>
>> > Reports error/warning messages if the LinkSpeedActive is configured as<br>>> > 2.5 Gbps when the LinkSpeedSupported is more than 2.5 Gbps.<br>>> ><br>>><br>>> ibportstate checks for more than this in terms of speed (and width)<br>
>> anomalies.<br>>><br>>> Would it be better for these scripts to use that tool now ? Alternatively,<br>>> the additional speed/width anomaly checks could be implemented in these<br>>> scripts but it does involve checking the peer port so there's a little more<br>
>> to it.<br>>><br>>> -- Hal<br>>><br>>><br>>> ><br>>> > Signed-off-by: Keshetti Mahesh < <a href="mailto:keshetti.mahesh@gmail.com">keshetti.mahesh@gmail.com</a>><br>
>> > ---<br>>> > infiniband-diags/scripts/<a href="http://ibcheckportspeed.in/" target="_blank">ibcheckportspeed.in</a> | 146<br>>> > ++++++++++++++++++++++++++<br>>> > infiniband-diags/scripts/<a href="http://ibcheckportwidth.in/" target="_blank">ibcheckportwidth.in</a> | 2 +-<br>
>> > infiniband-diags/scripts/<a href="http://ibcheckspeed.in/" target="_blank">ibcheckspeed.in</a> | 135<br>>> > ++++++++++++++++++++++++<br>>> > 3 files changed, 282 insertions(+), 1 deletions(-)<br>
>> > create mode 100644 infiniband-diags/scripts/<a href="http://ibcheckportspeed.in/" target="_blank">ibcheckportspeed.in</a><br>>> > create mode 100644 infiniband-diags/scripts/<a href="http://ibcheckspeed.in/" target="_blank">ibcheckspeed.in</a><br>
>> ><br>>> <snip...><br>>><br>><br>><br>> --<br>> Ira Weiny<br>> Math Programmer/Computer Scientist<br>> Lawrence Livermore National Lab<br>> 925-423-8008<br>> <a href="mailto:weiny2@llnl.gov">weiny2@llnl.gov</a><br>
><br></div></div></blockquote></div><br>