Full vs Limited IB partition members
An IB port can either be a full member or limited member of a partition. The difference is simple. All full members within a partition can see and communicate to each other as well as limited members in the same partition. However, the limited members cannot see and communicate to other limited members in same partition but they can see and communicate with full members.
To illustrate better lets take example where A & B have full membership to partition and C & D have limited membership to partition. So below will be the behavior.
Special case membership - 'BOTH'
When we deal with virtual machines in Linux (XEN or OVS), there may be a scenario where some VM IB ports need to be limited and some as full which are all running on same Dom0 Hypervisor. In these scenarios there is special membership called BOTH where Port GUIDs of Dom0 Hypervisor can be added as BOTH member to partition. With Port GUIDs of Dom0 added as BOTH membership to partition VM's membership running on Dom0 can either be full or limited. VM membership to a partition whether it is full or limited is defined in vm.cfg file. BOTH membership is commonly seen in Exalogic deployments.
An IB port can either be a full member or limited member of a partition. The difference is simple. All full members within a partition can see and communicate to each other as well as limited members in the same partition. However, the limited members cannot see and communicate to other limited members in same partition but they can see and communicate with full members.
To illustrate better lets take example where A & B have full membership to partition and C & D have limited membership to partition. So below will be the behavior.
- So A & B (full members) can communicate with each other and to C & D (limited members).
- C & D (limited members) cannot communicate with each other (as they both are limited members). But C & D (limited) members can communicate to A & B (full members).
Special case membership - 'BOTH'
When we deal with virtual machines in Linux (XEN or OVS), there may be a scenario where some VM IB ports need to be limited and some as full which are all running on same Dom0 Hypervisor. In these scenarios there is special membership called BOTH where Port GUIDs of Dom0 Hypervisor can be added as BOTH member to partition. With Port GUIDs of Dom0 added as BOTH membership to partition VM's membership running on Dom0 can either be full or limited. VM membership to a partition whether it is full or limited is defined in vm.cfg file. BOTH membership is commonly seen in Exalogic deployments.
Products to which Article Applies
OVS Deployments using Infiniband, Exalogic
tarun boyella
No comments:
Post a Comment