undefined | Better HN

0 pointseqvinox3y ago0 comments

You don't need FIB install for that.

For any amount of reasonable distinction of "servers" and "routers", you should never need a FIB install on a server. There are good reasons to keep these functions separate (most prominently, address ownership/binding issues with services that are frequently not designed to deal with multiple interfaces/route choices.)

NB: this is not about physical devices. VMs/containers on your host are frequently "servers" while the hypervisor is a "router".

0 comments

elij3y ago

route on host (rfc5549) is the best strategy for host mobility if your fabric is designed around that idea and you embrace ECMP, stateless networking and bipartite topologies. You need to track state to do that without changing the FIB.

j / k navigate · click thread line to collapse

0 pointseqvinox3y ago0 comments

You don't need FIB install for that.

NB: this is not about physical devices. VMs/containers on your host are frequently "servers" while the hypervisor is a "router".

0 comments

elij3y ago

j / k navigate · click thread line to collapse