[SOLVED] Peer/Cluster Communication not Working

[pker]

Hi, I've setted up two Proxmox Servers in my home lab, each one running in a distinct physical server, but can't ping each other, neither join the same cluster.

Both PVE can:

• Ping the gateway (192.168.15.1);
• Ping outside ips (8.8.8.8)
• Ping other devices in lan;
• Receives pings from my own desktop

Both PVE can't:

• Join cluster (500 ERROR; Unable to Reach Host)
• Ping each other (Unable to Reach Host)

Spoiler: PVE1 - ip a && ip r

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000 link/ether 74:27:ea:63:e6:6e brd ff:ff:ff:ff:ff:ff 3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 74:27:ea:63:e6:6e brd ff:ff:ff:ff:ff:ff inet 192.168.15.111/24 scope global vmbr0 valid_lft forever preferred_lft forever inet6 fe80::7627:eaff:fe63:e66e/64 scope link valid_lft forever preferred_lft forever default via 192.168.15.1 dev vmbr0 proto kernel onlink 192.168.15.0/24 dev vmbr0 proto kernel scope link src 192.168.15.111

Spoiler: PVE1 - cat /etc/network/interfaces

iface lo inet loopback iface enp2s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.15.111/24 gateway 192.168.15.1 bridge-ports enp2s0 bridge-stp off bridge-fd 0

Spoiler: PVE2 - ip a && ip r

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000 link/ether 74:27:ea:64:1f:51 brd ff:ff:ff:ff:ff:ff 3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 74:27:ea:64:1f:51 brd ff:ff:ff:ff:ff:ff inet 192.168.15.112/24 scope global vmbr0 valid_lft forever preferred_lft forever inet6 fe80::7627:eaff:fe64:1f51/64 scope link valid_lft forever preferred_lft forever default via 192.168.15.1 dev vmbr0 proto kernel onlink 192.168.15.0/24 dev vmbr0 proto kernel scope link src 192.168.15.112

Spoiler: PVE2 - cat /etc/network/interfaces

auto lo iface lo inet loopback iface enp2s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.15.112/24 gateway 192.168.15.1 bridge-ports enp2s0 bridge-stp off bridge-fd 0

 

[shanreich]

Can you post the output of the Cluster Join log?
Additionally the contents of /etc/hosts of both nodes would be interesting

 

[pker]

Spoiler: PVE2 trying to join cluster created at PVE1

Spoiler: PVE1 - cat /etc/hosts

127.0.0.1 localhost.localdomain localhost 192.168.15.111 pve.andradejoaoh pve # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts

Spoiler: PVE2 - cat /etc/hosts

127.0.0.1 localhost.localdomain localhost 192.168.15.112 pve2.andradejoaoh pve2 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts

 

[shanreich]

What are the hostnames of both hosts? cat /etc/hostname

 

[pker]

PVE1:

PVE2:

 

[shanreich]

Quite odd, do you have any Firewall set in PVE or in between the nodes that could block the connection?

 

[pker]

I haven't set any firewalls, they were fresh installed, I didn't change anything.
I don't think the router is blocking it.

 

[pker]

Quite odd, do you have any Firewall set in PVE or in between the nodes that could block the connection?

Thanks for the help, it was my switch that was creating a VLAN and I wasn't able to access.