[openib-general] [opensm] the default behavior of the openSM causes problems (configure the PKey table)

[Dotan Barak]

Thanks for the quick response.

On Monday 14 August 2006 15:17, Sasha Khapyorsky wrote:
> Hi Dotan,
> 
> On 14:36 Mon 14 Aug     , Dotan Barak wrote:
> > Hi.
> > 
> > I noticed that the behavior of the openSM was changed in the latest driver:
> > 
> > in the past, every HCA was configured (by the FW) with 0xffff in the first entry.
> > today, the PKey table is being configured by the openSM: the first entry 
> > is being set to 0x7fff (except for the host that the SM is being executed from)
> 
> This is OpenSM default behavior in the case where partition policy file
> exists (/etc/osm-partitions.conf is default name), even if it is empty.

You are right, this file was exist in the host with the following content:

Default=0x7fff : ALL, SELF=full ;
YetAnotherOne = 0x300 : ALL, SELF=full ;
partition1 = 0x1 : 0x0002c9020020b1c9=full;



> 
> When the partition policy file does not exist default 0xffff pkey value
> (full membership) should be inserted for all end-ports.
> 
> I am not able to reproduce the reported behavior with my setup. If you
> are please describe your scenario. Thanks.
I have 2 machines connected b2b (without any switch in the middle) connected 
using one cable from port 1 to port 1.

I executed the SM from one machine, and in the other machine "perfquery" i got the failure.


Why doesn't the SM print that this file was found?
this way, users can know that this file was found in their machine and the SM is using those rules
(instead of the default rules, as you described)

Thanks
Dotan