BGP w/OVN: nexthop value not synchronised across cluster nodes #14531
Assignees
Milestone
Comments
|
In case it helps, it looks like restarting the LXD snap causes those values to re-sync: jsimpso@mc-002:~$ lxc query /internal/testing/bgp{
"peers": [
{
"address": "10.0.25.1",
"asn": 64513,
"count": 1,
"holdtime": 0,
"password": ""
}
],
"prefixes": [
{
"nexthop": "10.0.10.3",
"owner": "network_3",
"prefix": "172.16.0.128/28"
},
{
"nexthop": "0.0.0.0",
"owner": "network_4",
"prefix": "172.16.0.0/28"
},
{
"nexthop": "0.0.0.0",
"owner": "network_5",
"prefix": "172.16.1.0/25"
}
],
"server": {
"address": "10.0.25.11",
"asn": 64512,
"router_id": "10.0.25.11",
"running": true
}
}jsimpso@mc-002:~$ sudo snap restart lxd
2024-11-28T11:07:48+08:00 INFO Waiting for "snap.lxd.daemon.service" to stop.
Restarted.
jsimpso@mc-002:~$ lxc query /internal/testing/bgp{
"peers": [
{
"address": "10.0.25.1",
"asn": 64513,
"count": 1,
"holdtime": 0,
"password": ""
}
],
"prefixes": [
{
"nexthop": "10.0.10.4",
"owner": "network_4",
"prefix": "172.16.0.0/28"
},
{
"nexthop": "10.0.10.5",
"owner": "network_5",
"prefix": "172.16.1.0/25"
},
{
"nexthop": "10.0.10.3",
"owner": "network_3",
"prefix": "172.16.0.128/28"
}
],
"server": {
"address": "10.0.25.11",
"asn": 64512,
"router_id": "10.0.25.11",
"running": true
}
} |
|
Thanks @jsimpso this is high on my list to work on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
Issue description
This is a MicroCloud deployed cross 3 physical nodes
I've configured BGP between LXD and the physical router in this lab network
The router is successfully receiving routes for the three networks I've created so far. However, one of those networks is showing different values for the next hop:
Running
lxc query internal/testing/bgpacross the three nodes confirms that only one of them has the nexthop value set to the OVN router, the other two list "0.0.0.0".:mc-001:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "10.0.10.4", "owner": "network_4", "prefix": "172.16.0.0/28" }, { "nexthop": "0.0.0.0", "owner": "network_5", "prefix": "172.16.1.0/25" } ], "server": { "address": "10.0.25.10", "asn": 64512, "router_id": "10.0.25.10", "running": true } }mc-002:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "10.0.10.4", "owner": "network_4", "prefix": "172.16.0.0/28" }, { "nexthop": "0.0.0.0", "owner": "network_5", "prefix": "172.16.1.0/25" } ], "server": { "address": "10.0.25.11", "asn": 64512, "router_id": "10.0.25.11", "running": true } }mc-003:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "10.0.10.4", "owner": "network_4", "prefix": "172.16.0.0/28" }, { "nexthop": "10.0.10.5", "owner": "network_5", "prefix": "172.16.1.0/25" } ], "server": { "address": "10.0.25.12", "asn": 64512, "router_id": "10.0.25.12", "running": true } }Steps to reproduce
I seem to be able to trigger this behaviour by changing the configuration of the network. This issue occurred after I changed the MTU for the network from
1442to1500for some unrelated troubleshooting. Changing the configuration back to its original state doesn't appear to have any positive effect.I've just reproduced this by replicating that same change (editing the network's YAML configuration via the LXD UI) on
network_4from the above output, and now see the same situation there:Router
mc-001:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "0.0.0.0", "owner": "network_5", "prefix": "172.16.1.0/25" }, { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "0.0.0.0", "owner": "network_4", "prefix": "172.16.0.0/28" } ], "server": { "address": "10.0.25.10", "asn": 64512, "router_id": "10.0.25.10", "running": true } }mc-002:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "0.0.0.0", "owner": "network_4", "prefix": "172.16.0.0/28" }, { "nexthop": "0.0.0.0", "owner": "network_5", "prefix": "172.16.1.0/25" } ], "server": { "address": "10.0.25.11", "asn": 64512, "router_id": "10.0.25.11", "running": true } }mc-003:
{ "peers": [ { "address": "10.0.25.1", "asn": 64513, "count": 1, "holdtime": 0, "password": "" } ], "prefixes": [ { "nexthop": "10.0.10.3", "owner": "network_3", "prefix": "172.16.0.128/28" }, { "nexthop": "10.0.10.4", "owner": "network_4", "prefix": "172.16.0.0/28" }, { "nexthop": "10.0.10.5", "owner": "network_5", "prefix": "172.16.1.0/25" } ], "server": { "address": "10.0.25.12", "asn": 64512, "router_id": "10.0.25.12", "running": true } }The text was updated successfully, but these errors were encountered: