Installing and Administering Internet Services

298 Chapter 8
Configuring gated
Troubleshooting gated
ospf_monitor
/usr/sbin/ospf_monitor is a support tool that can be used to query
OSPF routers for information on OSPF routing tables, interfaces, and
neighbors, as well as data on AS external databases, link-state
databases, error logs, and input/output statistics. Running the
ospf_monitor command displays a prompt that allows you to enter
interactive commands. See the ospf_monitor man page for details on
using this tool.
Common Problems
This section covers typical problems with gated operation.
Problem 1: gated does not act as you expected it to.
First, check the syslogd output for any syntax errors that may have
been flagged.
To detect incorrect configuration commands, use gated tracing. The
following shows two sample configuration files, along with the trace files
generated by gated. The node used has three interfaces: lan0, lan1,
and lan2. In the configuration files, lan0, lan1, and lan3 are specified.
In the first configuration shown, the strictintfs option has been
specified for the interfaces, so gated exits when the error is detected.
Interface Configuration with strictintfs Option Specified.
The following configuration references a non-existent interface. The line
options strictintfs in the interfaces statement means that all
configured interfaces must be present before gated starts.
traceoptions "tt" general;
interfaces {
options strictintfs ;
interface lan0 lan1 lan3 passive ;
} ;
rip yes ;
The following is the tracing output that is produced when gated is
started with this configuration: