On 03/10/10 03:52 PM, Ted Kim wrote:
> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
> This information is Copyright 2010 Sun Microsystems
> 1. Introduction
> 1.1. Project/Component Working Name:
> IPoIB Administration Enhancement
> 1.2. Name of Document Author/Supplier:
> Author: Sudhakar Dindukurti
> 1.3 Date of This Document:
> 10 March, 2010
> 4. Technical Description
>
> 4.1 Acronyms
>
> HCA : Host Channel Adaptor
> P_Key : Partition Key
> IPoIB : IP over InfiniBand
> GUID : Global Unique Identifier
> IBTF : InfiniBand Transport Framework
> IBCM : InfiniBand Communication Manager
> SDP : Sockets Direct Protocol
> IBD : current IPoIB Solaris driver name
> ULP : Upper level Protocol
>
> 4.2 Requirements/Motivation
> ---------------------------
>
> 4.2.1 Consistent IBD device node naming across nodes in a clusters
>
> (Amber Road Requirement (CR 6864899))
>
> AmberRoad clustering software requires that datalink name for a specific
> partition on multiple nodes (identical h/w configuration) to be same. For
> example, if datalink name on node 1 for a P_key 0x8001 on HCA 1 and port 1
> is ibnet0, then the clustering software expects that datalink name for
> P_Key 0x8001 on HCA 1 and port 1 is also ibnet0 on the node 2 in the
> cluster. This is very difficult to achieve today. The problem is that
> IPoIB device name is constructed automatically by IPoIB driver by
> appending the instance number to the driver name (ex ibd0, ibd1, etc). So,
> the clustering software does not have any control on the IPoIB device
> name space. Also, IBTF framework does not guarantee that the same names
> across multiple nodes.
>
It seems like this is a bug in Amber Road, best dealt with there. Also,
how does this respond in the presence of Clearview Vanity Naming?
- Garrett
