You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we have the generic static routing module and the code to generate the static routes toward the default gateway, we could implement 'role: host' for other devices. The only requirements would be that a device supports the 'routing.static' feature.
To further optimize the static routes, we could have "initial.mgmt_vrf" feature to indicate whether the device uses a management VRF. Such a device needs just a default route not a bunch of routes for pool prefixes.
The text was updated successfully, but these errors were encountered:
We already have netlab_mgmt_vrf for frr, not exactly a feature but related
That would be a nice way to ensure someone using an old box/container would not complain -- create a bunch of static routes unless the node has netlab_mgmt_vrf set in which case use just a default route.
However, netlab_mgmt_vrf could be defined in a number of places, so it will be fun to figure out its final value.
Now that we have the generic static routing module and the code to generate the static routes toward the default gateway, we could implement 'role: host' for other devices. The only requirements would be that a device supports the 'routing.static' feature.
To further optimize the static routes, we could have "initial.mgmt_vrf" feature to indicate whether the device uses a management VRF. Such a device needs just a default route not a bunch of routes for pool prefixes.
The text was updated successfully, but these errors were encountered: