(FIXED) ifupdown problem with Mellanox ethernet cards
ufm
46 Posts
April 17, 2020, 10:02 amQuote from ufm on April 17, 2020, 10:02 amUPDATE: In 2.7.1 this issue has been fixed.
Hi!
As described here - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976 ifupdown prior vewrsion 0.8.27 have bug in detection interface type. Short patch description:
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.
I found fast fix - if after boot do rmmod mlx5_ib ; rmmod mlx5_core ; modprobe mlx5_core - network is up.
Two question:
- Are there any plans to upgrade to the new version of Ubuntu?
- Where can I place these commands so that they are called at the time of each download before working with the network (and at the same time it does not interfere with the standard work of PetaSAN)?
UPDATE: In 2.7.1 this issue has been fixed.
Hi!
As described here - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976 ifupdown prior vewrsion 0.8.27 have bug in detection interface type. Short patch description:
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.
I found fast fix - if after boot do rmmod mlx5_ib ; rmmod mlx5_core ; modprobe mlx5_core - network is up.
Two question:
- Are there any plans to upgrade to the new version of Ubuntu?
- Where can I place these commands so that they are called at the time of each download before working with the network (and at the same time it does not interfere with the standard work of PetaSAN)?
Last edited on February 9, 2021, 3:40 pm by ufm · #1
admin
2,918 Posts
April 17, 2020, 11:23 amQuote from admin on April 17, 2020, 11:23 amIf you mean the upcoming Ubuntu 20.04, we have plans but it will be a while. Note we use a SUSE kernel and this may be kernel related, we typically upgrade kernels more frequent.
you may also specify if you want to load specific kernel modules, or blacklist modules in /etc/modprobe.d/
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
If you mean the upcoming Ubuntu 20.04, we have plans but it will be a while. Note we use a SUSE kernel and this may be kernel related, we typically upgrade kernels more frequent.
you may also specify if you want to load specific kernel modules, or blacklist modules in /etc/modprobe.d/
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
ufm
46 Posts
April 17, 2020, 11:32 amQuote from ufm on April 17, 2020, 11:32 am
Quote from admin on April 17, 2020, 11:23 am
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
But as I understand - after any upgrade need patch this file again?
Quote from admin on April 17, 2020, 11:23 am
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
But as I understand - after any upgrade need patch this file again?
admin
2,918 Posts
April 17, 2020, 12:41 pmQuote from admin on April 17, 2020, 12:41 pmCan you name the script
/opt/petasan/scripts/pre_start_network.sh
and we can check for this path if present
Can you name the script
/opt/petasan/scripts/pre_start_network.sh
and we can check for this path if present
Last edited on April 17, 2020, 12:42 pm by admin · #4
ufm
46 Posts
April 17, 2020, 9:06 pmQuote from ufm on April 17, 2020, 9:06 pmWow. That would be just great! Thanks!
Wow. That would be just great! Thanks!
ufm
46 Posts
April 18, 2020, 12:19 amQuote from ufm on April 18, 2020, 12:19 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) ifupdown problem with Mellanox ethernet cards
ufm
46 Posts
Quote from ufm on April 17, 2020, 10:02 amUPDATE: In 2.7.1 this issue has been fixed.
Hi!
As described here - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976 ifupdown prior vewrsion 0.8.27 have bug in detection interface type. Short patch description:
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.I found fast fix - if after boot do rmmod mlx5_ib ; rmmod mlx5_core ; modprobe mlx5_core - network is up.
Two question:
- Are there any plans to upgrade to the new version of Ubuntu?
- Where can I place these commands so that they are called at the time of each download before working with the network (and at the same time it does not interfere with the standard work of PetaSAN)?
UPDATE: In 2.7.1 this issue has been fixed.
Hi!
As described here - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857976 ifupdown prior vewrsion 0.8.27 have bug in detection interface type. Short patch description:
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.
I found fast fix - if after boot do rmmod mlx5_ib ; rmmod mlx5_core ; modprobe mlx5_core - network is up.
Two question:
- Are there any plans to upgrade to the new version of Ubuntu?
- Where can I place these commands so that they are called at the time of each download before working with the network (and at the same time it does not interfere with the standard work of PetaSAN)?
admin
2,918 Posts
Quote from admin on April 17, 2020, 11:23 amIf you mean the upcoming Ubuntu 20.04, we have plans but it will be a while. Note we use a SUSE kernel and this may be kernel related, we typically upgrade kernels more frequent.
you may also specify if you want to load specific kernel modules, or blacklist modules in /etc/modprobe.d/
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
If you mean the upcoming Ubuntu 20.04, we have plans but it will be a while. Note we use a SUSE kernel and this may be kernel related, we typically upgrade kernels more frequent.
you may also specify if you want to load specific kernel modules, or blacklist modules in /etc/modprobe.d/
within PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
ufm
46 Posts
Quote from ufm on April 17, 2020, 11:32 amQuote from admin on April 17, 2020, 11:23 amwithin PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to callBut as I understand - after any upgrade need patch this file again?
Quote from admin on April 17, 2020, 11:23 amwithin PetaSAN, you can insert a custom script to run before network configuration, edit file:
/opt/petasan/scripts/node_start_ips.py
at top of file
logger.debug("Loading network configurations.")
call_cmd("script_path") # add this ..replace script_path with any executable script you want to call
But as I understand - after any upgrade need patch this file again?
admin
2,918 Posts
Quote from admin on April 17, 2020, 12:41 pmCan you name the script
/opt/petasan/scripts/pre_start_network.sh
and we can check for this path if present
Can you name the script
/opt/petasan/scripts/pre_start_network.sh
and we can check for this path if present
ufm
46 Posts
Quote from ufm on April 17, 2020, 9:06 pmWow. That would be just great! Thanks!
Wow. That would be just great! Thanks!
ufm
46 Posts
Quote from ufm on April 18, 2020, 12:19 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.