Bug report: ConnectX-5 unable to use non-default P_Key
This is with plain 4.13-rc7.
Attempts to bring up the 0x8002 P_Key IPoIB device using dhcp fail and NetworkManager releases the device.
Switch to static IP configuration, the device comes up, but IPoIB is unable to ping other devices on the 0x8002 P_Key.
I tried other means of trying to communicate over a specific P_Key, and I seem to recall we used to have the option to specify the target using the GUID, but I couldn't find any tools that still allow me to specify a target that way and also allow me to specify the P_Key (it probably exists, I just don't know which tool to use to do it).
Signature · 8 lines
Doug Ledford <[email protected]> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Doug Ledford
This is with plain 4.13-rc7.
Attempts to bring up the
0x8002P_KeyIPoIB device using dhcp fail and NetworkManager releases the device.
In rawhide, the enhanced IPoIB is enabled by default and the upstream version has limitation which you are experienced. This is the main reason, why we didn't enable it by default. Alex and his team are working to prepare upstream patches from our MLNX_OFED solution to allow such configuration and I'll forward them as soon as they will be ready.
Thanks