(FIXED) mellanox nic - wrong ib/ether detection
ufm
46 Posts
April 17, 2020, 12:28 amQuote from ufm on April 17, 2020, 12:28 amPlease help.
I encountered the problem described here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976
May be anyone have solution for this trouble?
UPDATE: In 2.7.1 this issue has been fixed.
Please help.
I encountered the problem described here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976
May be anyone have solution for this trouble?
UPDATE: In 2.7.1 this issue has been fixed.
Last edited on February 9, 2021, 3:39 pm by ufm · #1
Kurti2k
16 Posts
April 17, 2020, 8:42 amQuote from Kurti2k on April 17, 2020, 8:42 amHello, it may help you
you must change Port Type from your MLX Card
InfiniBand (1)
Ethernet (2)
AutoSense (3)
default set is 3
set port type to 2 (edit /dev/mtXXXX_pciconfX)
mst status
mlxconfig -d /dev/mt4121_pciconf0 set LINK_TYPE_P1=2 LINK_TYPE_P2=2
reboot
Best Regards
Hello, it may help you
you must change Port Type from your MLX Card
InfiniBand (1)
Ethernet (2)
AutoSense (3)
default set is 3
set port type to 2 (edit /dev/mtXXXX_pciconfX)
mst status
mlxconfig -d /dev/mt4121_pciconf0 set LINK_TYPE_P1=2 LINK_TYPE_P2=2
reboot
Best Regards
ufm
46 Posts
April 17, 2020, 9:25 amQuote from ufm on April 17, 2020, 9:25 amUnfortunately not. 🙁
First esxi not absolutely Linux.
Secondly, the problem here is not so much that the network card says that it is included in the infiniband, but that the ifup incorrectly determines card connection. And in the new version, this is fixed.
Unfortunately not. 🙁
First esxi not absolutely Linux.
Secondly, the problem here is not so much that the network card says that it is included in the infiniband, but that the ifup incorrectly determines card connection. And in the new version, this is fixed.
ufm
46 Posts
April 17, 2020, 9:48 amQuote from ufm on April 17, 2020, 9:48 amThis quote from patch for ifupdown, as I unnderstand accepted in version 0.8.27 (petasan uses 0.8.17ubuntu1.1)
Detecting an Infiniband interface by testing for the existence of
/sys/class/net/%link%/device/infiniband is unreliable, as an
Infiniband capable port running in Ethernet mode may still have
the Infiniband directory in sysfs. When this type of port is in
Ethernet mode, ifupdown attempts and fails to create an Infiniband
partition on the Ethernet port, instead of creating a VLAN.
This quote from patch for ifupdown, as I unnderstand accepted in version 0.8.27 (petasan uses 0.8.17ubuntu1.1)
Detecting an Infiniband interface by testing for the existence of
/sys/class/net/%link%/device/infiniband is unreliable, as an
Infiniband capable port running in Ethernet mode may still have
the Infiniband directory in sysfs. When this type of port is in
Ethernet mode, ifupdown attempts and fails to create an Infiniband
partition on the Ethernet port, instead of creating a VLAN.
Kurti2k
16 Posts
April 17, 2020, 10:04 amQuote from Kurti2k on April 17, 2020, 10:04 amwhat Mellanox cards used ?
Best regards
what Mellanox cards used ?
Best regards
ufm
46 Posts
April 17, 2020, 10:17 amQuote from ufm on April 17, 2020, 10:17 am
Quote from Kurti2k on April 17, 2020, 10:04 am
what Mellanox cards used ?
Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
Quote from Kurti2k on April 17, 2020, 10:04 am
what Mellanox cards used ?
Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
ufm
46 Posts
April 18, 2020, 12:20 amQuote from ufm on April 18, 2020, 12:20 amAdditional information: Looks like to replacing ifupdown package to ifupdown2 resolve this trouble. I'm not sure that such a replacement will not break anything else, but it solves this problem.
Additional information: Looks like to replacing ifupdown package to ifupdown2 resolve this trouble. I'm not sure that such a replacement will not break anything else, but it solves this problem.
(FIXED) mellanox nic - wrong ib/ether detection
ufm
46 Posts
Quote from ufm on April 17, 2020, 12:28 amPlease help.
I encountered the problem described here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976
May be anyone have solution for this trouble?
UPDATE: In 2.7.1 this issue has been fixed.
Please help.
I encountered the problem described here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976
May be anyone have solution for this trouble?
UPDATE: In 2.7.1 this issue has been fixed.
Kurti2k
16 Posts
Quote from Kurti2k on April 17, 2020, 8:42 amHello, it may help youyou must change Port Type from your MLX Card
InfiniBand (1)
Ethernet (2)
AutoSense (3)default set is 3
set port type to 2 (edit /dev/mtXXXX_pciconfX)
mst status
mlxconfig -d /dev/mt4121_pciconf0 set LINK_TYPE_P1=2 LINK_TYPE_P2=2
reboot
Best Regards
Hello, it may help you
you must change Port Type from your MLX Card
InfiniBand (1)
Ethernet (2)
AutoSense (3)default set is 3
set port type to 2 (edit /dev/mtXXXX_pciconfX)
mst status
mlxconfig -d /dev/mt4121_pciconf0 set LINK_TYPE_P1=2 LINK_TYPE_P2=2
reboot
Best Regards
ufm
46 Posts
Quote from ufm on April 17, 2020, 9:25 amUnfortunately not. 🙁
First esxi not absolutely Linux.
Secondly, the problem here is not so much that the network card says that it is included in the infiniband, but that the ifup incorrectly determines card connection. And in the new version, this is fixed.
Unfortunately not. 🙁
First esxi not absolutely Linux.
Secondly, the problem here is not so much that the network card says that it is included in the infiniband, but that the ifup incorrectly determines card connection. And in the new version, this is fixed.
ufm
46 Posts
Quote from ufm on April 17, 2020, 9:48 amThis quote from patch for ifupdown, as I unnderstand accepted in version 0.8.27 (petasan uses 0.8.17ubuntu1.1)
Detecting an Infiniband interface by testing for the existence of
/sys/class/net/%link%/device/infiniband is unreliable, as an
Infiniband capable port running in Ethernet mode may still have
the Infiniband directory in sysfs. When this type of port is in
Ethernet mode, ifupdown attempts and fails to create an Infiniband
partition on the Ethernet port, instead of creating a VLAN.
This quote from patch for ifupdown, as I unnderstand accepted in version 0.8.27 (petasan uses 0.8.17ubuntu1.1)
Detecting an Infiniband interface by testing for the existence of
/sys/class/net/%link%/device/infiniband is unreliable, as an
Infiniband capable port running in Ethernet mode may still have
the Infiniband directory in sysfs. When this type of port is in
Ethernet mode, ifupdown attempts and fails to create an Infiniband
partition on the Ethernet port, instead of creating a VLAN.
Kurti2k
16 Posts
Quote from Kurti2k on April 17, 2020, 10:04 amwhat Mellanox cards used ?
Best regards
what Mellanox cards used ?
Best regards
ufm
46 Posts
Quote from ufm on April 17, 2020, 10:17 amQuote from Kurti2k on April 17, 2020, 10:04 amwhat Mellanox cards used ?
Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
Quote from Kurti2k on April 17, 2020, 10:04 amwhat Mellanox cards used ?
Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
ufm
46 Posts
Quote from ufm on April 18, 2020, 12:20 amAdditional information: Looks like to replacing ifupdown package to ifupdown2 resolve this trouble. I'm not sure that such a replacement will not break anything else, but it solves this problem.
Additional information: Looks like to replacing ifupdown package to ifupdown2 resolve this trouble. I'm not sure that such a replacement will not break anything else, but it solves this problem.