Multiple Default routes seen on Secondary Node.
Article ID: CTX234941
Updated On:
Description
Multiple Default routes seen on Secondary Node, whereas single default route on Primary.
Resolution
Do not configure default route on secondary other than what is configured on Primary.
Even if this has to be done during initial setup, once HA is up and running ensure to remove the default route from Secondary which does not match the one in primary.
node config, none of this will be wiped out on secondary as a part of HA SYNC.
If a different default route is configured on the Secondary node as compared to the Primary, this will not be removed as a part of config sync. Instead the one from primary will be added as part of config sync causing the Secondary node to have two default routes.
In this scenario if a failover happens, the old secondary (new primary) will have two default routes and will forward traffic via both routes (round robin) this can also cause an outage if one of the default routes is wrong / invalid.
Even if this has to be done during initial setup, once HA is up and running ensure to remove the default route from Secondary which does not match the one in primary.
Problem Cause
Hostname, NSIP, default gateway, interface LA Channel Bindings are individualnode config, none of this will be wiped out on secondary as a part of HA SYNC.
If a different default route is configured on the Secondary node as compared to the Primary, this will not be removed as a part of config sync. Instead the one from primary will be added as part of config sync causing the Secondary node to have two default routes.
In this scenario if a failover happens, the old secondary (new primary) will have two default routes and will forward traffic via both routes (round robin) this can also cause an outage if one of the default routes is wrong / invalid.
Was this article helpful?
Yes
No
Powered by
