[openib-general] SM assigned GID addresses

[Hal Rosenstock]

On Wed, 2007-02-14 at 11:56, Batwara, Ashish wrote:
> Thanks for your reply.
> So do you mean to say that current GUIDCap is always configured by SM to
> 1 for all the HCAs, and it is safe to assume that one IB port will have
> only one or multiple IB address but that will have GUID portion common
> in them (Based upon manufacturer's assigned EUI-64 based).

GUIDCap is a RO component in terms of the SM and guaranteed to be at
least 1 for an endport. This comes from the device SMA, not the SM.

-- Hal

> We are trying to define the target functionality for IB for our storage
> arrays, and are trying to explore howmany port addresses that we can get
> from an initiator standpoint.
> How does this IB port GUID maps to SRP initiator ID? Are they same or
> I/O Controller may have its own GUID and can use SM prefix to derive
> initiator port ID in SRP login req?
> 
> Thanks
> Ashish
> 
> -----Original Message-----
> From: Hal Rosenstock [mailto:halr at voltaire.com] 
> Sent: Wednesday, February 14, 2007 10:41 AM
> To: Batwara, Ashish
> Cc: openib-general at openib.org
> Subject: Re: [openib-general] SM assigned GID addresses
> 
> Hi,
> 
> On Wed, 2007-02-14 at 11:12, Batwara, Ashish wrote:
> > Hi,
> > I am referring to Section 4.1.1 of IB Spec which talks about "GID
> Usage
> > AND Properties". Does anyone know whether or not SM uses item # 3
> below
> > for the address assignment and who are all the vendor supports # 3?
> 
> > Can anybody points me to the appropriate driver documentation in this
> area?
> 
> OpenSM supports setting either the default GID prefix or a configured
> GID prefix and GIDs are comprised of this prefix and the endport EUI-64
> (at index 0 of GUIDInfo).
> 
> OpenSM does not currently support configuring GUIDInfo indices above 0.
> I'm also not sure how the stack would deal with this either. Is this a
> requirement for some reason ? If so, can you elaborate/explain ?
> 
> -- Hal
> 
> > Thanks
> > Ashish
> > 
> > 
> > GID USAGE AND PROPERTIES
> > 1) Each endport shall be assigned at least one unicast GID. The first
> > unicast GID assigned shall be created using the manufacturer assigned
> > EUI-64 identifier. This GID is referred to as GID index 0 and is
> > formed by techniques 3(a) and 3(b) described below.
> > 2) The default GID prefix shall be (0xFE80::0). A packet using the
> > default
> > GID prefix and either a manufacturer assigned or SM assigned
> > EUI-64 must always be accepted by an endnode. A packet containing
> > a GRH with a destination GID with this prefix must never be
> > forwarded by a router, i.e. it is restricted to the local subnet.
> > 3) A unicast GID shall be created using one or more of the following
> > mechanisms:
> > a) Concatenation of the default GID prefix with the manufacturer
> > assigned
> > EUI-64 identifier associated with an endport. This GID is
> > referred to as the default GID.
> > b) Concatenation of a subnet manager assigned 64-bit GID prefix
> > and the manufacturer assigned EUI-64 identifier associated with
> > an endport.
> > c) Assignment of a GID by the subnet manager. The subnet manager
> > creates a GID by concatenating the GID prefix (default or assigned)
> > with a set of locally assigned EUI-64 values (at GID index
> > 1 or above). Each endport must be assigned at least one unicast GID
> > using (a). Additional GIDs may be assigned using (b) and/or (c). Note:
> A
> > subnet
> > shall only have one assigned GID prefix (non default) at any given
> > time.
> > 
> > _______________________________________________
> > openib-general mailing list
> > openib-general at openib.org
> > http://openib.org/mailman/listinfo/openib-general
> > 
> > To unsubscribe, please visit
> http://openib.org/mailman/listinfo/openib-general
> > 
>