no network access to/from proxmox host after making network changes, updating, and restarting

[pzerkel]

I am new to Proxmox VE. Currently evaluating it as a potential VMware replacement.

I have a Dell R840xd server. It has the two integrated 1GB Ethernet ports, one of which is being used to connect to the management network. I also have two 2-port 10Gbe SFP+ cards installed, which will be used to connect to storage on an IxSystems SAN.

For testing purposes, I only connected one of the 1 GB Ethernet ports (to our management switch) and one of the 10GB ports (to our 10GB switch for storage).

Initially (for the 1st 24 hours or so) I was able to log into the web console for Proxmox. That was working ok, but I wanted to start assigning an IP to the 10gb card for storage. When I tried to assign it an IP, it told me I could not (while I do not remember the exact error-I believe it said it was part of vmbr0. I was able to remove it from there and assign it an IP (on the storage subnet).

At the same time, I have been watching the Youtube playlist from LearnLinuxTV about proxmox. In one of those videos he demo’d how to update the system. I followed that then re-booted the host. After the reboot, I was unable to ping the host. I also could not ping anything from the local host. Not the gateway nor any other device on the subnet.

I suspect my problem has more to do with me changing the network settings, than doing the updates, but I do not know for sure.

I re-installed proxmox this morning and after rebooting I am still unable to ping anything.

lo, eno1np0, eno3, eno2np1, eno4, ens2f1np0, ensf1np1 and vmbr0.

ip a initially showed these all down (except for lo). The assigned IP shows under vmbr0. All other ports showed down initially. The two ports with cables connected are eno3 (1 gig) and eno2np1 (10 gig). I was able to run “ifup eno3” and “ifup eno2np1” . After that “ip a” does show those two ports as up. But vmbr0 is still showing down. I have tried “ifup vmbr0”, but still shows down.

I do not believe this is a firewall issue because I can take a laptop, assign it the same ip as the proxmox host is using and plug it into the same cable and I have network connectivity.

 

[Chris]

Hi,
please share the output of cat /etc/network/interfaces so we might see your actual network config. Also, the output of ip route and ip link as well as the latest ifupdown2 log located in the corresponding subfolder of /var/log/ifupdown2.

 

[pzerkel]

OK, starting here with output from cat /etc/network/interfaces. Note that because I have no network conectivity, I could not cut and paste. So I took a screenshot with my phone and then manually typed in the below. I have tried to be careful to avoid typos, but you never know...

-----------------------------------------------------
auto lo
iface lo inet loopback

iface eno1np0 inet manual

auto vmbr0
iface inet static
address 192.1681.40/24
gateway 192.168.1.1
bridge-ports eno1np0
bridge-stp off
bridge-fd 0

iface eno3 inet manual

iface eno2np1 inet manual

iface eno4 inet manual

iface ens2f0np0 inet manual

iface ens2f1np1 inet manual
------------------------------------------------------------

The first thing I notice is that vmbr0 shows bridge-ports eno1np0. I believe that should be referring to eno3, which is the switch connected to the 192.168.1.0/24 subnet switch. But I am not sure how to make that change.

I will put the other requested data in a separate post.

Thank Uoi.

 

[pzerkel]

I am attaching screenshots of output form "ip route" and "ip link". I am still working on getting the latest ifupdown2 log.

 

[Chris]

address 192.1681.40/24

I assume the missing dot here is a typo, should state address 192.168.1.40/24

bridge-ports eno1np0

The first thing I notice is that vmbr0 shows bridge-ports eno1np0. I believe that should be referring to eno3, which is the switch connected to the 192.168.1.0/24 subnet switch. But I am not sure how to make that change.

If that is the case, you should adapt this to bridge-ports eno3 and reload the config via ifreload -a after editing and saving the network config.
By this you logically bind the interface to the bridge, the bridge carrying the IPv4 address which allows you to connect to the host.

Note, if you have ethtool installed, you can identify the ports by blinking them via ethtool -p <ifname>.

 

[pzerkel]

Thank You! I have network connectivity now and am able to log into the console.

First, yes that missing dot was a type. Changing the line to bridge-ports eno3 and doing the ifreload -a got it working! Thanks Again!

What I have not yet tested is whether this will continue working after a reboot.

 

[pzerkel]

Happy to report, that I just rebooted, and I still have network connectivity. Thank You again!