No Network After Step 31 - Eve-NG Pro Bare Install

[tiorico]

After setting up IP address information in the series of text UI dialogs in Step 31, the system reboots and comes back up without connectivity. Debugging, I found that the server still shows (ip a) eth0-eth3 interfaces and all of them are down, so it has no route out. I compared this to a running Eve-NG Pro server and the running version shows all of the pnet interfaces. Before step 31 the eth0 interface was up and functional. So it appears something happened after entering the eve IP info in step 31 which prevented the pnet bridges from being created. I ran through the process twice to make sure I didn't miss anything and had the same results both times. Everything in the preceding process went smoothly both times without any errors. This is a bare metal install on a Dell R710. I have another Dell R710 that is running an earlier version of Eve (4.0.1-56) that I followed the same process for and had no issues.

[Uldis (UD)]

you have to check order of your NICs
Comppare what MAC address belong to which interface, might be simply physical interfaces swap cable will need on server
With ubuntu such happens especially if your Server have 4 or more NICs

[tiorico]

I've verified MAC addresses stay aligned with interface names before/after step 31. I tried the moving the cable to each to verify, but no luck.

When I look at the 'ip a' output of an operational server, I see 10 pnetX interfaces as well as a nat0 and docker0 interface. I also see pnet0 linked to eth0 like this"

Code: Select all

eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master pnet0 state UP group default qlen 1000

None of these pnet/nat/docker interfaces exist on the server I'm trying to install after step 31. It is like the step that creates the pnetX interfaces and links them to the ethX isn't happening.

One thing that I was wondering is in step 25 where the interface name is changed from 'ensxxx' to 'eth0' in '00-installer-config.yaml'. Does this need to happen for the other 3 interfaces (ensp2/3/4 change to eth1/eth2/eth3)? The docs don't say.

[candidhat]

Hi

I've hit this issue too - did you ever get to the bottom of it?


EDIT: I've fixed this. It's netplan. After the install, there's a setup process that asks again for hostname, IP address etc for the node. Once this is complete, it must generate a new Netplan .yaml file. The yaml includes quotation marks for IP address and DNS. Remove the quotation marks, save, then sudo netplan apply.

[tiorico]

I hadn't gotten to the bottom of it. What you described wasn't the problem in my environment as after the Eve install, the netplan yaml file didn't exist. However this did get me looking at a few things and I ended up finding the problem. The issue was that during the install I didn't specify a dns domain. While looking for the netplan yaml I noticed the interfaces file, so took a look and everything looked right. I then tried running ifup and this failed...because the dns-domain line was blank. I manually added a domain and I could run ifup and after a reboot all of the interfaces came up. I'm speculating the installer calls 'ifup' which failed and the network never came up. I spent too many hours messing with this, doh.