Tip

This is the documentation for the 24.06 version. Looking for the documentation of the latest version? Have a look here.

Dynamic Routing Manager Configuration¶

Configuration of the dynamic routing manager itself is performed from within config-route-dynamic-manager mode, which is entered as follows:

tnsr(config)# route dynamic manager
tnsr(config-route-dynamic-manager)#

That mode offers options which apply to the dynamic routing manager process, including global options which affect multiple routing protocols, logging options, and debugging options.

Dynamic Routing Manager Options¶

These options control behavior of routes received from dynamic routing sources.

(ipv4|ipv6) nht resolve-via-default:

Allows next-hop tracking to locate the next hop using the default route when the routing table does not contain an entry with a route to the peer. This allows the dynamic routing manager to locate peers using the default route rather than requiring a static route to a peer.

This is enabled by default and is useful when routing peers are reachable via the default route.

Tip

To disable this behavior use the no form, e.g. no ipv4 nht resolve-via-default.

Logging¶

The dynamic routing manager daemon can send log messages to a file, via syslog, or both.

log file <filename> [<level>]:

Instructs the dynamic routing manager daemon to send log messages to the specified file. The file must be in /var/log/frr/ and the name must end in .log.

The optional level parameter determines the verboseness of the logged data. See Log levels for details.

Warning

This command requires an absolute path to a log file, not a relative path. For example: /var/log/frr/routing.log. This file must be writable by the frr user.

The OS will automatically rotate the logs based on the configuration in /etc/logrotate.d/netgate-frr. The current configuration rotates the logs when they grow larger than 500 Kilobytes and rotates the logs 14 times before removing older log entries.

log syslog [<level>]:

Instructs the dynamic routing manager daemon to send log messages to syslog. The optional level parameter determines the verboseness of the logged data. See Log levels for details.

Log levels¶

Log levels set the verboseness of the logging recorded by the dynamic routing manager. Each level includes messages from higher priority levels. The default level is debugging, which will log as much detail as possible.

Note

Even if the log level is set to debugging, actual debugging messages may not appear unless specific debug entries are set. See Debugging for details.

In order of verboseness, from low to high, the available level values are:

emergencies
alerts
critical
errors
warnings
notifications
informational
debugging

For example, if the log level is set to errors, then the logs will contain messages with a level of emergencies, alerts, critical, and errors, and will exclude the rest.

Debugging¶

The debug command controls which debugging messages will be logged by the dynamic routing manager. These include:

debug events:: General events.
debug fpm:: Forwarding Plane Manager events.
debug kernel:: Kernel messages.
debug kernel msgdump [send|receive]:: Raw netlink messages, optionally limited to send or receive messages.
debug nht:: Next-Hop tracking events
debug packet [send|receive] [detail]:: Information about each packet seen by the dynamic routing manager. Optionally limited to send or receive packets. The detail keyword will log additional information for each packet.
debug rib [detail]:: Routing Information Base events, optionally with more detailed information.

Note

Debugging messages will only appear in logs if the logs are set to include debugging messages. See Log levels for details.