I ran dmesg -w and with that session open, unplugged the cable, watched the light go out on the port, and then plugged it back in, watched the light come on. No new messages appeared in the output of the session.
Help Configuring a Network Adapter on VE Host
- Thread starter greenhornet
- Start date
Unusual, but Kernel/NIC interaction depends on the vendor.
You can use "ip link set DEV up" to force NIC up to see if the link is detected and confirm cable to port relationship.
https://access.redhat.com/sites/def...s/rh_ip_command_cheatsheet_1214_jcs_print.pdf
Then, you can alter your configuration file to bring that interface up with appropriate IP configuration.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You can use "ip link set DEV up" to force NIC up to see if the link is detected and confirm cable to port relationship.
https://access.redhat.com/sites/def...s/rh_ip_command_cheatsheet_1214_jcs_print.pdf
Then, you can alter your configuration file to bring that interface up with appropriate IP configuration.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Fair point. This is pretty standard hardware though. It's an HPDL380 G7 with an add on NIC - Intel Ethernet Converged Network Adapter X540-T2. I would think this would be pretty common equipment, but I might be making false assumptions there. I will give the ip command guide you listed a review and give it a try. I'll report back. Thanks.
You don't have
You have
Your
Best
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
ens3f0.You have
enp3s0f0 and enp3s0f0.Your
enp3s0f0 is already UP as evident from ip a output. Best
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
OK... looks like I was able to find the correct device ( ens2f1 ) . After bringing it up, I'm seeing: ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP>
Now I'll try to manually configure and test. Thank you for the guidance.
root@jayne:~# ip link set ens2f1 up
root@jayne:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether 9c:8e:99:0f:be:24 brd ff:ff:ff:ff:ff:ff
3: enp3s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 9c:8e:99:0f:be:26 brd ff:ff:ff:ff:ff:ff
4: enp4s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 9c:8e:99:0f:be:28 brd ff:ff:ff:ff:ff:ff
5: enp4s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 9c:8e:99:0f:be:2a brd ff:ff:ff:ff:ff:ff
6: ens2f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether a0:36:9f:37:d2:b4 brd ff:ff:ff:ff:ff:ff
altname enp11s0f0
7: ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:37:d2:b6 brd ff:ff:ff:ff:ff:ff
altname enp11s0f1
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 9c:8e:99:0f:be:24 brd ff:ff:ff:ff:ff:ff