Run "vtysh -b" after FRR is started and you should see the incorrect commands, vtysh will warn about them. This is what is done to apply frr.conf on startup.
FRR doesn't log incorrect commands by default right now since that would add noise to the log file if you make normal mistakes while in an interactive session. I agree it would be helpful if we logged config issues at startup.
Quentin
Hi,
so when I am using the vtysh and typing in commands manually, when I
enter a wrong or non-existing command, I receive an error: '%Unknown
command: COMMAND'. But how do I find out that some of the commands from
my frr.conf file were wrong? I tried both 'log file' and 'log stdout'
together with 'log commands'. With 'log file' and 'log commands' when I
start frr, I can see the commands that were read from the frr.conf, but
when there is a wrong command, no error shows up. Is this correct? The
command is simply skipped.
Now with 'log stdout' I am really not sure where the output gets
redirected. In vtysh I don't see any logs showing up on the screen.
Maybe I am missing something here? Do I miss some configuration
somewhere to redirect the stdout somewhere? I was kind of assuming I
would see the logs in the vtysh itself - sort of how on Cisco devices.
If anyone could share some insight on this, I would be grateful. Thanks.
Michal Ruprich
_______________________________________________
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev