Search results

  1. D

    Onboard intel nic issue or something else?

    I also noticed this in the gui syslog after a reboot of the new node: Dec 09 13:38:05 pve2 kernel: igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Dec 09 13:38:06 pve2 pvestatd[1076]: storage 'VM-Restore' is not online Dec 09 13:38:06 pve2...
  2. D

    Onboard intel nic issue or something else?

    Recently deployed a new server and created a cluster. New node has an onboard intel nic (I've heard these can be troublesome) - but the problem here is that it is not getting anywhere near the advertised speed. I've checked and replaced cables and this is what i get: new node: root@pve2:~#...
  3. D

    [SOLVED] New NIC best practice?

    Works perfectly, thanks for the assist. No kernel update was needed. Just had to tell the bridge to use the other interface in the UI.
  4. D

    [SOLVED] New NIC best practice?

    Sounds simple enough (famous last words). I'll see what happens after I install it later.
  5. D

    [SOLVED] New NIC best practice?

    Yup, got all that ready once I slap it in there. It looks like I'm on a 5 series kernel unless I'm reading this wrong?
  6. D

    [SOLVED] New NIC best practice?

    Using Proxmox VE for over a week and I love it. Been having that often reported problem with an onboard intel nic (random nic resets) and decided to buy a non-intel pci-nic. What's the best practice for getting that 'noticed' by Proxmox once the physical install is complete? Thanks, Nick