[SOLVED] Proxmox-server not reachable after adding hwaddress to /etc/network/interfaces (Upgrade VE 6 to 7)

[r4dh4l]

Hi,

tonight I wanted to upgrade my Proxmox VE 6.4 to version 7. Following the instructions under https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Linux_Bridge_MAC-Address_Change I adjusted /etc/network/interfaces from

root@proxmox-ve6:/# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp2s0f0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.5
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports enp2s0f0
        bridge_stp off
        bridge_fd 0

iface enp2s0f1 inet manual
root@proxmox-ve6:/#

to

root@proxmox-ve6:/# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp2s0f0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.5
        hwaddress 98:f2:b3:e7:c2:48
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports enp2s0f0
        bridge_stp off
        bridge_fd 0

iface enp2s0f1 inet manual
root@proxmox-ve6:/#

because the output of "ip -c link" was:

root@proxmox-ve6:/# ip -c 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: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 98:f2:b3:e7:c2:48 brd ff:ff:ff:ff:ff:ff
3: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 98:f2:b3:e7:c2:49 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 98:f2:b3:e7:c2:48 brd ff:ff:ff:ff:ff:ff
root@proxmox-ve6:/#

Then I rebooted because ifupdown2 was/is not installed. Then I couldn't reach the Proxmox server via SSH (wating for around 30min writing this).

The server is located in another city so I don't have physical right now but I still have access to the router of the remote (home) LAN. The Proxmox server is listed as offline (I'm very sure that I typed "reboot" and not "shutdown -h now").

Any idea what I did wrong (maybe I was misinterpretating the Wiki instructions)?

 

[r4dh4l]

Just got a mail that the server rebooted shortly after publishing my post here. So the reboot needed more than 30mins (which is maybe okay if there were running VMs but all VMs were already offline as preparation for the upgrade process). That's would I call an interesting start for the upgrade process.

TLDR: Problem solved for now.