> -----Original Message-----
> From: Hal Rosenstock [mailto:h...@dev.mellanox.co.il]
> Sent: Wednesday, December 09, 2015 8:46 AM
> >>> To solve the problem, this patch introduces the following priority
> >>> to interpret default pkey:
> >>> 1. Find the first non-management full-member pkey; 2. If it fails,
> >>> find pkey 0xffff; 3. If pkey 0xffff is not available, use the first
> >>> pkey.
> >>> This approach will work in both securely and insecurely partitions
> >>> fabrics.
> >>
> >> Shouldn't the pkey to be used for such interACM communication be
> >> configured ?
> > Yes. The purpose of this patch is only to make a secure system work out of
> box (default configuration). When a specific pkey is given in the
> ibacm_addr.cfg file, there will be no need to interpret the "default" pkey.
> >
> >> First full member pkey is non-deterministic. Isn't it the case that
> >> it may not include proper set of ACMs to communicate with ?
> >
> > This is only for the default configuration, where a reasonable
> > assumption is that members of an intended partition (group of ports) will
> all have the same full-member pkey.
>
> Yes, but it may not be first (lowest index) pkey in table of different ports.
>
This is the best effort and it should work for most common configurations, but
may not work for more complicated cases.
Any other suggestions?
> > To make it really work, one needs to edit ibacm_addr.cfg.
>
> It may work without config depending on a number of factors but can cause
> issues to be debugged.
>
> Only sure way is config :-(
Exactly.
Kaike
N�����r��y����b�X��ǧv�^�){.n�+����{��ٚ�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�m��������zZ+�����ݢj"��!�i
