reconfigure network pve with new subnet in Evpn

[gian2000]

initially I had configured pve8 with a single node with bridge vmbr0 on the subnet 192.168.10.0/24 gatevay 192.168.10.1.then I added a second node and created a cluster and in each node the vnet localnetwork appeared on the same subnet.to be able to make the vms communicate I then switched to Evpn and it worked, in the sense that the vms communicated with each other and with the outside.Then I was forced to change the subnet to 192.168.20.0/24 gateway 192.168.20.1.now nothing works anymore and I can't change or delete the localnetwork.also I have never been able to make the fqdn resolution work with dns from the vms, nslookup times out and ping doesn't respond.the 2 nodes have ip 192.168.9.12 and 192.168.9.13 gateway and dns 192.168.9.1.do i have to reinstall the cluster?if you need more configuration information i will send it.thanks.

 

[gian2000]

Hi, partially solved.now all the vm of the 2 nodes communicate but it remains localnetwork and I can't do ing from the vm to the 2 nodes or even to external ip.thanks.

 

[gian2000]

Hi, now i can pringo between the vm of the 2 nodes, from the vm to the 2 nodes, and from the 2 nodes to the vm, and outside but only with ip.if i use ping with external fqdn it doesn't resolve the name.the gateway is 192.168.9.1 and it's on the same subnet as the 2 nodes that use it as a gateway.the vm use 192.168.9.1 as a gateway.nslookup times out.thanks.

 

[gian2000]

Hi.
maybe I solved it.
in the file /etc/frr/frr.conf I have the section

!
ip route 192.168.20.0/24 10.255.255.2 xvrf_Evpn
!

then in the routing table: root@pve2:~# ip route
default via 192.168.9.1 dev vmbr0 proto kernel onlink 10.10.10.0/24 dev enp3s0 proto kernel scope link src 10.10.10.2 10.255.255.0/30 dev xvrf_Evpn proto kernel scope link src 10.255.255 .1 192.168.9.0/24 dev vmbr0 proto kernel scope link src 192.168.9.13 192.168.20.0/24 nhid 140 via 10.255.255.2 dev xvrf_Evpn proto static metric 20 if I replace the last line with ip route add 192.168.20.0/255.255.255.0 dev EvpnNet

then

default via 192.168.9.1 dev vmbr0 proto kernel onlink
10.10.10.0/24 dev enp3s0f1 proto kernel scope link src 10.10.10.1
10.255.255.0/30 dev xvrf_Evpn proto kernel scope link src 10.255.255.1
192.168.9.0/24 dev vmbr0 proto kernel scope link src 192.168.9.12
192.168.20.0/24 dev EvpnNet scope link

everything seems to work, vms pung each other, vms ping with nodes, nodes
ping vms, vms ping outside and fqdn resolution to
outside works.
also the dns of active directory installed on a vm with forwarder on dns 192.168.9.1
now works.

i don't know why there was that route configuration but i changed several
times the proxmox vm network since it is a test cluster.
we'll see if it appears again on the production cluster.
thanks.