Hal, If you would like to use my example configuration in the man page (the one with realistic GUID's) please feel free to do so. The GUID's are all imaginary but realistic.
Are you sure the default partition should be "Default=0x7fff,ipoib,rate=7:ALL,SELF=full;" and not "Default=0x7fff:SELF=full,ALL=limited;"? The second version forces both known and unknown CA's to be unable to reach any CA but the sm except via their own partition. It also seems to me that the first version bypasses partitioning by allowing CA's to use the default partition to reach other CA's not in the same partition. Also, if you would like, I would be happy to work on a version of the man page where I would try to possibly explain a bit more and have more complete examples. Thanks, Don Meyer Senior Network/System Engineer/Programmer US+ (253) 371-9532 iNet 8-371-9532 *Other names and brands may be claimed as the property of others ________________________________ From: Hal Rosenstock [mailto:[email protected]] Sent: Thursday, September 03, 2009 6:46 AM To: [email protected] Cc: Meyer, Donald J; [email protected] Subject: Re: [ofa-general] question about partitioning IB networks On Thu, Sep 3, 2009 at 9:43 AM, Yevgeny Kliteynik <[email protected]<mailto:[email protected]>> wrote: Hal Rosenstock wrote: On Mon, Aug 31, 2009 at 3:29 PM, Meyer, Donald J <[email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>>> wrote: ... ... Just as a sanity check, my interpretation so far is that my network should have a partition configuration file similar to the following. Can anyone tell me if I have this correct? In this example configuration, I am trying to create two partitions. One with rack one and two, the other with rack three and four: #Default partition (for SM control of the CA's) Default=0x7fff,ipoib,rate=7:ALL=limited; Default=0x7fff,ipoib,rate=7:ALL,SELF=full; #rack1 rack1=0x111,ipoib,rate=7,defmember=full:<GUID_list>; #rack2 rack2=0x111,ipoib,rate=7,defmember=full:<GUID_list>; #rack3 rack3=0x112,ipoib,rate=7,defmember=full:<GUID_list>; #rack4 rack4=0x112,ipoib,rate=7,defmember=full:<GUID_list>; I've never done it this way but it does look like the partition create code will detect the duplicated partitions (0x111 and 0x112) and merge ports from rack2 with rack1 and rack4 with rack3. It will. Note that partition names are meaningless in terms of IB management. Basically they are used just for logging. The only real partition ID is its pkey. The low 7 bits (without membership bit) of pkey denotes partition. -- Hal -- Yevgeny -- Hal *Thanks,* *Don Meyer* /Senior Network/System Engineer/Programmer/ US+ (253) 371-9532 iNet 8-371-9532 /*Other names and brands may be claimed as the property of others/ _______________________________________________ general mailing list [email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general ------------------------------------------------------------------------ _______________________________________________ general mailing list [email protected]<mailto:[email protected]> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
_______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
