Hi all,
I've configured two hosts in my cluster as per this wiki article https://pve.proxmox.com/wiki/Network_Model#Configuring_VLAN_in_a_cluster
Host #1, has two bonds (one GbE, one 10G) to the switch (Aruba S2500), host #2 has one GbE bond. Switch is configured for passive LACP bonding on all three pairs of ports concerned, and those port channels are configured as trunk ports.
Host #1 /etc/networking/interfaces:
and that of host #2
Hosts can ping the switch on the VLANs but cannot see eachother. When I first configured and brought up vmbr1 and vmbr30 on host #2 it could ping host #1 but not the other way round. Once I rebooted host #2 this was no longer the case.
Switch cannot ping any of the VLAN interfaces on either host, but could temporarily when the bridges were first configured but now cannot post-rebooting both hosts.
Any ideas how I might go about debugging this further?
I've configured two hosts in my cluster as per this wiki article https://pve.proxmox.com/wiki/Network_Model#Configuring_VLAN_in_a_cluster
Host #1, has two bonds (one GbE, one 10G) to the switch (Aruba S2500), host #2 has one GbE bond. Switch is configured for passive LACP bonding on all three pairs of ports concerned, and those port channels are configured as trunk ports.
Host #1 /etc/networking/interfaces:
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
auto enp3s0
iface enp3s0 inet manual
auto enp4s0
iface enp4s0 inet manual
auto enp1s0f2
iface enp1s0f2 inet manual
auto enp1s0f3
iface enp1s0f3 inet manual
auto bond1
iface bond1 inet manual
slaves enp1s0f2 enp1s0f23
bond_miimon 100
bond_mode 802.3ad
auto bond0
iface bond0 inet manual
slaves enp3s0 enp4s0
bond_miimon 100
bond_mode 802.3ad
auto vmbr0
iface vmbr0 inet static
address 192.168.0.118
netmask 255.255.255.0
gateway 192.168.0.1
bridge_ports bond0
bridge_stp off
bridge_fd 0
auto vmbr2
iface vmbr2 inet static
address 192.168.0.119
netmask 255.255.255.0
bridge_ports bond1
bridge_stp off
bridge_fd 0
auto vlan10
iface vlan10 inet manual
vlan_raw_device bond0
auto vmbr1
iface vmbr1 inet static
address 192.168.1.2
netmask 255.255.255.0
network 192.168.1.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0
post-up ip route add table vlan10 default via 192.168.1.254 dev vmbr1
post-up ip rule add from 192.168.1.0/24 table vlan10
post-down ip route del table vlan10 default via 192.168.1.254 dev vmbr1
post-down ip rule del from 192.168.1.0/24 table vlan10
#clusternet
auto vlan30
iface vlan30 inet manual
vlan_raw_device bond1
auto vmbr30
iface vmbr30 inet static
address 192.168.30.2
netmask 255.255.255.0
network 192.168.30.0
bridge_ports vlan30
bridge_stp off
bridge_fd 0
post-up ip route add table vlan30 default via 192.168.30.254 dev vmbr30
post-up ip rule add from 192.168.30.0/24 table vlan30
post-down ip route del table vlan30 default via 192.168.30.254 dev vmbr30
post-down ip rule del from 192.168.30.0/24 table vlan30
#VPN
auto vlan50
iface vlan50 inet manual
vlan_raw_device bond1
auto vmbr3
iface vmbr3 inet static
address 192.168.50.2
netmask 255.255.255.0
network 192.168.50.0
bridge_ports vlan50
bridge_stp off
bridge_fd 0
post-up ip route add table vlan50 default via 192.168.50.254 dev vmbr3
post-up ip rule add from 192.168.50.0/24 table vlan50
post-down ip route del table vlan50 default via 192.168.50.254 dev vmbr3
post-down ip rule del from 192.168.50.0/24 table vlan50
#PUBLIC
auto vlan99
iface vlan99 inet manual
vlan_raw_device bond1
auto vmbr4
iface vmbr4 inet static
address 192.168.99.2
netmask 255.255.255.0
network 192.168.99.0
bridge_ports vlan99
bridge_stp off
bridge_fd 0
post-up ip route add table vlan99 default via 192.168.99.254 dev vmbr4
post-up ip rule add from 192.168.99.0/24 table vlan99
post-down ip route del table vlan99 default via 192.168.99.254 dev vmbr4
post-down ip rule del from 192.168.99.0/24 table vlan99
#WAN
auto vlan200
iface vlan200 inet manual
vlan_raw_device bond1
auto vmbr5
iface vmbr5 inet static
address 192.168.200.2
netmask 255.255.255.0
network 192.168.200.0
bridge_ports vlan200
bridge_stp off
bridge_fd 0
post-up ip route add table vlan200 default via 192.168.200.254 dev vmbr5
post-up ip rule add from 192.168.200.0/24 table vlan200
post-down ip route del table vlan200 default via 192.168.200.254 dev vmbr5
post-down ip rule del from 192.168.200.0/24 table vlan200
#STORAGENETand that of host #2
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface enp1s0f0 inet manual
iface enp1s0f1 inet manual
auto bond0
iface bond0 inet manual
slaves enp1s0f0 enp1s0f1
bond_miimon 100
bond_mond 802.3ad
auto vmbr0
iface vmbr0 inet static
address 192.168.0.117
netmask 255.255.255.0
gateway 192.168.0.1
bridge_ports bond0
bridge_stp off
bridge_fd 0
auto vlan10
iface vlan10 inet manual
vlan_raw_device bond0
auto vmbr2
iface vmbr2 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0
post-up ip route add table vlan10 default via 192.168.1.254 dev vmbr2
post-up ip rule add from 192.168.1.0/24 table vlan10
post-down ip route del table vlan10 default via 192.168.1.254 dev vmbr2
post-down ip rule del from 192.168.1.0/24 table vlan10
#clusternet
auto vlan200
iface vlan200 inet manual
vlan_raw_device bond0
auto vmbr1
iface vmbr1 inet static
address 192.168.200.254
netmask 255.255.255.0
bridge_ports vlan200
bridge_stp off
bridge_fd 0
post-up ip route add table vlan200 default via 192.168.200.1 dev vmbr2
post-up ip rule add from 192.168.200.0/24 table vlan200
post-down ip route del table vlan200 default via 192.168.200.1 dev vmbr2
post-down ip rule del from 192.168.200.0/24 table vlan200
#storagenet
auto vlan30
iface vlan30 inet manual
vlan_raw_device bond0
auto vmbr30
iface vmbr30 inet static
address 192.168.30.1
netmask 255.255.255.0
network 192.168.30.0
bridge_ports vlan30
bridge_stp off
bridge_fd 0
post-up ip route add table vlan30 default via 192.168.30.254 dev vmbr30
post-up ip rule add from 192.168.30.0/24 table vlan30
post-down ip route del table vlan30 default via 192.168.30.254 dev vmbr30
post-down ip rule del from 192.168.30.0/24 table vlan30
#VPNHosts can ping the switch on the VLANs but cannot see eachother. When I first configured and brought up vmbr1 and vmbr30 on host #2 it could ping host #1 but not the other way round. Once I rebooted host #2 this was no longer the case.
Switch cannot ping any of the VLAN interfaces on either host, but could temporarily when the bridges were first configured but now cannot post-rebooting both hosts.
Any ideas how I might go about debugging this further?