Adding 2nd NIC

I have HA running in a VM. I am wanting to move it to another subnet so am adding a 2nd NIC so that once up, I can remove the one that is linked to the old subnet.

I have added the NIC in the VM but not seeing it in HA.

When I ssh into HA I get the following:

[core-ssh ~]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
20: eth0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:ac:1e:21:01 brd ff:ff:ff:ff:ff:ff

So the 2nd NIC is not seen.

But the below indicates that it is there (got this command from googling)

[core-ssh ~]$ dmesg | grep -i "eth1\|enX1"
[    8.376407] vif vif-1 enX1: renamed from eth1
[   78.455174] hassio: port 1(veth1b41010) entered blocking state
[   78.455183] hassio: port 1(veth1b41010) entered disabled state
[   78.455196] veth1b41010: entered allmulticast mode
[   78.456776] veth1b41010: entered promiscuous mode
[   78.462809] hassio: port 1(veth1b41010) entered blocking state
[   78.462816] hassio: port 1(veth1b41010) entered forwarding state
[   78.465175] hassio: port 1(veth1b41010) entered disabled state
[   79.400302] hassio: port 1(veth1b41010) entered blocking state
[   79.400309] hassio: port 1(veth1b41010) entered forwarding state
[   82.214422] eth1: renamed from veth425ab4f
[   90.568452] eth0: renamed from veth103860e
[  115.588012] eth0: renamed from veth18cfd08

and HA can see the NIC as per the below:

Very strange indeed. It seems that only the core_ssh container is the one not seeing it. So maybe restart your VM if you haven’t already.

Rebooted again and then realised there must be a cabling issue… which there was… so sorted:)