F5F Stay Refreshed Power Users Networks ConnectX-5 isn't responding, the other NICs are functioning properly.

ConnectX-5 isn't responding, the other NICs are functioning properly.

ConnectX-5 isn't responding, the other NICs are functioning properly.

A
AllTheWorID
Junior Member
4
06-18-2023, 05:36 PM
#1
A
AllTheWorID
06-18-2023, 05:36 PM #1

X
xanderzone317
Posting Freak
957
06-18-2023, 06:10 PM
#2
What path are you considering next? Are you checking for Link State updates or relying on DHCP to assign an IP? Have you adjusted the Netplan YAML to use DHCP or static assignment for this interface?
X
xanderzone317
06-18-2023, 06:10 PM #2

What path are you considering next? Are you checking for Link State updates or relying on DHCP to assign an IP? Have you adjusted the Netplan YAML to use DHCP or static assignment for this interface?

M
Marinated
Senior Member
666
06-20-2023, 05:15 AM
#3
I assume it's similar to my other NIC. The links are active so they should appear as up. DHCP should assign an IP automatically, correct? I haven't modified the YAML before, but I've never needed to in the past either. With a ConnectX-2, I can simply get an IP from DHCP without any extra steps.
M
Marinated
06-20-2023, 05:15 AM #3

I assume it's similar to my other NIC. The links are active so they should appear as up. DHCP should assign an IP automatically, correct? I haven't modified the YAML before, but I've never needed to in the past either. With a ConnectX-2, I can simply get an IP from DHCP without any extra steps.

0
0w8
Junior Member
19
06-20-2023, 06:36 AM
#4
0
0w8
06-20-2023, 06:36 AM #4

B
Bobster64HD
Member
129
06-20-2023, 02:19 PM
#5
Sure, I modified them that way. The server is now restarting. Hope that helps.
B
Bobster64HD
06-20-2023, 02:19 PM #5

Sure, I modified them that way. The server is now restarting. Hope that helps.

Z
ZoloKu
Member
206
06-23-2023, 04:11 PM
#6
You're seeing no IP address assigned even though the interfaces appear active. The system shows "DOWN" for physical links, but the YAML lists them as up. Trying to force interfaces upward in ifconfig usually helps, and checking physical connections or network settings might resolve the issue.
Z
ZoloKu
06-23-2023, 04:11 PM #6

You're seeing no IP address assigned even though the interfaces appear active. The system shows "DOWN" for physical links, but the YAML lists them as up. Trying to force interfaces upward in ifconfig usually helps, and checking physical connections or network settings might resolve the issue.

D
DeadpoOol
Member
175
06-23-2023, 05:01 PM
#7
She’s here! After a few updates and the addition of the missing enp6xxx interfaces, it finally functions again. Thanks a lot for your assistance! I was puzzled as to why I overlooked the YAML file during my research.
D
DeadpoOol
06-23-2023, 05:01 PM #7

She’s here! After a few updates and the addition of the missing enp6xxx interfaces, it finally functions again. Thanks a lot for your assistance! I was puzzled as to why I overlooked the YAML file during my research.

K
Kunall
Member
205
06-30-2023, 03:19 AM
#8
It's intriguing that IBST is displaying active status and linking as expected, even though it's limited to Ethernet on the X-5. It seems possible that at a deeper level, it might still be mimicking IP over InfiniBand. Links are working and traffic is moving smoothly.
K
Kunall
06-30-2023, 03:19 AM #8

It's intriguing that IBST is displaying active status and linking as expected, even though it's limited to Ethernet on the X-5. It seems possible that at a deeper level, it might still be mimicking IP over InfiniBand. Links are working and traffic is moving smoothly.

K
Kitten645321
Member
181
07-05-2023, 09:23 AM
#9
Sorry I wasn't able to respond quickly. I just returned from work. Good to know it's working. For future use, when updating the .YAML file instead of rebooting, run: netplan try This reads the YAML and verifies syntax which helps with bringing interfaces online. Normally you'd use netplan apply afterward to confirm changes without a reboot, though these steps often handle both. On Ubuntu Server, after initial setup you must manually add new interfaces via .YAML since they don't auto-configure like in Ubuntu Desktop. Unlike Ubuntu Server, servers usually prefer not to auto-setup NICs with DHCP unless instructed. Generally, new interfaces need /etc/rc.conf updates and a service restart for IP assignment. This approach has worked well across various Linux and UNIX distributions such as FreeBSD. New NICs don't auto-configure at installation; you must configure them manually.
K
Kitten645321
07-05-2023, 09:23 AM #9

Sorry I wasn't able to respond quickly. I just returned from work. Good to know it's working. For future use, when updating the .YAML file instead of rebooting, run: netplan try This reads the YAML and verifies syntax which helps with bringing interfaces online. Normally you'd use netplan apply afterward to confirm changes without a reboot, though these steps often handle both. On Ubuntu Server, after initial setup you must manually add new interfaces via .YAML since they don't auto-configure like in Ubuntu Desktop. Unlike Ubuntu Server, servers usually prefer not to auto-setup NICs with DHCP unless instructed. Generally, new interfaces need /etc/rc.conf updates and a service restart for IP assignment. This approach has worked well across various Linux and UNIX distributions such as FreeBSD. New NICs don't auto-configure at installation; you must configure them manually.